From: Nirmoy Das <nirmoy.das@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Gustavo Sousa <gustavo.sousa@intel.com>
Subject: Re: [PATCH] drm/xe/ptl: Apply Wa_14023061436
Date: Wed, 8 Jan 2025 14:54:53 +0100 [thread overview]
Message-ID: <e3e0ddbb-beef-4995-b9b1-ee93a4a326a1@intel.com> (raw)
In-Reply-To: <20241210215549.GT3224633@mdroper-desk1.amr.corp.intel.com>
On 12/10/2024 10:55 PM, Matt Roper wrote:
> On Tue, Dec 10, 2024 at 04:06:21PM +0100, Nirmoy Das wrote:
>> Enable WMTP for the BTD kernel to address Wa14023061436 by setting the
>> proper TDL Chicken Bit.
>>
>> Cc: Gustavo Sousa <gustavo.sousa@intel.com>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>> drivers/gpu/drm/xe/regs/xe_gt_regs.h | 3 +++
>> drivers/gpu/drm/xe/xe_wa.c | 4 ++++
>> 2 files changed, 7 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/regs/xe_gt_regs.h b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
>> index 162f18e975da..6829fbed1803 100644
>> --- a/drivers/gpu/drm/xe/regs/xe_gt_regs.h
>> +++ b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
>> @@ -496,6 +496,9 @@
>> #define EU_SYSTOLIC_LIC_THROTTLE_CTL_WITH_LOCK XE_REG_MCR(0xe534)
>> #define EU_SYSTOLIC_LIC_THROTTLE_CTL_LOCK_BIT REG_BIT(31)
>>
>> +#define TDL_CHICKEN XE_REG_MCR(0xe5f4, XE_REG_OPTION_MASKED)
>> +#define QID_WAIT_FOR_THREAD_NOT_RUN_DISABLE REG_BIT(12)
> e5f4 > e5f0 so I think this needs to be after the XEHP_HDC_CHICKEN0
> definition.
>
>
>> +
>> #define XEHP_HDC_CHICKEN0 XE_REG_MCR(0xe5f0, XE_REG_OPTION_MASKED)
>> #define LSC_L1_FLUSH_CTL_3D_DATAPORT_FLUSH_EVENTS_MASK REG_GENMASK(13, 11)
>> #define DIS_ATOMIC_CHAINING_TYPED_WRITES REG_BIT(3)
>> diff --git a/drivers/gpu/drm/xe/xe_wa.c b/drivers/gpu/drm/xe/xe_wa.c
>> index 570fe0376402..2889d6f65f51 100644
>> --- a/drivers/gpu/drm/xe/xe_wa.c
>> +++ b/drivers/gpu/drm/xe/xe_wa.c
>> @@ -637,6 +637,10 @@ static const struct xe_rtp_entry_sr lrc_was[] = {
> I don't see this register in the RCS engine's LRC (bspec 65182), so I'm
> not sure this is the correct list. We probably need this on
> engine_was[] so that this will be saved/restored properly around engine
> resets.
>
>> XE_RTP_RULES(GRAPHICS_VERSION(1200)),
>> XE_RTP_ACTIONS(SET(COMMON_SLICE_CHICKEN4, DISABLE_TDC_LOAD_BALANCING_CALC))
>> },
>> + { XE_RTP_NAME("14023061436"),
>> + XE_RTP_RULES(GRAPHICS_VERSION_RANGE(3000, 3001), ENGINE_CLASS(RENDER)),
> Given the above (that this isn't tied to one specific engine's LRC) and
> given that the register doesn't fall within the dedicated RCS range
> (0x2xxx), we should probably also change the ENGINE_CLASS(RENDER) to
> FUNC(xe_rtp_match_first_render_or_compute) here. For PTL (the only
> platform that uses these IPs at the moment) it doesn't really matter,
> but if we wind up extending this to some other platform in the future
> that lacks an RCS, then using the 'first render or compute' match will
> ensure that the workaround still gets applied properly in the absence of
> an RCS engine.
Thanks Matt for your detailed review. Sent out a v2 with above suggestions.
Regards,
Nirmoy
>
>
> Matt
>
>> + XE_RTP_ACTIONS(SET(TDL_CHICKEN, QID_WAIT_FOR_THREAD_NOT_RUN_DISABLE))
>> + },
>>
>> /* DG1 */
>>
>> --
>> 2.46.0
>>
prev parent reply other threads:[~2025-01-08 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 15:06 [PATCH] drm/xe/ptl: Apply Wa_14023061436 Nirmoy Das
2024-12-10 15:45 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-10 15:45 ` ✓ CI.checkpatch: " Patchwork
2024-12-10 15:46 ` ✓ CI.KUnit: " Patchwork
2024-12-10 16:04 ` ✓ CI.Build: " Patchwork
2024-12-10 16:07 ` ✓ CI.Hooks: " Patchwork
2024-12-10 16:08 ` ✓ CI.checksparse: " Patchwork
2024-12-10 16:35 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-10 17:54 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-10 21:55 ` [PATCH] " Matt Roper
2025-01-08 13:54 ` Nirmoy Das [this message]
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=e3e0ddbb-beef-4995-b9b1-ee93a4a326a1@intel.com \
--to=nirmoy.das@intel.com \
--cc=gustavo.sousa@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