intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH v2 4/8] drm/i915/reset: add intel_display_reset_test()
Date: Tue, 25 Feb 2025 13:16:54 +0200	[thread overview]
Message-ID: <87tt8i5l5l.fsf@intel.com> (raw)
In-Reply-To: <1e92734af3c4ab75b487e5f8ef891acee53de9bf.1740481927.git.jani.nikula@intel.com>

On Tue, 25 Feb 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> Add a helper for checking if we want to test display reset regardless of
> whether it's strictly necessary. This will come in handy in follow-up
> work where we want to check this from gt reset side.
>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display_reset.c | 8 ++++++--
>  drivers/gpu/drm/i915/display/intel_display_reset.h | 3 +++
>  2 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_reset.c b/drivers/gpu/drm/i915/display/intel_display_reset.c
> index cef9536c461c..b7962f90c21c 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_reset.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_reset.c
> @@ -22,6 +22,11 @@ static bool gpu_reset_clobbers_display(struct intel_display *display)
>  		intel_has_gpu_reset(to_gt(i915)));
>  }
>  
> +bool intel_display_reset_test(struct intel_display *display)
> +{
> +	return display->params.force_reset_modeset_test;
> +}
> +
>  void intel_display_reset_prepare(struct intel_display *display)
>  {
>  	struct drm_i915_private *dev_priv = to_i915(display->drm);
> @@ -33,7 +38,7 @@ void intel_display_reset_prepare(struct intel_display *display)
>  		return;
>  
>  	/* reset doesn't touch the display */
> -	if (!display->params.force_reset_modeset_test &&
> +	if (!intel_display_reset_test(display) &&
>  	    !gpu_reset_clobbers_display(display))
>  		return;
>  
> @@ -41,7 +46,6 @@ void intel_display_reset_prepare(struct intel_display *display)
>  	set_bit(I915_RESET_MODESET, &to_gt(dev_priv)->reset.flags);
>  	smp_mb__after_atomic();
>  	wake_up_bit(&to_gt(dev_priv)->reset.flags, I915_RESET_MODESET);
> -

Gah, a rebase fail.

>  	if (atomic_read(&display->restore.pending_fb_pin)) {
>  		drm_dbg_kms(display->drm,
>  			    "Modeset potentially stuck, unbreaking through wedging\n");
> diff --git a/drivers/gpu/drm/i915/display/intel_display_reset.h b/drivers/gpu/drm/i915/display/intel_display_reset.h
> index 9a1fe99bfcd4..c1dd2e8d0914 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_reset.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_reset.h
> @@ -6,8 +6,11 @@
>  #ifndef __INTEL_RESET_H__
>  #define __INTEL_RESET_H__
>  
> +#include <linux/types.h>
> +
>  struct intel_display;
>  
> +bool intel_display_reset_test(struct intel_display *display);
>  void intel_display_reset_prepare(struct intel_display *display);
>  void intel_display_reset_finish(struct intel_display *display);

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-02-25 11:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 11:14 [PATCH v2 0/8] drm/i915: display reset cleanups Jani Nikula
2025-02-25 11:14 ` [PATCH v2 1/8] drm/i915/display: convert display reset to struct intel_display * Jani Nikula
2025-02-25 11:14 ` [PATCH v2 2/8] drm/i915: move pending_fb_pin to struct intel_display Jani Nikula
2025-02-25 11:14 ` [PATCH v2 3/8] drm/i915/reset: add intel_gt_gpu_reset_clobbers_display() helper Jani Nikula
2025-02-25 11:14 ` [PATCH v2 4/8] drm/i915/reset: add intel_display_reset_test() Jani Nikula
2025-02-25 11:16   ` Jani Nikula [this message]
2025-02-25 20:14   ` Matt Roper
2025-02-25 11:14 ` [PATCH v2 5/8] drm/i915/reset: add wrappers for display reset calls Jani Nikula
2025-02-25 20:15   ` Matt Roper
2025-02-25 11:14 ` [PATCH v2 6/8] drm/i915/reset: move gt related stuff out of display reset Jani Nikula
2025-02-25 20:35   ` Matt Roper
2025-02-26 10:38     ` Jani Nikula
2025-02-26 23:46       ` Matt Roper
2025-03-03 11:29         ` Jani Nikula
2025-02-25 11:14 ` [PATCH v2 7/8] drm/i915/reset: pass test only parameter to intel_display_reset_finish() Jani Nikula
2025-02-25 20:37   ` Matt Roper
2025-02-25 11:14 ` [PATCH v2 8/8] drm/i915/reset: add modeset_stuck callback to intel_display_reset_prepare() Jani Nikula
2025-02-25 20:39   ` Matt Roper
2025-02-25 12:50 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: display reset cleanups (rev2) Patchwork
2025-02-25 12:50 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-02-25 13:10 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-25 15:56 ` ✗ i915.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=87tt8i5l5l.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@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;
as well as URLs for NNTP newsgroup(s).