> On Jan. 11, 2016, 11:52 p.m., Joel Hestness wrote: > > src/cpu/kvm/base.cc, line 495 > > <http://reviews.gem5.org/r/3235/diff/2/?file=53009#file53009line495> > > > > We should probably check with Andreas Sandberg on this one. It looks > > like ctrInsts is already a cummulative stat for the KVM CPU. This might be > > required by the KVM CPU for fast-forwarding correctness? This could cause > > changes in KVM correctness and/or regressions (if any are maintained). > > Hopefully, it is harmless to allow the stat to reset, though? > > Lena Olson wrote: > I think it should be okay -- ctrInsts and numInsts both already existed > and I don't modify them, I just changed which is used by totalInsts(), which > looks like it never gets called by anything besides the stats stuff. Another > pair of eyes wouldn't hurt though.
This seems fine to me both ctrInsts and numInsts are incremented with the value from hwInstructions performance counter. - Alexandru ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3235/#review7866 ----------------------------------------------------------- On Jan. 6, 2016, 10:07 p.m., Lena Olson wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/3235/ > ----------------------------------------------------------- > > (Updated Jan. 6, 2016, 10:07 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 11230:374d79447577 > --------------------------- > stats: organize and clarify resettable stats > > Some stats (e.g. sim_insts) were traditionally not reset, because they were > intended for simulator-level measurement. However, some other stats (e.g. > sim_ticks) WERE reset. In addition, some derived stats used both reset and > unreset stats in the calculation, resulting in nonsense values. This patch > creates two sets of overall stats: one set that respects reset, and is useful > for measuring the simulated program, and one set that does not reset, useful > for > studying the simulator itself. The non-resettable stats are prefixed with > "simulator_", as they behave different from other stats. > > > Diffs > ----- > > src/arch/null/cpu_dummy.hh 021524c21cbc > src/cpu/BaseCPU.py 021524c21cbc > src/cpu/base.hh 021524c21cbc > src/cpu/checker/cpu.hh 021524c21cbc > src/cpu/kvm/base.hh 021524c21cbc > src/cpu/kvm/base.cc 021524c21cbc > src/cpu/minor/cpu.cc 021524c21cbc > src/cpu/o3/cpu.hh 021524c21cbc > src/cpu/o3/cpu.cc 021524c21cbc > src/cpu/simple/base.hh 021524c21cbc > src/cpu/simple/base.cc 021524c21cbc > src/sim/stat_control.hh 021524c21cbc > src/sim/stat_control.cc 021524c21cbc > > Diff: http://reviews.gem5.org/r/3235/diff/ > > > Testing > ------- > > > Thanks, > > Lena Olson > > _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
