public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org,
	"Jouni Högander" <jouni.hogander@intel.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH v2 5/5] drm/i915/reset: Disable execlist per-engine reset for display reset tests
Date: Tue, 14 Apr 2026 18:56:19 +0300	[thread overview]
Message-ID: <351084abb7388df170677da2d4ad1e85841521db@intel.com> (raw)
In-Reply-To: <20260414142247.651-6-ville.syrjala@linux.intel.com>

On Tue, 14 Apr 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The display reset only happens from the full reset path. We must
> therefore force execlist submission to always take the full reset
> path and not the per-engine reset path. Currently the display
> reset tests are in fact not testing display resets at all on
> platforms using execlist submission. Ring submission and GuC
> submission always take the full path anyway.
>
> Also disable the engine reset inside __intel_gt_set_wedged() so
> that we simulate the intel_gt_gpu_reset_clobbers_display() behavior
> as closely as possible also when taking the full wedge path.
>
> The slight race between the separate intel_display_reset_test()
> calls in the overall reset path is harmless. kms_busy will keep
> the modparam fixed during the test, and even if someone were to
> fiddle with the modparam manually nothing bad should happen if
> the calls return different values.
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Jouni Högander <jouni.hogander@intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Not an expert here, but seems reasonable.

Acked-by: Jani Nikula <jani.nikula@intel.com>


> ---
>  drivers/gpu/drm/i915/gt/intel_reset.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
> index a1e6aaca8c9b..0b5f3fc58009 100644
> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
> @@ -967,6 +967,7 @@ static void nop_submit_request(struct i915_request *request)
>  
>  static void __intel_gt_set_wedged(struct intel_gt *gt)
>  {
> +	struct intel_display *display = gt->i915->display;
>  	struct intel_engine_cs *engine;
>  	intel_engine_mask_t awake;
>  	enum intel_engine_id id;
> @@ -984,7 +985,8 @@ static void __intel_gt_set_wedged(struct intel_gt *gt)
>  	awake = reset_prepare(gt);
>  
>  	/* Even if the GPU reset fails, it should still stop the engines */
> -	if (!intel_gt_gpu_reset_clobbers_display(gt))
> +	if (!intel_gt_gpu_reset_clobbers_display(gt) &&
> +	    !intel_display_reset_test(display))
>  		intel_gt_reset_all_engines(gt);
>  
>  	for_each_engine(engine, gt, id)
> @@ -1506,9 +1508,10 @@ void intel_gt_handle_error(struct intel_gt *gt,
>  
>  	/*
>  	 * Try engine reset when available. We fall back to full reset if
> -	 * single reset fails.
> +	 * single reset fails. Display reset test needs a full reset.
>  	 */
> -	if (!intel_uc_uses_guc_submission(&gt->uc) &&
> +	if (!intel_display_reset_test(gt->i915->display) &&
> +	    !intel_uc_uses_guc_submission(&gt->uc) &&
>  	    intel_has_reset_engine(gt) && !intel_gt_is_wedged(gt)) {
>  		local_bh_disable();
>  		for_each_engine_masked(engine, gt, engine_mask, tmp) {

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-04-14 15:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 14:22 [PATCH v2 0/5] drm/i915/reset: Expose "display_reset_count" in debugfs Ville Syrjala
2026-04-14 14:22 ` [PATCH v2 1/5] drm/i915/reset: Reorganize display reset code Ville Syrjala
2026-04-15  8:56   ` [PATCH v3 " Ville Syrjala
2026-04-14 14:22 ` [PATCH v2 2/5] drm/i915/reset: Move pending_fb_pin handling to i915 Ville Syrjala
2026-04-14 14:22 ` [PATCH v2 3/5] drm/xe/display: Add init_clock_gating.h stubs Ville Syrjala
2026-04-14 14:22 ` [PATCH v2 4/5] drm/i915/reset: Add "display_reset_count" debugfs file Ville Syrjala
2026-04-14 14:22 ` [PATCH v2 5/5] drm/i915/reset: Disable execlist per-engine reset for display reset tests Ville Syrjala
2026-04-14 15:56   ` Jani Nikula [this message]
2026-04-14 14:32 ` ✓ CI.KUnit: success for drm/i915/reset: Expose "display_reset_count" in debugfs (rev2) Patchwork
2026-04-14 15:40 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-14 17:07 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-15  9:05 ` ✓ CI.KUnit: success for drm/i915/reset: Expose "display_reset_count" in debugfs (rev3) Patchwork
2026-04-15 10:15 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-15 11:49 ` ✗ Xe.CI.FULL: 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=351084abb7388df170677da2d4ad1e85841521db@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jouni.hogander@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=ville.syrjala@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