On Wed, Oct 21, 2015 at 7:04 PM, Jason Ekstrand wrote:
> I'm not 100% sure if this actually matches the hardware. It's
> possible that some of the issue time is used to determine interference
> and do the thread switch in which case, there may be some overlap.
> However, it's definitely better th
I'm not 100% sure if this actually matches the hardware. It's
possible that some of the issue time is used to determine interference
and do the thread switch in which case, there may be some overlap.
However, it's definitely better than what we had before since, before,
issue time would get comple
The issue time for an instruction is how many cycles it takes to
actually put it into the pipeline. If there's a pipeline stall that
causes the instruction to be delayed, we should first take that into
account to figure out when the instruction would start executing and
*then* add the issue time. T
