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, dri-devel@lists.freedesktop.org,
Simona Vetter <simona.vetter@ffwll.ch>,
Christian König <christian.koenig@amd.com>,
Jouni Högander <jouni.hogander@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH 2/6] drm/i915/reset: Reorganize display reset code
Date: Thu, 09 Apr 2026 11:13:43 +0300 [thread overview]
Message-ID: <1faaaf6e482716344c969a1a14582b063ab801be@intel.com> (raw)
In-Reply-To: <20260408233458.22666-3-ville.syrjala@linux.intel.com>
On Thu, 09 Apr 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Stop returning the "is there a display?" status from
> intel_display_reset_prepare(). I plan to move the pending_fb_pin
> into the i915 code, so I need to make that determination already
> before intel_display_reset_prepare() is called. Add a new
> intel_display_reset_supported() function for that.
>
> Cc: Simona Vetter <simona.vetter@ffwll.ch>
> Cc: Christian König <christian.koenig@amd.com>
> 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>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> .../drm/i915/display/intel_display_reset.c | 23 ++++++++-----------
> .../drm/i915/display/intel_display_reset.h | 3 ++-
> drivers/gpu/drm/i915/gt/intel_reset.c | 13 +++++++----
> 3 files changed, 20 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_reset.c b/drivers/gpu/drm/i915/display/intel_display_reset.c
> index d00ef5bdcbda..137a2a33c8b0 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_reset.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_reset.c
> @@ -16,22 +16,24 @@
> #include "intel_hotplug.h"
> #include "intel_pps.h"
>
> +bool intel_display_reset_supported(struct intel_display *display)
> +{
> + return HAS_DISPLAY(display);
> +}
> +
> bool intel_display_reset_test(struct intel_display *display)
> {
> - return display->params.force_reset_modeset_test;
> + return HAS_DISPLAY(display) &&
> + display->params.force_reset_modeset_test;
> }
>
> -/* returns true if intel_display_reset_finish() needs to be called */
> -bool intel_display_reset_prepare(struct intel_display *display,
> +void intel_display_reset_prepare(struct intel_display *display,
> modeset_stuck_fn modeset_stuck, void *context)
> {
> struct drm_modeset_acquire_ctx *ctx = &display->restore.reset_ctx;
> struct drm_atomic_state *state;
> int ret;
>
> - if (!HAS_DISPLAY(display))
> - return false;
> -
> if (atomic_read(&display->restore.pending_fb_pin)) {
> drm_dbg_kms(display->drm,
> "Modeset potentially stuck, unbreaking through wedging\n");
> @@ -60,7 +62,7 @@ bool intel_display_reset_prepare(struct intel_display *display,
> ret = PTR_ERR(state);
> drm_err(display->drm, "Duplicating state failed with %i\n",
> ret);
> - return true;
> + return;
> }
>
> ret = drm_atomic_helper_disable_all(display->drm, ctx);
> @@ -68,13 +70,11 @@ bool intel_display_reset_prepare(struct intel_display *display,
> drm_err(display->drm, "Suspending crtc's failed with %i\n",
> ret);
> drm_atomic_state_put(state);
> - return true;
> + return;
> }
>
> display->restore.modeset_state = state;
> state->acquire_ctx = ctx;
> -
> - return true;
> }
>
> void intel_display_reset_finish(struct intel_display *display, bool test_only)
> @@ -83,9 +83,6 @@ void intel_display_reset_finish(struct intel_display *display, bool test_only)
> struct drm_atomic_state *state;
> int ret;
>
> - if (!HAS_DISPLAY(display))
> - return;
> -
> state = fetch_and_zero(&display->restore.modeset_state);
> if (!state)
> goto unlock;
> diff --git a/drivers/gpu/drm/i915/display/intel_display_reset.h b/drivers/gpu/drm/i915/display/intel_display_reset.h
> index 8b3bda134454..e0f15e757728 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_reset.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_reset.h
> @@ -12,8 +12,9 @@ struct intel_display;
>
> typedef void modeset_stuck_fn(void *context);
>
> +bool intel_display_reset_supported(struct intel_display *display);
> bool intel_display_reset_test(struct intel_display *display);
> -bool intel_display_reset_prepare(struct intel_display *display,
> +void intel_display_reset_prepare(struct intel_display *display,
> modeset_stuck_fn modeset_stuck, void *context);
> void intel_display_reset_finish(struct intel_display *display, bool test_only);
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
> index 37272871b0f2..ffd11767874f 100644
> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
> @@ -1425,16 +1425,19 @@ static void intel_gt_reset_global(struct intel_gt *gt,
> bool need_display_reset;
> bool reset_display;
>
> - need_display_reset = intel_gt_gpu_reset_clobbers_display(gt) &&
> + need_display_reset =
> + intel_display_reset_supported(display) &&
> + intel_gt_gpu_reset_clobbers_display(gt) &&
> intel_has_gpu_reset(gt);
>
> - reset_display = intel_display_reset_test(display) ||
> + reset_display =
> + intel_display_reset_test(display) ||
> need_display_reset;
>
> if (reset_display)
> - reset_display = intel_display_reset_prepare(display,
> - display_reset_modeset_stuck,
> - gt);
> + intel_display_reset_prepare(display,
> + display_reset_modeset_stuck,
> + gt);
>
> intel_gt_reset(gt, engine_mask, reason);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-09 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 23:34 [PATCH 0/6] drm/i915/reset: Solve display vs. GPU reset deadlock, again Ville Syrjala
2026-04-08 23:34 ` [PATCH 1/6] dma-buf: Remove old lies about dma_fence_wait_any_timeout() not accepting some fences Ville Syrjala
2026-04-09 8:09 ` Jani Nikula
2026-04-09 10:39 ` Christian König
2026-04-12 2:04 ` Claude review: " Claude Code Review Bot
2026-04-08 23:34 ` [PATCH 2/6] drm/i915/reset: Reorganize display reset code Ville Syrjala
2026-04-09 8:13 ` Jani Nikula [this message]
2026-04-12 2:04 ` Claude review: " Claude Code Review Bot
2026-04-08 23:34 ` [PATCH 3/6] drm/i915/reset: Move pending_fb_pin handling to i915 Ville Syrjala
2026-04-09 8:17 ` Jani Nikula
2026-04-12 2:04 ` Claude review: " Claude Code Review Bot
2026-04-08 23:34 ` [PATCH 4/6] drm/xe/display: Add init_clock_gating.h stubs Ville Syrjala
2026-04-09 8:19 ` Jani Nikula
2026-04-12 2:04 ` Claude review: " Claude Code Review Bot
2026-04-08 23:34 ` [PATCH 5/6] drm/i915/reset: Handle the display vs. GPU reset deadlock using a custom dma-fence Ville Syrjala
2026-04-09 10:37 ` Jani Nikula
2026-04-09 10:46 ` Christian König
2026-04-09 11:19 ` Ville Syrjälä
2026-04-09 12:17 ` Christian König
2026-04-12 2:04 ` Claude review: " Claude Code Review Bot
2026-04-08 23:34 ` [PATCH 6/6] drm/i915/display: Make fence timeout infinite Ville Syrjala
2026-04-09 10:51 ` Jani Nikula
2026-04-12 2:04 ` Claude review: " Claude Code Review Bot
2026-04-12 2:04 ` Claude review: drm/i915/reset: Solve display vs. GPU reset deadlock, again Claude Code Review Bot
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=1faaaf6e482716344c969a1a14582b063ab801be@intel.com \
--to=jani.nikula@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=simona.vetter@ffwll.ch \
--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