Skip to content

Commit 741f521

Browse files
committed
gem5: refactor syscall emulation links
1 parent 00d282d commit 741f521

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5042,7 +5042,8 @@ but it must be using the kernel version given by glibc, since we didn't hit that
50425042

50435043
Analogous to <<qemu-user-mode>>, but less usable.
50445044

5045-
https://stackoverflow.com/questions/48959349/how-to-solve-fatal-kernel-too-old-when-running-gem5-in-syscall-emulation-se-m
5045+
* https://stackoverflow.com/questions/48986597/when-should-you-use-full-system-fs-vs-syscall-emulation-se-with-userland-program
5046+
* https://stackoverflow.com/questions/48959349/how-to-solve-fatal-kernel-too-old-when-running-gem5-in-syscall-emulation-se-m
50465047

50475048
First we try some `-static` sanity checks.
50485049

@@ -5457,7 +5458,7 @@ Tested architectures:
54575458
* `aarch64`
54585459
* `x86_64`
54595460

5460-
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
5461+
Like QEMU, gem5 also has an user mode called syscall emulation mode (SE): <<gem5-syscall-emulation-mode>>
54615462

54625463
=== gem5 vs QEMU
54635464

0 commit comments

Comments
 (0)