Hello Everyone, It's been a while but I'm starting to use MARSSx86 for simulations again. I've been trying to run 16 core simulations and am finding that the boot time is very long (~5 hours to make a checkpoint). This makes it quite frustrating when I accidentally set the wrong parameters inside the workload or run the wrong workload or any number of other mistakes I tend to make.
So I was thinking -- what if I made a post boot but pre-simulation-switch checkpoint (i.e., checkpoint but stay in emulation mode). That way, the create_checkpoints.py script could just launch the system from the post-boot snapshot and proceed to launch the workloads which would have the PTL calls that would then make the actual simulation checkpoints. Not only would that reduce the time it took to create a lot of checkpoints, but also if I screwed up a checkpoint, I could just delete it, boot the post-boot snapshot, tweak the workload, and re-checkpoint the simulation. I think marss checkpoints piggyback on qemu's snapshot capabilities, but is there some downside to this approach here that I'm missing? Thanks, Paul
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
