Hi Atieh, You can take checkpoints within the benchmark by instrumenting the code with the M5 magic instructions. You will need to grab a few files from ./util/m5/ and move them to the source tree of your benchmark: m5op.h, m5ops.h and m5op_<arch>.S (where <arch> is the ISA that you're building the benchmark for). You will need to include the m5op.h header in the source code that you're instrumenting, and you will need to build and link against the m5op_<arch>.S assembly file. As an example of how the instrumentation works, you can check out the m5 control application, ./util/m5/m5.c, and the appropriate Makefiles in ./util/m5. Hope this helps, Joel
On Tue, May 31, 2011 at 5:30 AM, Atieh Lotfi <ati.lo...@gmail.com> wrote: > Hi, > > I have some questions about checkpoitning mechanism in gem5. Is it possible > to control the checkpoint from the benchmark itself and not to control it > from the command line? I don’t want to take periodic checkpoints. I want to > determine some points in the benchmark for taking checkpoints. > > I also have another question. I want to know over and above serialize.c, > which c codes are related to getting checkpoints? > > Thanks in advance, > > Regards, > Atieh > _______________________________________________ > gem5-users mailing list > gem5-users@m5sim.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- Joel Hestness PhD Student, Computer Architecture Dept. of Computer Science, University of Texas - Austin http://www.cs.utexas.edu/~hestness
_______________________________________________ gem5-users mailing list gem5-users@m5sim.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
