Dear Tyler, Thank you for your quick response. The simulator was built using "scons -Q c=1". When the "-machine single_core" option is available in the simconfig file (apart from the 3 simpoint options, which are already in), we get the message "Simulator is now waiting for a 'run' command." and it is idle, and if we remove it, it behaves the way I explained to you previously. That is, it generates a couple of wrong checkpoints and then it freezes. However, I have two more questions: 1. Is the procedure that generates checkpoints executed in emulation or in simulation mode? 2. Do you mean that the "-machine" option is needed in order to correctly generate the checkpoints? I really appreciate your help. George On Wed, September 10, 2014 22:00, [email protected] wrote: > Did you configure MARSS to use more than one CPU context? If you didn't > build MARSS with (scons c=1 ...) or use a machine configuration similar to > single_core's, that could be an explanation for the problems that you're > seeing. > > Tyler > >> >> >> >> >> >> >> >> >> >> >> Hello to all, >> >> We are trying to generate checkpoints from already >> created SimPoints, taken from SPEC CPU2006. Although we have followed >> the >> instructions shown in the MARSSx86 wiki page, it does not seem to work >> properly. The image is downloaded from the wiki (ubuntu-natty.qcow2) and >> the benchmarks are built in the same image. >> >> >> >> As a result, a couple of checkpoints are created and then the image >> freezes unexpectedly. Sometimes, it generates all the checkpoints, but >> unfortunately they are wrong, that is, they were taken in almost the >> same >> instructions. >> >> Below is the procedure that we followed: >> >> 1. >> Booting MARSSx86, using default >> configurations: >> >> qemu/qemu-system-x86_64 -vnc :10 -m 4096 -hda >> /opt/images/ubuntu-natty.qcow2 >> >> 2. By using of "create_checkpoint" >> binary (provided by ubuntu-natty.qcow2), we created the initial >> checkpoint >> at the beginning of the benchmark: >> e.g.: >> ~/create_checkpoint bzip2; >> ./bzip2_base.gcc43-64bit chicken.jpg 30 > /dev/null; >> ~/stop_sim >> >> 3. Rebooting MARSSx86 using the last created >> checkpoint: >> >> qemu/qemu-system-x86_64 -vnc :10 -m 4096 -loadvm bzip2 >> -simconfig simconfig.cfg -hda /opt/images/ubuntu-natty.qcow2 >> >> where >> simconfig.cfg file have the contents exactly as shown >> bellow: >> >> -simpoint >> /opt/simpoints/401.bzip2/t.simpoints >> -simpoint-interval >> 100M >> -simpoint-chk-name bzip2 >> >> Do you have any idea about what >> might be wrong? >> >> Â >> >> Thanks in advance, >> >> George >> >> >> >> _______________________________________________ >> http://www.marss86.org >> Marss86-Devel mailing list >> [email protected] >> https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel >> > > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
