changeset 1252ec1c8714 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=1252ec1c8714
description:
        Config: Change misleading "cycle" message to say "tick".

        Most of the messages in the config scripts that report a time value 
already
        print "@ tick" followed by the current tick value, but a few were 
printing
        "@ cycle". Since this is a distinction that's frequently confusing to 
new
        users, this changes those message to the more accurate and consistent 
"@ tick".

diffstat:

 configs/common/Simulation.py |  6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diffs (30 lines):

diff -r 634d88f0dbd4 -r 1252ec1c8714 configs/common/Simulation.py
--- a/configs/common/Simulation.py      Mon Nov 15 19:37:15 2010 -0800
+++ b/configs/common/Simulation.py      Wed Nov 17 23:16:19 2010 -0500
@@ -246,7 +246,7 @@
         else:
             print "Switch at curTick count:%s" % str(10000)
             exit_event = m5.simulate(10000)
-        print "Switched CPUS @ cycle = %s" % (m5.curTick())
+        print "Switched CPUS @ tick %s" % (m5.curTick())
 
         # when you change to Timing (or Atomic), you halt the system
         # given as argument.  When you are finished with the system
@@ -267,7 +267,7 @@
                 exit_event = m5.simulate()
             else:
                 exit_event = m5.simulate(options.warmup)
-            print "Switching CPUS @ cycle = %s" % (m5.curTick())
+            print "Switching CPUS @ tick %s" % (m5.curTick())
             print "Simulation ends instruction count:%d" % \
                     (testsys.switch_cpus_1[0].max_insts_any_thread)
             m5.drain(testsys)
@@ -367,7 +367,7 @@
 
     if exit_cause == '':
         exit_cause = exit_event.getCause()
-    print 'Exiting @ cycle %i because %s' % (m5.curTick(), exit_cause)
+    print 'Exiting @ tick %i because %s' % (m5.curTick(), exit_cause)
 
     if options.checkpoint_at_end:
         m5.checkpoint(joinpath(cptdir, "cpt.%d"))
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to