Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe/mtl: Reduce Wa_14018575942 scope to the CCS engine
Date: Fri, 28 Jul 2023 14:22:45 -0400	[thread overview]
Message-ID: <ZMQHddL/uBrHo0LB@intel.com> (raw)
In-Reply-To: <20230728175601.2343755-2-matthew.d.roper@intel.com>

On Fri, Jul 28, 2023 at 10:56:02AM -0700, Matt Roper wrote:
> The MTL version of Wa_14018575942 has been updated to suggest only
> applying the register change on the CCS engine.
> 
> Note that DG2 and PVC have a functionally equivalent workaround with
> Wa_18018781329; for now that one is still applying to all engines,
> although we'll keep an eye on it in case it changes to be CCS-specific
> too.

I just noticed there are changes in DG2 recommendation as well.
Please check 14015427992.

In PVC it probably doesn't matter much because no usage on RCS or
media engines...

for this one here anyway:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> 
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_wa.c | 10 +---------
>  1 file changed, 1 insertion(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_wa.c b/drivers/gpu/drm/xe/xe_wa.c
> index 497a8c05c715..5cf84a096302 100644
> --- a/drivers/gpu/drm/xe/xe_wa.c
> +++ b/drivers/gpu/drm/xe/xe_wa.c
> @@ -238,21 +238,13 @@ static const struct xe_rtp_entry_sr gt_was[] = {
>  	},
>  	{ XE_RTP_NAME("14018575942"),
>  	  XE_RTP_RULES(GRAPHICS_VERSION_RANGE(1270, 1271)),
> -	  XE_RTP_ACTIONS(SET(RENDER_MOD_CTRL, FORCE_MISS_FTLB),
> -			 SET(COMP_MOD_CTRL, FORCE_MISS_FTLB))
> +	  XE_RTP_ACTIONS(SET(COMP_MOD_CTRL, FORCE_MISS_FTLB))
>  	},
>  	{ XE_RTP_NAME("22016670082"),
>  	  XE_RTP_RULES(GRAPHICS_VERSION_RANGE(1270, 1271)),
>  	  XE_RTP_ACTIONS(SET(SQCNT1, ENFORCE_RAR))
>  	},
>  
> -	/* Xe_LPM+ */
> -	{ XE_RTP_NAME("14018575942"),
> -	  XE_RTP_RULES(MEDIA_VERSION(1300)),
> -	  XE_RTP_ACTIONS(SET(XELPMP_VDBX_MOD_CTRL, FORCE_MISS_FTLB),
> -			 SET(XELPMP_VEBX_MOD_CTRL, FORCE_MISS_FTLB))
> -	},
> -
>  	{}
>  };
>  
> -- 
> 2.41.0
> 

  reply	other threads:[~2023-07-28 18:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 17:56 [Intel-xe] [PATCH] drm/xe/mtl: Reduce Wa_14018575942 scope to the CCS engine Matt Roper
2023-07-28 18:22 ` Rodrigo Vivi [this message]
2023-07-28 19:04 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-07-28 19:04 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-07-28 19:06 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-07-28 19:10 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-28 19:10 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-28 19:11 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-28 19:45 ` [Intel-xe] ○ CI.BAT: info " 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=ZMQHddL/uBrHo0LB@intel.com \
    --to=rodrigo.vivi@intel.com \
    --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