On Wed, Nov 10, 2010 at 9:31 AM, Ali Saidi <[email protected]> wrote: > On Wed, 10 Nov 2010 08:01:37 -0800, Steve Reinhardt <[email protected]> > wrote: > > Pardon my naivete, but what does the "delayed commit" flag do? > > On Mon, Nov 8, 2010 at 11:58 AM, Ali Saidi <[email protected]> wrote: > >> changeset ba11187e2582 in /z/repo/m5 >> details: http://repo.m5sim.org/m5?cmd=changeset;node=ba11187e2582 >> description: >> ARM: Make all ARM uops delayed commit. > > Really, it should be all non-lastuop uops delayed commit, but it tells > the cpu model that it the uop can't be committed until all uops in the op > are complete. In terms of the simple cpu it prevents an interrupt from > occurring mid-uop. >
As you imply, why isn't this the default behavior? I can see having a special flag for the occasional case where a macroinstruction is interruptible other than at the end of the instruction, but this seems backwards. Steve
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
