Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/i915/dg2: Drop pre-production GT workarounds
Date: Tue, 15 Aug 2023 10:50:59 -0700	[thread overview]
Message-ID: <874jl0tcsc.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230815173611.142687-9-matthew.d.roper@intel.com>

On Tue, 15 Aug 2023 10:36:15 -0700, Matt Roper wrote:
>

Hi Matt,

> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index 04bc1f4a1115..eadbfd2fb9e5 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -3381,25 +3381,6 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
>	intel_engine_pm_get(stream->engine);
>	intel_uncore_forcewake_get(stream->uncore, FORCEWAKE_ALL);
>
> -	/*
> -	 * Wa_16011777198:dg2: GuC resets render as part of the Wa. This causes
> -	 * OA to lose the configuration state. Prevent this by overriding GUCRC
> -	 * mode.
> -	 */
> -	if (intel_uc_uses_guc_rc(&gt->uc) &&
> -	    (IS_DG2_GRAPHICS_STEP(gt->i915, G10, STEP_A0, STEP_C0) ||
> -	     IS_DG2_GRAPHICS_STEP(gt->i915, G11, STEP_A0, STEP_B0))) {
> -		ret = intel_guc_slpc_override_gucrc_mode(&gt->uc.guc.slpc,
> -							 SLPC_GUCRC_MODE_GUCRC_NO_RC6);
> -		if (ret) {
> -			drm_dbg(&stream->perf->i915->drm,
> -				"Unable to override gucrc mode\n");
> -			goto err_gucrc;
> -		}
> -
> -		stream->override_gucrc = true;
> -	}
> -
>	ret = alloc_oa_buffer(stream);
>	if (ret)
>		goto err_oa_buf_alloc;
> @@ -3439,7 +3420,6 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
>	if (stream->override_gucrc)
>		intel_guc_slpc_unset_gucrc_mode(&gt->uc.guc.slpc);
>
> -err_gucrc:
>	intel_uncore_forcewake_put(stream->uncore, FORCEWAKE_ALL);
>	intel_engine_pm_put(stream->engine);
>

If we are deleting this, let's basically remove all references to "gucrc"
in this file and includes. So:

* clean up the error path
* Remove stream->override_gucrc
* clean up i915_oa_stream_destroy

Maybe the functions intel_guc_slpc_unset_gucrc_mode and
intel_guc_slpc_override_gucrc_mode can also be removed.

Let's wait to hear from Umesh/Vinay (Cc'd) who implemented this stuff.

Thanks.
--
Ashutosh

  reply	other threads:[~2023-08-15 17:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 17:36 [Intel-gfx] [PATCH 0/4] Drop support for pre-production DG2 hardware Matt Roper
2023-08-15 17:36 ` [Intel-gfx] [PATCH 1/4] drm/i915/dg2: Recognize pre-production hardware Matt Roper
2023-08-16 18:08   ` Matt Atwood
2023-08-15 17:36 ` [Intel-gfx] [PATCH 2/4] drm/i915/dg2: Drop pre-production display workarounds Matt Roper
2023-08-16 18:14   ` Matt Atwood
2023-08-15 17:36 ` [Intel-gfx] [PATCH 3/4] drm/i915/dg2: Drop pre-production GT workarounds Matt Roper
2023-08-15 17:50   ` Dixit, Ashutosh [this message]
2023-08-15 17:36 ` [Intel-gfx] [PATCH 4/4] drm/i915: Tidy workaround definitions Matt Roper
2023-08-16 20:07   ` Matt Atwood
2023-08-15 19:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Drop support for pre-production DG2 hardware Patchwork
2023-08-15 19:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-15 19:27 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-16  9:11 ` [Intel-gfx] [PATCH 0/4] " Jani Nikula

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=874jl0tcsc.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-gfx@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