All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Ensure wa_init_finish() is called for ctx workaround list
Date: Thu, 26 Aug 2021 09:26:31 +0100	[thread overview]
Message-ID: <c824c665-0a49-e112-9134-97edeab3b8a4@linux.intel.com> (raw)
In-Reply-To: <20210826033559.1209020-1-matthew.d.roper@intel.com>


On 26/08/2021 04:35, Matt Roper wrote:
> A recent restructuring of our context workaround list initialization
> added an early return for non-render engines; this caused us to
> potentially miss the wa_init_finish() call at the end of the function.
> The mistake is pretty harmless --- the only impact is that non-render
> engines on graphics version 12.50+ platforms we don't trim down the
> workaround list to reclaim some memory, and we don't print the usual
> "Initialized 1 context workaround" message in dmesg.  Let's change the
> early return to a jump down to the wa_init_finish() call at the bottom
> of the function.
> 
> Reported-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Fixes: 9e9dfd080201 ("drm/i915/dg2: Maintain backward-compatible nested batch behavior")
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
>   drivers/gpu/drm/i915/gt/intel_workarounds.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> index 688ed04edbf6..94e1937f8d29 100644
> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> @@ -689,7 +689,7 @@ __intel_engine_init_ctx_wa(struct intel_engine_cs *engine,
>   		fakewa_disable_nestedbb_mode(engine, wal);
>   
>   	if (engine->class != RENDER_CLASS)
> -		return;
> +		goto done;
>   
>   	if (IS_DG1(i915))
>   		dg1_ctx_workarounds_init(engine, wal);
> @@ -720,6 +720,7 @@ __intel_engine_init_ctx_wa(struct intel_engine_cs *engine,
>   	else
>   		MISSING_CASE(GRAPHICS_VER(i915));
>   
> +done:
>   	wa_init_finish(wal);
>   }
>   
> 

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

Tvrtko

  parent reply	other threads:[~2021-08-26  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  3:35 [Intel-gfx] [PATCH] drm/i915: Ensure wa_init_finish() is called for ctx workaround list Matt Roper
2021-08-26  6:21 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2021-08-26  8:26 ` Tvrtko Ursulin [this message]
2021-08-26 16:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Ensure wa_init_finish() is called for ctx workaround list (rev2) Patchwork
2021-08-27  0:11 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=c824c665-0a49-e112-9134-97edeab3b8a4@linux.intel.com \
    --to=tvrtko.ursulin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.