On Sun, 3 Jun 2012, Volos Stavros wrote:
Hi Nilay,
Thanks for your reply.
When trying with gem5_fast I get the following error or commenting out the call
to setupFuncEvents, I get the following error:
fatal: Can't unserialize 'system.cpu0:locked' @ cycle
2573654901000[paramIn:build/ALPHA_MOESI_hammer/sim/serialize.cc, line 228]
I recreated the ruby checkpoints to make sure that they are read by the same
binary they were created from.
From the documentation on gem5.org --
By default, gem5 assumes that the checkpoint is to be restored using
Atomic CPUs. This may not work if the checkpoint was recorded using Timing
/ Detailed / Inorder CPU. One can mention the option --restore-with-cpu
<CPU Type> on the command line. The cpu type supplied with this option is
then used for restoring from the checkpoint.
--
Nilay
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
