Another option would be to edit the progress interval code to dump and reset the stats every interval. You would just need to call the right functions on that event (Stats::dump() and Stats::reset() ???) The progress interval code should be in src/cpu/base.cc if I remember correctly.
OR, you could do what Ali suggests and add "m5.stats.reset()" right after the line "m5.stats.dump()". That is probably the easier route to take. 2012/1/14 马君 <[email protected]> > I've tried that. But as far as I know, -prog-inveral indicates committed > instructions, and how to modify a loop in "Simulation.py" using > prog_interval to dump stats.txt every <prog_interval>? > > > -----邮件原件----- > 发件人: [email protected] [mailto:[email protected]] 代 > 表 Mahmood Naderan > 发送时间: 2012年1月14日 0:49 > 收件人: gem5 users mailing list > 主题: Re: [gem5-users] 答复: How to dump stats.txt every fixed interval of > instructions in SE mod > > Have you tried "--prog-interval"? > Does that work for you? > > > On 1/13/12, Ali Saidi <[email protected]> wrote: > > The example below should work, but you'll need to call m5.stats.reset() > as > > well. > > > > Ali > > > > On Jan 12, 2012, at 7:12 PM, 马君 wrote: > > > >> As far as I know, prog_interval imply fixed ticks, how to dump by > >> instructions > >> Thanks > >> > >> 发件人: [email protected] [mailto:[email protected]] > 代表 > >> Korey Sewell > >> 发送时间: 2012年1月11日 23:50 > >> 收件人: gem5 users mailing list > >> 主题: Re: [gem5-users] How to dump stats.txt every fixed interval of > >> instructions in SE mode > >> > >> Check out configs/common/Options.py and then use the "progress interval" > >> option to dump and a fixed # of ticks for a duration of the simulation. > >> > >> 2012/1/11 马君 <[email protected]> > >> Hi gem5 users: > >> I’ve known how to dump stats.txt every fixed interval of ticks > >> with: > >> exit_event = m5.simulate() > >> But, when I use “for” loop to dump stats.txt based on the > number > >> of instructions, just like: > >> for n in range(100) > >> for i in xrange(np): > >> testsys.cpu[i].max_insts_any_thread = options.maxinsts > >> exit_event = m5.simulate() > >> m5.stats.dump() > >> I found that only the first interval data is correct. > >> Could anyone help me that? > >> > >> Jun > >> > >> _______________________________________________ > >> gem5-users mailing list > >> [email protected] > >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > >> > >> > >> > >> -- > >> - Korey > >> _______________________________________________ > >> gem5-users mailing list > >> [email protected] > >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > > > > -- > -- > // Naderan *Mahmood; > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- - Korey
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
