changeset 650fc966ed78 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=650fc966ed78
description:
config: Initialize and check cpt_starttick
The previous changeset (9816) that fixes the use of max ticks
introduced the
variable cpt_starttick, which is used for setting the relative max tick.
Unfortunately, with checkpointing at an instruction count or with
simpoints,
the checkpoint tick is not stored conveniently, so to ensure that
cpt_starttick
is initialized, set it to 0. Also, if using --rel-max-tick, check the
use of
instruction counts or simpoints to warn the user that the max tick
setting does
not include the checkpoint ticks.
diffstat:
configs/common/Simulation.py | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diffs (23 lines):
diff -r 94dac7d7bb88 -r 650fc966ed78 configs/common/Simulation.py
--- a/configs/common/Simulation.py Wed Sep 11 15:33:27 2013 -0500
+++ b/configs/common/Simulation.py Wed Sep 11 15:34:21 2013 -0500
@@ -126,6 +126,7 @@
if not isdir(cptdir):
fatal("checkpoint dir %s does not exist!", cptdir)
+ cpt_starttick = 0
if options.at_instruction or options.simpoint:
inst = options.checkpoint_restore
if options.simpoint:
@@ -430,6 +431,11 @@
# NOTE: this may need to be updated if checkpoints ever store
# the ticks per simulated second
maxtick_from_rel += cpt_starttick
+ if options.at_instruction or options.simpoint:
+ warn("Relative max tick specified with --at-instruction or" \
+ " --simpoint\n These options don't specify the " \
+ "checkpoint start tick, so assuming\n you mean " \
+ "absolute max tick")
explicit_maxticks += 1
if options.maxtime:
maxtick_from_maxtime = m5.ticks.fromSeconds(options.maxtime)
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
