Commit be90e344 authored by Chris Wilson's avatar Chris Wilson

drm/i915/gt: Cancel banned contexts after GT reset

As we started marking the ce->gem_context as NULL on closure, we can no
longer use that to carry closure information. Instead, we can look at
whether the context was killed on closure instead.

Fixes: 130a95e9 ("drm/i915/gem: Consolidate ctx->engines[] release")
Closes: https://gitlab.freedesktop.org/drm/intel/issues/1379Signed-off-by: default avatarChris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: default avatarMika Kuoppala <mika.kuoppala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200304165113.2449213-1-chris@chris-wilson.co.uk
parent 8f1e5740
...@@ -94,13 +94,7 @@ static bool mark_guilty(struct i915_request *rq) ...@@ -94,13 +94,7 @@ static bool mark_guilty(struct i915_request *rq)
ctx = NULL; ctx = NULL;
rcu_read_unlock(); rcu_read_unlock();
if (!ctx) if (!ctx)
return false; return intel_context_is_banned(rq->context);
if (i915_gem_context_is_closed(ctx)) {
intel_context_set_banned(rq->context);
banned = true;
goto out;
}
atomic_inc(&ctx->guilty_count); atomic_inc(&ctx->guilty_count);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment