You're right that this is potentially confusing, but there isn't a universal clock period so that division isn't possible. A better fix is to change cycle to tick which seems to have been done to most but not all of the scripts in configs in the source tree. I found a few places on the wiki here:
http://m5sim.org/wiki/index.php/Simulation_Scripts_Explained where 'Exiting @ cycle' is used. Is that what you mean by "the fs.py posted on the webpage"? I'm not aware of any actual fs.py file posted on the website. I'll fix the discrepancies in configs and on the wiki. Please let me know if you're talking about some additional location we'll also need to fix. Gabe Stevenson Jian wrote: > Hi, > I noticed that the fs.py posted on the webpage ends with the following > line: > print 'Exiting @ cycle %i because %s' % (m5.curTick(), exit_cause). > > Well, cycle is not the same as Tick. This is really misleading... > Could someone make the easy fix by dividing the m5.curTick() by the > number of ticks per clock period? > Thanks, > Steve > ------------------------------------------------------------------------ > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
