Re: [Intel-gfx] [PATCH v2] drm/i915: Actually flush interrupts on reset not just wedging

Chris Wilson writes: > Commit 0f36a85c3bd5 ("drm/i915: Flush pending interrupt following a GPU > reset") got confused and only applied the flush to the set-wedge path > (which itself is proving troublesome), but we also need the > serialisation on the regular reset path. Oops. > > Move the interr

Re: [Intel-gfx] [PATCH v2] drm/i915: Actually flush interrupts on reset not just wedging

Quoting Mika Kuoppala (2018-03-23 10:53:00) > Chris Wilson writes: > > > Commit 0f36a85c3bd5 ("drm/i915: Flush pending interrupt following a GPU > > reset") got confused and only applied the flush to the set-wedge path > > (which itself is proving troublesome), but we also need the > > serialisat

Re: [Intel-gfx] [PATCH v2] drm/i915: Actually flush interrupts on reset not just wedging

Chris Wilson writes: > Commit 0f36a85c3bd5 ("drm/i915: Flush pending interrupt following a GPU > reset") got confused and only applied the flush to the set-wedge path > (which itself is proving troublesome), but we also need the > serialisation on the regular reset path. Oops. > > Move the interr

[Intel-gfx] [PATCH v2] drm/i915: Actually flush interrupts on reset not just wedging

Commit 0f36a85c3bd5 ("drm/i915: Flush pending interrupt following a GPU reset") got confused and only applied the flush to the set-wedge path (which itself is proving troublesome), but we also need the serialisation on the regular reset path. Oops. Move the interrupt into reset_irq() and make it c