path: root/drivers/gpu/drm/i915/selftests/i915_gem_object.c
diff options
authorChris Wilson <>2019-02-20 14:56:37 +0000
committerChris Wilson <>2019-02-20 16:31:08 +0000
commitc41166f9a145f1c4ce2961b338f9b57495ace4b5 (patch)
tree137e4dc4097be291198f44c822469ae4804ae751 /drivers/gpu/drm/i915/selftests/i915_gem_object.c
parent47ed55a9bb9e284d46d6f2489e32a53b59152809 (diff)
drm/i915: Beware temporary wedging when determining -EIO
At a few points in our uABI, we check to see if the driver is wedged and report -EIO back to the user in that case. However, as we perform the check and reset asynchronously (where once before they were both serialised by the struct_mutex), we may instead see the temporary wedging used to cancel inflight rendering to avoid a deadlock during reset (caused by either us timing out in our reset handler, i915_wedge_on_timeout or with malice aforethought in intel_reset_prepare for a stuck modeset). If we suspect this is the case, that is we see a wedged driver *and* reset in progress, then wait until the reset is resolved before reporting upon the wedged status. v2: might_sleep() (Mika) Bugzilla: Signed-off-by: Chris Wilson <> Cc: Mika Kuoppala <> Reviewed-by: Mika Kuoppala <> Link:
Diffstat (limited to 'drivers/gpu/drm/i915/selftests/i915_gem_object.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/gpu/drm/i915/selftests/i915_gem_object.c b/drivers/gpu/drm/i915/selftests/i915_gem_object.c
index 395ae878e0f7..784982aed625 100644
--- a/drivers/gpu/drm/i915/selftests/i915_gem_object.c
+++ b/drivers/gpu/drm/i915/selftests/i915_gem_object.c
@@ -583,7 +583,7 @@ static int igt_mmap_offset_exhaustion(void *arg)
for (loop = 0; loop < 3; loop++) {
intel_wakeref_t wakeref;
- if (i915_terminally_wedged(&i915->gpu_error))
+ if (i915_terminally_wedged(i915))
obj = i915_gem_object_create_internal(i915, PAGE_SIZE);