Configs: Fix handling of maxtick and take_checkpoints
authorJoel Hestness <jthestness@gmail.com>
Tue, 9 Apr 2013 21:25:30 +0000 (16:25 -0500)
committerJoel Hestness <jthestness@gmail.com>
Tue, 9 Apr 2013 21:25:30 +0000 (16:25 -0500)
commit82c6734f6b0a614d01cb7c64a6bc53a20ca906a1
treea694485cea7b0fe78e267c77a308099a9e9b032b
parent1583056de8d5d9698cfeb87fb72a80e532e275c3
Configs: Fix handling of maxtick and take_checkpoints

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.
configs/common/Simulation.py