Nate, so what mechanism are you envisioning to change the eventq pointer? It seems like we need a solution that modifies the Ruby objects' eventq pointers to point to a supplemental eventq during cache warmup and the main eventq during the main simulation loop.
Brad > -----Original Message----- > From: [email protected] [mailto:gem5-dev- > [email protected]] On Behalf Of nathan binkert > Sent: Tuesday, June 21, 2011 12:20 PM > To: gem5 Developer List > Subject: Re: [gem5-dev] [m5-dev] Ruby Cache Warmup > > > The idea of a second event queue is an interesting alternative. How easy is > it to point certain SimObjects at one event queue during one period of > execution and another event queue at a different period? > > Each SimObject is derived from EventManager and as a result has an eventq > pointer which it uses for scheduling. You can simply update this pointer. > Steve's code isn't actually necessary now that I think of it. > > Nate > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
