Re: [Intel-gfx] [PATCH] drm/i915: Look for active requests earlier in the reset path

2017-05-18 Thread Michel Thierry
On 5/18/2017 2:16 PM, Chris Wilson wrote: On Thu, May 18, 2017 at 02:11:15PM -0700, Michel Thierry wrote: And store the active request so that we only search for it once; this applies for reset-engine and full reset. v2: Check for request completion inside _prepare_engine, don't use ECANCELED,

Re: [Intel-gfx] [PATCH] drm/i915: Look for active requests earlier in the reset path

2017-05-18 Thread Chris Wilson
On Thu, May 18, 2017 at 02:11:15PM -0700, Michel Thierry wrote: > And store the active request so that we only search for it once; this > applies for reset-engine and full reset. > > v2: Check for request completion inside _prepare_engine, don't use > ECANCELED, remove unnecessary null checks

[Intel-gfx] [PATCH] drm/i915: Look for active requests earlier in the reset path

2017-05-18 Thread Michel Thierry
And store the active request so that we only search for it once; this applies for reset-engine and full reset. v2: Check for request completion inside _prepare_engine, don't use ECANCELED, remove unnecessary null checks (Chris). v3: Capture active requests during reset_prepare and store it the

Re: [Intel-gfx] [PATCH] drm/i915: Look for active requests earlier in the reset path

2017-05-18 Thread Chris Wilson
On Thu, May 18, 2017 at 11:22:57AM -0700, Michel Thierry wrote: > And store the active request so that we only search for it once; this > applies for reset-engine and full reset. > > v2: Check for request completion inside _prepare_engine, don't use > ECANCELED, remove unnecessary null checks

Re: [Intel-gfx] [PATCH] drm/i915: Look for active requests earlier in the reset path

2017-05-18 Thread Michel Thierry
On 5/18/2017 11:22 AM, Michel Thierry wrote: fixes Signed-off-by: Michel Thierry rebase mistake ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Intel-gfx] [PATCH] drm/i915: Look for active requests earlier in the reset path

2017-05-18 Thread Michel Thierry
And store the active request so that we only search for it once; this applies for reset-engine and full reset. v2: Check for request completion inside _prepare_engine, don't use ECANCELED, remove unnecessary null checks (Chris). v3: Capture active requests during reset_prepare and store it the