Hi Balaji, You're correct, it's ply called once. If you'd like to reschedule a repeating event, you'll need to do something to make that happen. Some possibilities include changing the LocalSimLoopExitEvent to re-schedule itself after it's executed, create a parameter that does this, or create a function that can be called in Python that does this.
Ali On Mar 24, 2013, at 2:29 AM, Balaji Soundararajan <[email protected]> wrote: > Hi, > > I am trying to dump out statistics after every quantum of instructions, and > as per the other posts I am using max_insts_any_thread in Simulation.py to > set the quantum size. > However, the stats are dumped only twice, once for the first quantum, and > second time for the rest of the program. > > print "****REAL SIMULATION****" > > np = options.num_cpus > for i in xrange(np): > testsys.cpu[i].max_insts_any_thread = options.maxinsts > //options.maxinsts=10 > exit_event = m5.simulate(maxtick - m5.curTick()) > //works for first 10 instructions > m5.stats.dump() > m5.stats.reset() > while exit_event.getCause() != "target called exit()": > exit_event = m5.simulate(maxtick - m5.curTick()) > //finishes the entire program > m5.stats.dump() > m5.stats.reset() > > As per my understanding, in base.cc, comInstEventQueue[tid]->schedule(event, > p->max_insts_any_thread) is called only once in the constructor. > Kindly tell me what I am missing here. > > The command I use to run the simulation is > build/ARM/gem5.debug configs/example/se.py -c > tests/test-progs/hello/bin/arm/linux/hello --cpu-type=detailed --caches > --l2cache --maxinsts=1 > > Thanks, > S. Balaji > _______________________________________________ > 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
