Are you talking about generating checkpoints with the detailed FullCPU model? That's not really supported. It's a pain to deal with things like outstanding memory references, and it's never been something we've needed, since when you're just trying to get past boot there's really no reason to do the boot in detailed mode anyway.
However, you should be able to take a checkpoint you generated with SimpleCPU and load it up in a functionally equivalent FullCPU simulation and run from there. We don't do that typically; we use the Sampler to start up in SimpleCPU and warm up the caches for a while then switch. (Note that the checkpoint does not include cache contents so there's not a lot of point in having caches in your checkpoint generation run.) But conceptually loading a SimpleCPU checkpoint directly into a FullCPU model should work. If that's what you're having trouble with, let us know.
Steve James Michael Poe II wrote:
I have a quick question about checkpointing. What I would like to do is be able to start the simulator past the long linux booting process in the Full system (detailed cpu) mode. I ran the simulator in the Full system mode using the default (linux-boot-detailed/run.py) configuration, loaded bash, and then issued an m5 checkpoint command. When I do this in the SimpleCPU mode (linux-boot/run.py), I can then just restart the simulator at any time using the --Root.checkpoint argument and it loads perfectly to the point right where I left it. I can't seem to get it to work right in the detailed mode, however (which is unfortunately where I need it most). Within the console, it seems to be re-booting the entire system (I again get all of the cryptic memory addresses and kernel information that the boot process displays in the beginning), but before it gets very far, it seems to terminate with the following message: CONSOLE PANIC (looping): CPU\uffff0 entering slaveLoop. Reenetering the console. HOSED Am I doing anything blatantly wrong? Am I correct to think that a checkpoint can be used this way? It seems to work in the Simple mode. I know one alternative would be to use the Sampler to go from Simple to Detailed, however setting up the checkpoint seems much easier, and since I won't be changing any architecturally visible to linux parameters, this method would also be much faster for me. Thank you for your help, James Ps. I did find one prior reference to this error [the "HOSED" error .. :) ] on the mailing list, but I think the author was directly interested in the booting process, and I don't think it relates to checkpointing... ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ m5sim-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/m5sim-users
------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ m5sim-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/m5sim-users
