summaryrefslogtreecommitdiff
path: root/src/cpu/kvm/BaseKvmCPU.py
diff options
context:
space:
mode:
authorAndreas Sandberg <andreas.sandberg@arm.com>2016-03-30 10:52:25 +0100
committerAndreas Sandberg <andreas.sandberg@arm.com>2016-03-30 10:52:25 +0100
commita3efb6bd1d0d83297b5b412badc0b7db98b7be1e (patch)
tree424147084794cefe47a22b53758bfb538d1bc16e /src/cpu/kvm/BaseKvmCPU.py
parentd4eb354e30171c8c1d65c7158eb05369be6c5e2e (diff)
downloadgem5-a3efb6bd1d0d83297b5b412badc0b7db98b7be1e.tar.xz
kvm: Add an option to force context sync on kvm entry/exit
This changeset adds an option to force the kvm-based CPUs to always synchronize the gem5 thread context representation on entry/exit into the kernel. This is very useful for debugging. Unfortunately, it is also the only way to get reliable register contents when using remote gdb functionality. The long-term solution for the latter would be to implement a kvm-specific thread context. Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Alexandru Dutu <alexandru.dutu@amd.com>
Diffstat (limited to 'src/cpu/kvm/BaseKvmCPU.py')
-rw-r--r--src/cpu/kvm/BaseKvmCPU.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/cpu/kvm/BaseKvmCPU.py b/src/cpu/kvm/BaseKvmCPU.py
index b7c964669..34ab752de 100644
--- a/src/cpu/kvm/BaseKvmCPU.py
+++ b/src/cpu/kvm/BaseKvmCPU.py
@@ -71,6 +71,8 @@ class BaseKvmCPU(BaseCPU):
kvmVM = Param.KvmVM(Parent.any, 'KVM VM (i.e., shared memory domain)')
useCoalescedMMIO = Param.Bool(False, "Use coalesced MMIO (EXPERIMENTAL)")
usePerfOverflow = Param.Bool(False, "Use perf event overflow counters (EXPERIMENTAL)")
+ alwaysSyncTC = Param.Bool(False,
+ "Always sync thread contexts on entry/exit")
hostFreq = Param.Clock("2GHz", "Host clock frequency")
hostFactor = Param.Float(1.0, "Cycle scale factor")