3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 02:05:57 +01:00
Code Issues Releases Wiki Activity

gem5: refactor syscall emulation links

Browse Source
This commit is contained in:
Ciro Santilli
2018-06-21 08:46:59 +01:00
parent 00d282d912
commit 741f5215e9
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.adoc
View File

@@ -5042,7 +5042,8 @@ but it must be using the kernel version given by glibc, since we didn't hit that
Analogous to <<qemu-user-mode>>, but less usable.
https://stackoverflow.com/questions/48959349/how-to-solve-fatal-kernel-too-old-when-running-gem5-in-syscall-emulation-se-m
* https://stackoverflow.com/questions/48986597/when-should-you-use-full-system-fs-vs-syscall-emulation-se-with-userland-program
* https://stackoverflow.com/questions/48959349/how-to-solve-fatal-kernel-too-old-when-running-gem5-in-syscall-emulation-se-m
First we try some `-static` sanity checks.
@@ -5457,7 +5458,7 @@ Tested architectures:
* `aarch64`
* `x86_64`
Like QEMU, gem5 also has a syscall emulation mode (SE), but in this tutorial we focus on the full system emulation mode (FS). For a comparison see: https://stackoverflow.com/questions/48986597/when-should-you-use-full-system-fs-vs-syscall-emulation-se-with-userland-program
Like QEMU, gem5 also has an user mode called syscall emulation mode (SE): <<gem5-syscall-emulation-mode>>
=== gem5 vs QEMU