From: Gustavo Sousa <gustavo.sousa@intel.com>
To: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH 1/1] drm/xe: Add support for WA 14028250015
Date: Tue, 3 Nov 2026 11:33:36 -0300 [thread overview]
Message-ID: <87zevqougv.fsf@intel.com> (raw)
In-Reply-To: <10a999d06de867a938a67fbc345e4acda9ddafff.camel@intel.com>
"Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com> writes:
> [snip]
>
>> Also, on the subject, I would prefer that we stick to the notation
>> Wa_14028250015.
> will fix
> [snip]
>
>>
>> > GUC_WA_KLV_REMAP_RANGED_TLB_INV = 0x900f,
>> > GUC_WA_KLV_IGNORE_MMIO_READ_SEM_TOKEN_64 = 0x9010,
>> > GUC_WA_KLV_IGNORE_MULTIQ_CTX_COMPLETE_WITH_PREEMPT_IN_CSB = 0x9011,
>> > + GUC_WA_KLV_ENABLE_PAGE_RECLAIM_ERROR_COMPLETION = 0x9012,
>>
>> Probably better to use the same name as defined by GuC here?
> if u mean the internal spec - sure i can do that but i didnt realize that is the convention here.
I'm not sure if this is the convention though. :-)
I just thought it would make sense to keep the names in sync. Maybe
Daniele can provide his input here.
--
Gustavo Sousa
> [snip]
>
>> > + /* On GuC 70.78 onwards, we enable GuC PRL-completion-IRQ workaround on applicable GMIDs */
>> > + if (XE_GT_WA(gt, 14028250015) && GUC_FIRMWARE_VER_AT_LEAST(>->uc.guc, 70, 78) &&
>> > + gt_to_xe(gt)->info.has_page_reclaim_hw_assist)
>>
>> Should we really gate this by the has_page_reclaim_hw_assist feature
>> flag? This flag can be changed at runtime via debugfs. I would assume
>> that GuC would do the right thing if PRL is not supported on the IP it
>> is running.
>
> yeah - like your idea better - will just always do it.
>
> [snip]
next prev parent reply other threads:[~2026-11-03 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 18:10 [PATCH 1/1] drm/xe: Add support for WA 14028250015 Alan Previn
2026-10-29 18:20 ` ✓ CI.KUnit: success for series starting with [1/1] " Patchwork
2026-10-29 18:54 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-30 15:18 ` ✓ Xe.CI.FULL: " Patchwork
2026-10-30 23:12 ` [PATCH 1/1] " Gustavo Sousa
2026-11-02 16:47 ` Teres Alexis, Alan Previn
2026-11-03 14:33 ` Gustavo Sousa [this message]
2026-11-03 22:48 ` Ceraolo Spurio, Daniele
-- strict thread matches above, loose matches on Subject: below --
2026-11-02 18:05 [PATCH 1/1] drm/xe: Add support for Wa_14028250015 Alan Previn
2026-11-03 1:57 ` Julia Filipchuk
2026-11-03 23:58 ` Gustavo Sousa
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=87zevqougv.fsf@intel.com \
--to=gustavo.sousa@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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