* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux
>
> 1. The first stage of the pipeline should not process the stage when a
> drainPending flag is set (or should this be associated specifically
> with the fetch logic?)
>
This sounds good. There is already a "checkSignals" type function in the
pipeline stage definition that you may be able to play
Thanks for the overview, Ali. It helped a lot. Draining is definitely
the trickier thing.
This is my understanding of the flow in O3:
1. When drain() is called, it sets the "drainPending" flag to TRUE
following which the fetch stage does not fetch any instructions.
2. Subsequently, when all the
This was another patch that I forgot about (I had a lot going on before
Christmas and in January - sorry). Can I assume that it's ok to commit
this one too?
Just a note about this - I don't have the EIO regressions running so can't
update the stats for these. Can someone else do it once I'
Hi everyone,
I just realised that I didn't ever actually commit these patches. Does
anyone have any problems with them, or can I go ahead? I know it's ISCA
rebuttal period, so no rush (it's been a month and a half anyhow, I'm sure
a little longer won't hurt!)
Cheers
Tim
On Mon, 14 Dec 20
