From 90bd20aae2bc940397628a4598b5b25f2c8549b5 Mon Sep 17 00:00:00 2001 From: Ali Saidi Date: Mon, 7 Jan 2013 13:05:33 -0500 Subject: tests: Always specify memory mode in every test system. Previous to this change we didn't always set the memory mode which worked as long as we never attempted to switch CPUs or checked that a CPU was in a memory system with the correct mode. Future changes will make CPUs verify that they're operating in the correct mode and thus we need to always set it. --- tests/configs/o3-timing-mp-ruby.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'tests/configs/o3-timing-mp-ruby.py') diff --git a/tests/configs/o3-timing-mp-ruby.py b/tests/configs/o3-timing-mp-ruby.py index 9bdef5eef..126e71ed5 100644 --- a/tests/configs/o3-timing-mp-ruby.py +++ b/tests/configs/o3-timing-mp-ruby.py @@ -38,7 +38,8 @@ import ruby_config ruby_memory = ruby_config.generate("TwoLevel_SplitL1UnifiedL2.rb", nb_cores) # system simulated -system = System(cpu = cpus, physmem = ruby_memory, membus = CoherentBus()) +system = System(cpu = cpus, physmem = ruby_memory, membus = CoherentBus(), + mem_mode = "timing") for cpu in cpus: # create the interrupt controller -- cgit v1.2.3