Hi Nilay, I am aware of this feature. I do restore the checkpoint using --restore-with-cpu.
When setting that parameter to timing, it works. However, the simulation will not be detailed. I want to run an OoO+ruby simulation as soon as the checkpoint is loaded. I tried several combinations: a) --restore-with-cpu=detailed b) --restore-with-cpu=timing --cpu-type=detailed All of them give the same error: fatal: Can't unserialize 'system.cpu0:locked' @ cycle 2573654901000 [paramIn:build/ALPHA_MOESI_hammer/sim/serialize.cc, line 228] I looked at configs/common/Simulation.py, but it seems that in case that restore cpu and cpu type are not the same, it switches to Atomic. So, it's not clear to me what the command should look like so as to perform an OoO+ruby simulation by loading a ruby checkpoint. Regards, -Stavros. ________________________________________ From: Nilay Vaish [ni...@cs.wisc.edu] Sent: Sunday, June 03, 2012 3:01 PM To: Volos Stavros Cc: gem5-users@gem5.org Subject: Re: Ruby + OoO + with check-pointing support 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
