From 741f5215e9515c0d7179671f49fe1781f94e70e3 Mon Sep 17 00:00:00 2001 From: Ciro Santilli Date: Thu, 21 Jun 2018 08:46:59 +0100 Subject: [PATCH] gem5: refactor syscall emulation links --- README.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.adoc b/README.adoc index 9cfe88e..e7b6ca2 100644 --- a/README.adoc +++ b/README.adoc @@ -5042,7 +5042,8 @@ but it must be using the kernel version given by glibc, since we didn't hit that Analogous to <>, 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 vs QEMU