summaryrefslogtreecommitdiff
path: root/src/cpu/kvm/BaseKvmCPU.py
diff options
context:
space:
mode:
authorAndreas Sandberg <andreas@sandberg.pp.se>2013-06-11 09:24:55 +0200
committerAndreas Sandberg <andreas@sandberg.pp.se>2013-06-11 09:24:55 +0200
commitc97a99110b8beafcf557636688e81861157a8c1e (patch)
treefc68cc805f2d62bf79ce901cc5298d40b099cac3 /src/cpu/kvm/BaseKvmCPU.py
parent4f002930bc03125b9b886233985993291f5a4730 (diff)
downloadgem5-c97a99110b8beafcf557636688e81861157a8c1e.tar.xz
kvm: Separate host frequency from simulated CPU frequency
We used to use the KVM CPU's clock to specify the host frequency. This was not ideal for several reasons. One of them being that the clock parameter of a CPU determines the frequency of some of the components connected to the CPU. This changeset adds a separate hostFreq parameter that should be used to specify the host frequency until we add code to autodetect it. The hostFactor should still be used to specify the conversion factor between the host performance and that of the simulated system.
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 796a7794b..644ca3620 100644
--- a/src/cpu/kvm/BaseKvmCPU.py
+++ b/src/cpu/kvm/BaseKvmCPU.py
@@ -71,4 +71,6 @@ 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)")
+
+ hostFreq = Param.Clock("2GHz", "Host clock frequency")
hostFactor = Param.Float(1.0, "Cycle scale factor")