Hello, 
I have done something similar, taking a checkpoint after booting the image. 
However, I use only the "m5 exit" command instead of the "m5 checkpoint" and I 
take checkpoints using AtomicSimple and the fs.py. You can replace "checkpoint" 
with "exit" to see if it works for your configuration. In order this to work, 
you HAVE to use the option "--checkpoint-at-end" in your gem5 command. You can 
also specify a path for the checkpoint output to have a clear result by using 
"--checkpoint-dir=PATH_TO_DIR". This way, after booting, gem5 exits and with 
the above option a checkpoint is triggered. 

Example .rcS script : 
......... 
/sbin/m5 exit 
runspec --config=myconfig.cfg --size=test --noreportable --tune=base 
--iterations=1 mcf 
echo "mcf done!" 
/sbin/m5 exit 

After you can restore your checkpoint and continue execution using the same 
.rcS script, it will actually continue after the first m5 exit, which is just 
after booting. 

Hope it helps, 

-- 
Kleovoulos Kalaitzidis 
Doctorant - Équipe PACAP 

Centre de recherche INRIA Rennes - Bretagne Atlantique 
Bâtiment 12E, Bureau E321, Campus de Beaulieu, 
35042 Rennes Cedex, France 

> From: "Sethu Jose" <[email protected]>
> To: "gem5 users mailing list" <[email protected]>
> Sent: Sunday, April 28, 2019 3:03:52 AM
> Subject: [gem5-users] On checkpointing while using custom config file

> Hi,

> I'm trying out X86 full system simulation in GEM5 as explained in the tutorial
> found in this link:
> [ http://learning.gem5.org/book/part5/fs_config.html |
> http://learning.gem5.org/book/part5/fs_config.html ]

> I'm doing full system simulation using TimingSimpleCPU with X86. I would like 
> to
> take checkpoint once the system has booted up. The command I use to run the
> simulation is as follows:

> build/X86/gem5.opt configs/full_system/run.py --script=path/to/script

> With this, the system boots up and executes the script.

> I plan to take checkpoint right after booting up the system. Hence, I have 
> added
> the following line to the script:
> ****************
> echo "Creating checkpoint..."
> /sbin/m5 checkpoint
> echo "Checkpoint created!"
> echo "Started mcf ..."
> runspec --config=myconfig.cfg --size=test --noreportable --tune=base
> --iterations=1 mcf
> echo "mcf done!"
> /sbin/m5 exit
> ****************

> With this, the simulation exits when running /sbin/m5 stating the exit cause 
> as
> checkpoint. However, no checkpoint folders are created in the working
> directory. Neither does the restore command work. I have tried take checkpoint
> by running /sbin/m5 exit in the booted up system terminal. This also causes 
> the
> simulation to exit without creating any checkpoint folders.

> As I'm new to GEM5, could you please provide any insights on this issue? Is
> there any specific code that I need to add to my config file to make it take
> checkpoint?

> Thanks in advance for any help.

> Regards,
> Sethu

> _______________________________________________
> gem5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to