> I don't really know anything about the situation here, The problem is that threads activations/deactivation needs to happen after the tick event. Typically, a CPU event will happen to do this and as long as the CPU's Tick event has been scheduled before the activation/deactivation event then we're fine. But, if were activating threads because of some pipeline event (e.g. after a cache miss) then we need to enforce that the correct ordering takes place.
> but is it > possible to just call a function to take care of the thread activation > at the end of the tick event? I'm making the assumption that every time > a thread is activated a tick should have already happened for that instant. > That's probably the right assumption, although checking to see if there are threads ready to activate/deactivate at the end of every Tick defeats the purpose of having an event to do this for you when the time is right, no? -- - Korey
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
