sanchayanmaity/gem5
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Configs: Fix handling of maxtick and take_checkpoints

Browse source 
In Simulation.py, calls to m5.simulate(num_ticks) will run the simulated system
for num_ticks after the current tick. Fix calls to m5.simulate in
scriptCheckpoints() and benchCheckpoints() to appropriately handle the maxticks
variable.
This commit is contained in:
Joel Hestness 2013-04-09 16:25:30 -05:00
parent 1583056de8
commit 82c6734f6b
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
configs/common/Simulation.py
View file

@ -183,7 +183,7 @@ def scriptCheckpoints(options, maxtick, cptdir):
period = int(period)
num_checkpoints = 0
exit_event = m5.simulate(when)
exit_event = m5.simulate(when - m5.curTick())
exit_cause = exit_event.getCause()
while exit_cause == "checkpoint":
exit_event = m5.simulate(when - m5.curTick())
@ -215,7 +215,7 @@ def scriptCheckpoints(options, maxtick, cptdir):
return exit_event
def benchCheckpoints(options, maxtick, cptdir):
exit_event = m5.simulate(maxtick)
exit_event = m5.simulate(maxtick - m5.curTick())
exit_cause = exit_event.getCause()
num_checkpoints = 0