I used mercurial to clone the latest version of gem5 in development
repository. By the way, I used to work on the stable release, however,
when I was trapped in a coherence protocol error then I switched to the
development repository to work around that error.
Thanks,
Hanfeng
On 11/27/2012 09:38 PM, Nilay Vaish wrote:
On Tue, 27 Nov 2012, hanfeng QIN wrote:
Hi all,
I adopt gem5 in SE plus Ruby mode. I want to warm up cache before
data measurement. During my experiment, I found the '-W' option does
not work. The simulation process is controlled in Ruby mode from
scratch instead of after <N> instructions as expected. I check the
file /config/common/Simulation.py/ and it seems that '-W' is only
invalid when '-s' is also specified. However, once I plus '-s'
option, the simulation is aborted and it throws an exception as
following,
info: Entering event queue @ 0. Starting simulation...
hack: be nice to actually delete the event here
Switched CPUS @ tick 54500
Changing memory mode to timing
System already in target mode. Memory mode unchanged.
switching cpus
gem5.opt: build/ALPHA_MESI_CMP_directory/cpu/simple/timing.cc:159:
virtual void TimingSimpleCPU::switchOut(): Assertion `_status ==
BaseSimpleCPU::Running || _status == Idle' failed.
Program aborted at cycle 54500
According to the above exception, I reviewed the '_status' and it
equals to BaseSimpleCPU::IcacheWaitResponse. I have no idea about
this bug.
What version of gem5 are you using?
--
Nilay
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
