"comittComittedInsts" is funny ... haha ...tongue-twister! On the SMT side of things, I think the stats try to account for per-thread committed insts and then a overall total. The names/comments should reflect those better.
More than likely since there is so many different accounting for commits, they ALL probably arent being tagged for the special cases. So maybe what's needed is: sim_insts and committed_per_thread (if SMT) On Thu, Apr 23, 2009 at 12:05 PM, Steve Reinhardt <[email protected]> wrote: > OK, it's really a fairly superficial (but still troubling) statistics > problem... note that the SimpleCPU instruction count for this program is > 6404; O3 reasonably ends up with 6403 because the exit syscall instruction > causes the simulation to terminate before it gets committed, so you will be > off by one. That I can live with. But (1) why do we have so many different > stats to count committed instructions in O3 and (2) why aren't they > consistent? > > from tests/quick/00.hello/ref/alpha/linux/o3-timing/stats.txt: > sim_insts 6386 > # Number of instructions simulated > system.cpu.commit.COM:count 6403 # Number > of instructions committed > system.cpu.commit.commitCommittedInsts 6403 # The number of > committed instructions > system.cpu.committedInsts 6386 # > Number of Instructions Simulated > system.cpu.committedInsts_total 6386 # Number > of Instructions Simulated > > > > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > > -- ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
