Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Tapani Pälli" <tapani.palli@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <tilak.tirumalesh.tangudu@intel.com>
Subject: Re: [PATCH] drm/xe/xe3: Apply wa_14024997852
Date: Sat, 25 Oct 2025 08:43:03 +0300	[thread overview]
Message-ID: <0f94ff84-c160-4ae0-8d10-0a4f040562d7@intel.com> (raw)
In-Reply-To: <20251024235248.GN1207432@mdroper-desk1.amr.corp.intel.com>


On 10/25/25 02:52, Matt Roper wrote:
> On Thu, Oct 23, 2025 at 07:40:41AM +0300, Tapani Pälli wrote:
>> Whitelist registers needed for userspace to control autostrip on xe3.
>>
>> Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_reg_whitelist.c | 7 +++++++
>>   1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_reg_whitelist.c b/drivers/gpu/drm/xe/xe_reg_whitelist.c
>> index 690bc327a363..fab56673153b 100644
>> --- a/drivers/gpu/drm/xe/xe_reg_whitelist.c
>> +++ b/drivers/gpu/drm/xe/xe_reg_whitelist.c
>> @@ -89,6 +89,13 @@ static const struct xe_rtp_entry_sr register_whitelist[] = {
>>   				   RING_FORCE_TO_NONPRIV_ACCESS_RD |
>>   				   RING_FORCE_TO_NONPRIV_RANGE_4))
>>   	},
>> +	{ XE_RTP_NAME("14024997852"),
>> +	  XE_RTP_RULES(GRAPHICS_VERSION(3500), ENGINE_CLASS(RENDER)),
> We don't have any platforms with an IP version of exactly 35.00.  If you
> were trying to whitelist this for everything Xe3p and beyond, you could
> use GRAPHICS_VERSION_RANGE with an undefined upper bound, but generally
> we avoid doing that for whitelists because future platforms/IPs might
> not need this workaround anymore, but some new setting with security
> implications could get added to the register in the future and we
> wouldn't want to accidentally give userspace access on those future
> platforms due to an unbounded range on the whitelist entry.
>
> The only Xe3p platform we have on drm-tip at the moment is Xe3p_XPC
> (version 35.11), but as far as I can see, Wa_14024997852 doesn't apply
> there (and in fact that IP doesn't even have a render engine).  This
> workaround _does_ apply to various Xe3 platform though (with versions
> ranging from 30.00 to 30.05) and we don't seem to have those whitelisted
> in the KMD yet.  Your patch here has an "xe3" prefix, so are those the
> versions you actually intended to target?

Argh yes, the intention was indeed to target "3000", not "3500". Will 
fix this.

For me it looks like this WA is for whole the xe3 so I'm assuming 
GRAPHICS_VERSION_RANGE or GRAPHICS_STEP is not necessary for this WA.


>
> Matt
>
>> +	  XE_RTP_ACTIONS(WHITELIST(FF_MODE,
>> +				   RING_FORCE_TO_NONPRIV_ACCESS_RW),
>> +			 WHITELIST(VFLSKPD,
>> +				   RING_FORCE_TO_NONPRIV_ACCESS_RW))
>> +	},
>>   };
>>   
>>   static void whitelist_apply_to_hwe(struct xe_hw_engine *hwe)
>> -- 
>> 2.51.0
>>

  reply	other threads:[~2025-10-25  5:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  4:40 [PATCH] drm/xe/xe3: Apply wa_14024997852 Tapani Pälli
2025-10-23  5:29 ` ✓ CI.KUnit: success for " Patchwork
2025-10-23  6:08 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-23 11:22 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-24 23:52 ` [PATCH] " Matt Roper
2025-10-25  5:43   ` Tapani Pälli [this message]
2025-10-26 11:15   ` [PATCH v2] " Tapani Pälli
2025-10-28 20:59     ` Matt Roper
2025-10-29  8:50       ` [PATCH v3] " Tapani Pälli
2025-10-29 22:24         ` Matt Roper
2025-10-26 11:22 ` ✓ CI.KUnit: success for drm/xe/xe3: Apply wa_14024997852 (rev2) Patchwork
2025-10-26 12:01 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-26 13:09 ` ✓ Xe.CI.Full: " Patchwork
2025-10-29 10:44 ` ✓ CI.KUnit: success for drm/xe/xe3: Apply wa_14024997852 (rev3) Patchwork
2025-10-29 11:34 ` ✓ Xe.CI.BAT: " 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=0f94ff84-c160-4ae0-8d10-0a4f040562d7@intel.com \
    --to=tapani.palli@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=tilak.tirumalesh.tangudu@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