I don't think you're going to be able to do this very easily since by definition the checkpoint will always have identical state between boot ups, so I'm not sure how you'd send a message to the machine to tell it you want to kill the thread. Perhaps if you rigged up some crazy network code like "query the host machine and see if I need to abort", though getting that to work with QEMU networking would probably be a fun fun task (and would also pollute your results, probably).
Why don't you just setup a second hard drive image with a checkpoint that just launches milc alone? Are you worried about the differences from the bootup being nondeterministic and messing up your results? On Wed, Jun 8, 2011 at 9:47 AM, Zhe Wang <[email protected]> wrote: > Hi, > > I have a question about how to kill a thread after marss load a checkpoint. > I made a checkpoint for multiprogram application. Such as I have two > benchmark mcf and milc. I set them on two different cores and run them by > using marss. After I load the checkpoint , I would like to kill benchmark > mcf, just left milc running. Then reason I want to do this is I would like > to compare the performance difference between benchmark milc running alone > with milc running with other benchmarks. Any idea about how to kill a > thread after load the checkpoint? > > Thanks > zhe > > _______________________________________________ > 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
