summaryrefslogtreecommitdiff
path: root/configs/example/fs.py
diff options
context:
space:
mode:
authorCurtis Dunham <Curtis.Dunham@arm.com>2017-02-14 15:09:18 -0600
committerCurtis Dunham <Curtis.Dunham@arm.com>2017-02-14 15:09:18 -0600
commit41beacce088e8f682a0e8ac48f22a3fa4805a43b (patch)
tree3cd96b36acb9b38a2010eeae07f193a9d2292c73 /configs/example/fs.py
parentd3bfc03688e164c02e9c25730ada11b669c01eda (diff)
downloadgem5-41beacce088e8f682a0e8ac48f22a3fa4805a43b.tar.xz
sim, kvm: make KvmVM a System parameter
A KVM VM is typically a child of the System object already, but for solving future issues with configuration graph resolution, the most logical way to keep track of this object is for it to be an actual parameter of the System object. Change-Id: I965ded22203ff8667db9ca02de0042ff1c772220 Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com>
Diffstat (limited to 'configs/example/fs.py')
-rw-r--r--configs/example/fs.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/configs/example/fs.py b/configs/example/fs.py
index 1ada59084..8102edc75 100644
--- a/configs/example/fs.py
+++ b/configs/example/fs.py
@@ -143,7 +143,7 @@ def build_test_system(np):
for i in xrange(np)]
if is_kvm_cpu(TestCPUClass) or is_kvm_cpu(FutureClass):
- test_sys.vm = KvmVM()
+ test_sys.kvm_vm = KvmVM()
if options.ruby:
# Check for timing mode because ruby does not support atomic accesses
@@ -280,7 +280,7 @@ def build_drive_system(np):
drive_sys.kernel = binary(options.kernel)
if is_kvm_cpu(DriveCPUClass):
- drive_sys.vm = KvmVM()
+ drive_sys.kvm_vm = KvmVM()
drive_sys.iobridge = Bridge(delay='50ns',
ranges = drive_sys.mem_ranges)