Where is that code? Is it an asisa specific thing? I'm pretty sure I got this stuff working properly.
Basically the model now is that you create an event and you schedule it on an event queue. So, you'd do e = m5.event.create(self) m5.event.mainq.schedule(e, m5.curTick() + self.period) m5.event.create() is designed to wrap an existing class or function and call __call__ on it when the event is processed. Now there is a m5.event.Event class that is slightly better way to do things. You derive from m5.event.Event, and implement __call__. Then call m5.event.mainq.schedule() on an instantiation of that event. Nate On Tue, Oct 14, 2008 at 3:00 PM, Rick Strong <[EMAIL PROTECTED]> wrote: > A similar problem occurs for scripts that use > m5.internal.event.create(self, m5.curTick() + self.period) stating that > 'module' object has no attribute 'create'. Perhaps a swig function is > missing? > > Best, > -Rick > > nathan binkert wrote: >> Shoot. Good catch. I forgot about that. Not all checkpoints are >> going to be affected by this, but indeed some are. You can comment >> out the panic and after it, put: >> mainEventQueue->schedule(_when); >> >> This problem arises from the fact that events don't know which queue >> they're supposed to be scheduled on and in the future, there will be >> more than one event queue to choose from. I'll try to fix this for >> real as soon as I can. >> >> Nate >> >> On Tue, Oct 14, 2008 at 12:20 PM, Rick Strong <[EMAIL PROTECTED]> wrote: >> >>> Hi, >>> >>> I am attempting to resume checkpoints in full system mode in scripts >>> that previously worked, but notice that the resume from checkpoint is >>> failing with: >>> >>> panic: need to figure out how to unserialize scheduled events >>> >>> Are checkpoints broken with the new eventq? >>> >>> Best, >>> -Rick >>> >>> _______________________________________________ >>> m5-dev mailing list >>> [email protected] >>> http://m5sim.org/mailman/listinfo/m5-dev >>> >>> >>> >> _______________________________________________ >> m5-dev mailing list >> [email protected] >> http://m5sim.org/mailman/listinfo/m5-dev >> >> > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
