From: Matthew Auld <matthew.auld@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3] drm/i915: Skip error capture when wedged on init
Date: Fri, 12 Nov 2021 15:44:03 +0000 [thread overview]
Message-ID: <231e81f0-765b-9ebf-ffd6-067f245f3a46@intel.com> (raw)
In-Reply-To: <20211111130634.266098-1-tvrtko.ursulin@linux.intel.com>
On 11/11/2021 13:06, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Trying to capture uninitialised engines when we wedged on init ends in
> tears. Skip that together with uC capture, since failure to initialise the
> latter can actually be one of the reasons for wedging on init.
>
> v2:
> * Use i915_disable_error_state when wedging on init/fini.
>
> v3:
> * Handle mock tests.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com> # v1
Assuming this works locally, r-b still stands.
> ---
> drivers/gpu/drm/i915/gt/intel_reset.c | 2 ++
> drivers/gpu/drm/i915/selftests/mock_gem_device.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
> index 51b56b8e5003..0fbd6dbadce7 100644
> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
> @@ -1448,6 +1448,7 @@ void intel_gt_set_wedged_on_init(struct intel_gt *gt)
> BUILD_BUG_ON(I915_RESET_ENGINE + I915_NUM_ENGINES >
> I915_WEDGED_ON_INIT);
> intel_gt_set_wedged(gt);
> + i915_disable_error_state(gt->i915, -ENODEV);
> set_bit(I915_WEDGED_ON_INIT, >->reset.flags);
>
> /* Wedged on init is non-recoverable */
> @@ -1457,6 +1458,7 @@ void intel_gt_set_wedged_on_init(struct intel_gt *gt)
> void intel_gt_set_wedged_on_fini(struct intel_gt *gt)
> {
> intel_gt_set_wedged(gt);
> + i915_disable_error_state(gt->i915, -ENODEV);
> set_bit(I915_WEDGED_ON_FINI, >->reset.flags);
> intel_gt_retire_requests(gt); /* cleanup any wedged requests */
> }
> diff --git a/drivers/gpu/drm/i915/selftests/mock_gem_device.c b/drivers/gpu/drm/i915/selftests/mock_gem_device.c
> index 9ab3f284d1dd..d0e2e61de8d4 100644
> --- a/drivers/gpu/drm/i915/selftests/mock_gem_device.c
> +++ b/drivers/gpu/drm/i915/selftests/mock_gem_device.c
> @@ -177,6 +177,8 @@ struct drm_i915_private *mock_gem_device(void)
>
> mock_uncore_init(&i915->uncore, i915);
>
> + spin_lock_init(&i915->gpu_error.lock);
> +
> i915_gem_init__mm(i915);
> intel_gt_init_early(&i915->gt, i915);
> atomic_inc(&i915->gt.wakeref.count); /* disable; no hw support */
>
next prev parent reply other threads:[~2021-11-12 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 11:43 [Intel-gfx] [PATCH v2] drm/i915: Skip error capture when wedged on init Tvrtko Ursulin
2021-11-10 15:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Skip error capture when wedged on init (rev2) Patchwork
2021-11-10 19:09 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-11 13:06 ` [Intel-gfx] [PATCH v3] drm/i915: Skip error capture when wedged on init Tvrtko Ursulin
2021-11-12 15:44 ` Matthew Auld [this message]
2021-11-11 14:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Skip error capture when wedged on init (rev3) Patchwork
2021-11-11 18:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=231e81f0-765b-9ebf-ffd6-067f245f3a46@intel.com \
--to=matthew.auld@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox