Hi Zheng, This was a known bug with the default parameters to the simulation scripts. I just fixed this with changeset 9816: http://repo.gem5.org/gem5/rev/971507cbbe65. You should be able to download the diff from the reviews page and apply it to your repository: http://reviews.gem5.org/r/1816/.
This change actually splits the maxtick specification into relative and absolute flags, so you could either specify to run to absolute time 3B ticks with --abs-max-tick=3000000000, or that the simulation should run 2B ticks after restoring from the checkpoint with --rel-max-tick=2000000000, which would run to absolute time 3B ticks in the case you describe here (check out configs/common/Options.py for more detail on these flags). Hope that helps, Joel On Fri, Jul 26, 2013 at 10:11 AM, Zheng Wu <[email protected]> wrote: > Hi all, > > I have created a checkpoint at Tick 1 billion and when I restore the > checkpoint and continue simulation, I also specify a --maxtick to be 3 > billion (3x10^12 Ticks). > > However, based on the simulation output and stats.txt file, it seems that > the simulation exited at Tick 2 billion instead of 3 billion, any ideas? > > > Output: > Exiting @ tick 2,000,000,000,000 because simulate() limit reached > > Stats: > sim_ticks 1,000,000,000,000 # Number of ticks > simulated > final_tick 2,000,000,000,000 # Number of ticks > from beginning of simulation (restored from checkpoints and never reset) > > > Thank, > Zheng Wu > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- Joel Hestness PhD Student, Computer Architecture Dept. of Computer Science, University of Wisconsin - Madison http://pages.cs.wisc.edu/~hestness/
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
