[Intel-gfx] [PATCH 12/12] drm/i915: Don't force serialisation on marking up execlists irq posted

Since we coordinate with the execlists tasklet using a locked schedule operation that ensures that after we set the engine->irq_posted we always have an invocation of the tasklet, we do not need to use a locked operation to set the engine->irq_posted itself. Signed-off-by: Chris Wilson --- drive

Re: [Intel-gfx] [PATCH 12/12] drm/i915: Don't force serialisation on marking up execlists irq posted

Chris Wilson writes: > Since we coordinate with the execlists tasklet using a locked schedule > operation that ensures that after we set the engine->irq_posted we > always have an invocation of the tasklet, we do not need to use a locked > operation to set the engine->irq_posted itself. > > Signe

Re: [Intel-gfx] [PATCH 12/12] drm/i915: Don't force serialisation on marking up execlists irq posted

On 11/05/2017 20:59, Chris Wilson wrote: Since we coordinate with the execlists tasklet using a locked schedule operation that ensures that after we set the engine->irq_posted we always have an invocation of the tasklet, we do not need to use a locked operation to set the engine->irq_posted itse