From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Wait for reset to complete before returning from debugfs/i915_wedged
Date: Thu, 16 Mar 2017 18:38:09 +0200 [thread overview]
Message-ID: <87a88l18jy.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20170315140129.19175-4-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Provide some serialisation between user operations by waiting for the
> reset initiated by setting i915_wedged to complete.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 5fdf8c137235..ada823815b8a 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -4129,6 +4129,10 @@ i915_wedged_set(void *data, u64 val)
> i915_handle_error(dev_priv, val,
> "Manually setting wedged to %llu", val);
>
> + wait_on_bit(&dev_priv->gpu_error.flags,
> + I915_RESET_HANDOFF,
> + TASK_UNINTERRUPTIBLE);
> +
But what happens here if we have already prevented the reset and
the handoff never clears? Seems like it is a stuck task as the
handoff is not cleared on error path in i915_reset.
-Mika
> return 0;
> }
>
> --
> 2.11.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-16 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 14:01 [PATCH 1/4] drm/i915: Split I915_RESET_IN_PROGRESS into two flags Chris Wilson
2017-03-15 14:01 ` [PATCH 2/4] drm/i915: Move engine->submit_request selection to a vfunc Chris Wilson
2017-03-15 14:01 ` [PATCH 3/4] drm/i915: Restore engine->submit_request before unwedging Chris Wilson
2017-03-15 14:01 ` [PATCH 4/4] drm/i915: Wait for reset to complete before returning from debugfs/i915_wedged Chris Wilson
2017-03-16 16:38 ` Mika Kuoppala [this message]
2017-03-16 17:01 ` Chris Wilson
2017-03-16 17:02 ` Mika Kuoppala
2017-03-15 15:10 ` ✗ Fi.CI.BAT: warning for series starting with [1/4] drm/i915: Split I915_RESET_IN_PROGRESS into two flags Patchwork
2017-03-16 16:18 ` [PATCH 1/4] " Mika Kuoppala
2017-03-16 16:47 ` Mika Kuoppala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a88l18jy.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.