On Wed, Oct 14, 2009 at 5:10 PM, nathan binkert <[email protected]> wrote: >> + reschedule(tickEvent, curTick + tickEvent.when()); > > This seems pretty suspect to me. Generally, when we unserialize > events, we first serialize the event time and then schedule it later. > In fact, the way that the existing event reschedule is happening is > likely not correct since it will cause a hiccup in the interval. > Check out how ns_gige.cc serializes transmitTick and replicate it for > both event and tickEvent this will ensure that the events are > serialized and unserialized properly.
Yea, Brad and I have been hashing through this together and we figured that out already. > Let me know how things work out (and please commit a patch if it does). Will do... still tracking down the second bug and trying to figure out if it's related or not. Steve _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
