> Whether there's an interrupt available is already tracked by ISA > dependent code by the Interrupts object which lives at commit. Why does > fetch need to know? Anything it fetches is just going to get blown away > anyway.
The point is, you want to redirect fetch intelligently. When there is an interrupt, you just want to insert it into the instruction stream (like an asynchronous branch), not treat it like an exception. If you treat it like an exception, as you say, you blow a lot of useful work away. There's no reason to do this with an interrupt. Interrupts are already expensive operations. It would not be good to unreasonably make them more expensive (especially if real machines don't). Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
