summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorLouis Burda <quent.burda@gmail.com>2023-02-06 11:30:27 -0600
committerLouis Burda <quent.burda@gmail.com>2023-02-06 11:30:27 -0600
commit8d018c17170a3b623f48de5282955b817a6284f3 (patch)
tree70c44cfe471771ef2a42933118846c6ab869df11 /Makefile
parent4dd9fe04e1399e8629ab2a98b54db6a7dcdb0076 (diff)
downloadcachepc-8d018c17170a3b623f48de5282955b817a6284f3.tar.gz
cachepc-8d018c17170a3b623f48de5282955b817a6284f3.zip
qemu-targetstep: Attempt to track guest process gfn when running in userspace
Seems like single-stepping the guest with LAPIC influences the guest scheduler behaviour, since just a single step inside the target gfn (to determine if its running in userspace), is enough to for us to never reach the GUEST_STOP_TRACK event. FWICT the single-stepping is not frequent and does not take long enough to justify never reaching the stop event.
Diffstat (limited to 'Makefile')
-rwxr-xr-xMakefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index fe4b337..9590b92 100755
--- a/Makefile
+++ b/Makefile
@@ -11,7 +11,7 @@ BINS += test/kvm-step test/kvm-step_guest
BINS += test/kvm-targetstep test/kvm-targetstep_guest
BINS += test/kvm-pagestep test/kvm-pagestep_guest
BINS += test/qemu-pagestep
-BINS += test/qemu-eviction test/qemu-eviction_guest
+BINS += test/qemu-targetstep test/qemu-targetstep_guest
# BINS += test/qemu-aes_guest test/qemu-aes
BINS += util/loglevel util/reset util/mainpfn