From: "Chauhan, Shekhar" <shekhar.chauhan@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
Matt Atwood <matthew.s.atwood@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 8/9] drm/xe/ptl: Add performance tuning settings for PTL
Date: Tue, 10 Sep 2024 12:07:58 +0530 [thread overview]
Message-ID: <fbeba95c-01f3-4381-968f-6854c8646737@intel.com> (raw)
In-Reply-To: <20240906235524.GA5774@mdroper-desk1.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
I see a couple of new performance tunings for PTL, can we have them in
the same patch and then rewrite the commit message, instead of it being
only applicable to L3SQCREG5?
-shekhar
On 9/7/2024 5:25 AM, Matt Roper wrote:
> On Fri, Sep 06, 2024 at 02:51:52PM -0700, Matt Atwood wrote:
>> From: Matt Roper<matthew.d.roper@intel.com>
>>
>> The L3SQCREG5 tuning suggestion remains the same on Xe3 as on Xe2.
>>
>> Bspec: 72161
>> Signed-off-by: Matt Roper<matthew.d.roper@intel.com>
>> Signed-off-by: Matt Atwood<matthew.s.atwood@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_tuning.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_tuning.c b/drivers/gpu/drm/xe/xe_tuning.c
>> index faa1bf42e50e..9bb6afaa560a 100644
>> --- a/drivers/gpu/drm/xe/xe_tuning.c
>> +++ b/drivers/gpu/drm/xe/xe_tuning.c
>> @@ -25,15 +25,15 @@ static const struct xe_rtp_entry_sr gt_tunings[] = {
>> XE_RTP_ACTIONS(SET(XEHP_SQCM, EN_32B_ACCESS))
>> },
>>
>> - /* Xe2 */
>> + /* Xe2 / Xe3 */
>>
>> { XE_RTP_NAME("Tuning: L3 cache"),
>> - XE_RTP_RULES(GRAPHICS_VERSION_RANGE(2001, XE_RTP_END_VERSION_UNDEFINED)),
>> + XE_RTP_RULES(GRAPHICS_VERSION_RANGE(2001, 3000)),
> We should just leave this one as upper bound undefined (i.e., applies to
> Xe2 and all future platforms until we come back here to change it).
>
>> XE_RTP_ACTIONS(FIELD_SET(XEHP_L3SQCREG5, L3_PWM_TIMER_INIT_VAL_MASK,
>> REG_FIELD_PREP(L3_PWM_TIMER_INIT_VAL_MASK, 0x7f)))
>> },
>> { XE_RTP_NAME("Tuning: L3 cache - media"),
>> - XE_RTP_RULES(MEDIA_VERSION(2000)),
>> + XE_RTP_RULES(MEDIA_VERSION_RANGE(2000, 3000)),
> And we should probably use an unbound upper range on this one as well.
> In general we should probably assume that tuning settings will continue
> to hold true to future platforms unless/until we know otherwise, since
> that also matches how these things are now being documented in the
> bspec.
>
>
> Matt
>
>> XE_RTP_ACTIONS(FIELD_SET(XE2LPM_L3SQCREG5, L3_PWM_TIMER_INIT_VAL_MASK,
>> REG_FIELD_PREP(L3_PWM_TIMER_INIT_VAL_MASK, 0x7f)))
>> },
>> --
>> 2.44.0
>>
--
-shekhar
[-- Attachment #2: Type: text/html, Size: 3293 bytes --]
next prev parent reply other threads:[~2024-09-10 6:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 21:51 [PATCH 0/9] Add Xe3 and Panther Lake support Matt Atwood
2024-09-06 21:51 ` [PATCH 1/9] drm/xe/xe3: Xe3 uses the same PAT settings as Xe2 Matt Atwood
2024-09-06 22:39 ` Rodrigo Vivi
2024-09-06 23:12 ` Lucas De Marchi
2024-09-06 21:51 ` [PATCH 2/9] drm/xe/xe3: Define Xe3 feature flags Matt Atwood
2024-09-06 23:34 ` Matt Roper
2024-09-06 21:51 ` [PATCH 3/9] drm/xe/xe3: Generate and store the L3 bank mask Matt Atwood
2024-09-06 23:43 ` Matt Roper
2024-09-09 12:15 ` Francois Dugast
2024-09-06 21:51 ` [PATCH 4/9] drm/xe/xe3: Add initial set of workarounds Matt Atwood
2024-09-11 18:03 ` Matt Roper
2024-09-06 21:51 ` [PATCH 5/9] drm/xe/xe3: Extend wa_15015404425 for xe3 Matt Atwood
2024-09-06 23:52 ` Matt Roper
2024-09-11 20:17 ` Matt Roper
2024-09-06 21:51 ` [PATCH 6/9] drm/xe/xe3lpm: Add new "instance0" steering table Matt Atwood
2024-09-06 21:51 ` [PATCH 7/9] drm/xe/ptl: PTL re-uses Xe2 MOCS table Matt Atwood
2024-09-10 6:16 ` Chauhan, Shekhar
2024-09-06 21:51 ` [PATCH 8/9] drm/xe/ptl: Add performance tuning settings for PTL Matt Atwood
2024-09-06 23:55 ` Matt Roper
2024-09-10 6:37 ` Chauhan, Shekhar [this message]
2024-09-06 21:51 ` [PATCH 9/9] drm/xe/ptl: Add PTL platform definition Matt Atwood
2024-09-06 23:56 ` Matt Roper
2024-09-12 16:56 ` Matt Roper
2024-09-06 23:31 ` ✗ CI.checkpatch: warning for Add Xe3 and Panther Lake support Patchwork
2024-09-06 23:32 ` ✓ CI.KUnit: success " Patchwork
2024-09-06 23:44 ` ✓ CI.Build: " Patchwork
2024-09-06 23:46 ` ✓ CI.Hooks: " Patchwork
2024-09-06 23:48 ` ✓ CI.checksparse: " Patchwork
2024-09-07 0:30 ` ✓ 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=fbeba95c-01f3-4381-968f-6854c8646737@intel.com \
--to=shekhar.chauhan@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=matthew.s.atwood@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