Here is an example cmd line. ./build/ALPHA/gem5.opt configs/example/fs.py -n 2 --checkpoint-dir=/path/to/checkpoint/dir/ -r 1 --cpu-type=atomic --restore-with-cpu=atomic --take-checkpoints=$x,$y --max-checkpoints=$N
where $x = c_1 in your case. $y is the period of doing checkpoint and $N specify how many checkpoints you want in total. $N = (c_2 - c_1) / $y in your case. The program will stop after taking $N checkpionts Runjie On Mon, Oct 29, 2012 at 11:14 PM, shervin hajiamini <hajamini_2...@yahoo.com > wrote: > Hi Runjie, > > Thank you very much for your email. I have not tried this way. For getting > the periodic stats for the ROI of a benchmark, do I ONLY need to use the > command line options of fs.py/ruby_fs.py? (without changing gem5 source > code) > > For getting the periodic stats for ROI which starts at tick/cycle c_1 and > ends at tick/cycle c_2, I would appreciate if you could precisely let me > know which command option(s) I need to use? could you please give me a > numerical example? > > Thanks, > Shervin > > --- On *Tue, 10/30/12, Runjie Zhang <rz...@virginia.edu>* wrote: > > > From: Runjie Zhang <rz...@virginia.edu> > Subject: Re: [gem5-users] dumping periodic stats with checkpoints > To: hajamini_2...@yahoo.com > Cc: gem5-users@gem5.org > Date: Tuesday, October 30, 2012, 3:10 AM > > Hi, Shervin > > Have you tried the cmd line options of either fs.py or ruby_fs.py? > > For example: > > --take-checkpoints=TAKE_CHECKPOINTS > <M,N> will take checkpoint at cycle M and every N > cycles thereafter > --max-checkpoints=MAX_CHECKPOINTS > the maximum number of checkpoints to drop > --max-checkpoints=MAX_CHECKPOINTS > the maximum number of checkpoints to drop > --work-begin-checkpoint-count=WORK_BEGIN_CHECKPOINT_COUNT > checkpoint at specified work begin count > --work-end-checkpoint-count=WORK_END_CHECKPOINT_COUNT > checkpoint at specified work end count > > > ------------------------------------------------------------------------- > > the second simulate should be end_tick_ROI - start_tick_ROI. You pass a > relative time to the function, not an absolute time. > > Thanks, > > Ali > > On Oct 27, 2012, at 11:29 PM, shervin hajiamini wrote: > > > Hi Ali, Andreas, > > > > > > > > I have tested dumping periodic stats for only ROI by putting the > following > > statements in simulation.py: > > > > > > > > M5.simulate(start_tick_ROI) > > statDump(4000000000) > > exit_event = m5.simulate(end_tick_ROI) > > > > The stats get dumped (every period) starting from start_tick_ROI, but it > does > > NOT stop at end_tick_ROI. > > > > Please let me know how I can make sure that the simulation stops at > > end_tick_ROI. I am interested in having stats for only ROI. > > > > Thanks, > > Shervin > > > > ------------------------------------------------------ > > > > Hi Shervin, > > > > If you are not interested in what happens after a specific tick T, then > only > > run to that tick and exit. > > > > Andreas > > --------------------------------------- > > > > Hello Ali, > > > > I would appreciate in you could answer my question (email below) about > > dumping stats for ROI using simulation.py. > > > > Following your direction, I have run the simulation with stats dumped > every > > period, however I want to have the period dumping stopped at a particular > > tick (end of ROI). Could you please let me know how I can specify that in > > simulation.py? > > > > Regards, > > Shervin > > > > --------------------------------------------------- > > Hi Ali, > > > > Thank you very much for your direction. If I have understood it > correctly, > > "ticks_till_ROI" indicates the TICK when ROI starts? How can I specify > when > > (at which tick) ROI ends? Shall I specify that with m5.MaxTick? > > > > Could you please tell me where exactly (in simulation.py) I should put > the > > statements you said? Shall I put it in after ***Real Simulation***? > > > > Thanks, > > Shervin > > ------------------------------------------------------------------------ > > > > Hi Shervin, > > > > You can modify Simulation.py to run for however many ticks you need an > then > > return control to python: > > m5.simulate(ticks_till_ROI) > > statDump(1000000000) > > m5.simulate(m5.MaxTick) > > > > > > Ali > > > > ******************************** > > _______________________________________________ > > gem5-users mailing list > > gem5-users@gem5.org <http://mc/compose?to=gem5-users@gem5.org> > > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
