Chris Wilson <[email protected]> writes: > [ text/plain ] > The get-reset-stats ioctls wasn't waiting for a pending reset before > reporting its statistics, and so was ignoring a hang generated by the > context that should have been reported against said context. > > Signed-off-by: Chris Wilson <[email protected]>
This is the fix we are looking for. And so blatantly obvious that I blame myself for walking past this yesterday. Testcase: igt/gem_reset_stats/reset_stats-* Tested-by: Mika Kuoppala <[email protected]> Reviewed-by: Mika Kuoppala <[email protected]> > --- > drivers/gpu/drm/i915/i915_gem_context.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/i915_gem_context.c > b/drivers/gpu/drm/i915/i915_gem_context.c > index f3c76ca6b411..2aedd188473d 100644 > --- a/drivers/gpu/drm/i915/i915_gem_context.c > +++ b/drivers/gpu/drm/i915/i915_gem_context.c > @@ -1056,7 +1056,7 @@ int i915_gem_context_reset_stats_ioctl(struct > drm_device *dev, > if (args->ctx_id == DEFAULT_CONTEXT_HANDLE && !capable(CAP_SYS_ADMIN)) > return -EPERM; > > - ret = mutex_lock_interruptible(&dev->struct_mutex); > + ret = i915_mutex_lock_interruptible(dev); > if (ret) > return ret; > > -- > 2.8.1 > > _______________________________________________ > Intel-gfx mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
