From: Matt Roper <matthew.d.roper@intel.com>
To: Shekhar Chauhan <shekhar.chauhan@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v3 1/1] drm/xe/xe2_lpg: Introduce performance guide changes
Date: Mon, 22 Jan 2024 08:33:04 -0800 [thread overview]
Message-ID: <20240122163304.GA5506@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20240122054904.2111721-2-shekhar.chauhan@intel.com>
On Mon, Jan 22, 2024 at 11:19:04AM +0530, Shekhar Chauhan wrote:
> Add performance guide changes to Xe2_LPG.
>
> BSpec: 72161
> Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
> ---
> drivers/gpu/drm/xe/regs/xe_gt_regs.h | 6 ++++++
> drivers/gpu/drm/xe/xe_tuning.c | 9 ++++++++-
> 2 files changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/regs/xe_gt_regs.h b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> index 0d4bfc35ff37..cd27480f6486 100644
> --- a/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> +++ b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> @@ -144,6 +144,9 @@
>
> #define GSCPSMI_BASE XE_REG(0x880c)
>
> +#define CCCHKNREG1 XE_REG_MCR(0x8828)
> +#define ENCOMPPERFFIX REG_BIT(18)
> +
> /* Fuse readout registers for GT */
> #define XEHP_FUSE4 XE_REG(0x9114)
> #define CFEG_WMTP_DISABLE REG_BIT(20)
> @@ -289,6 +292,9 @@
> #define XEHP_L3NODEARBCFG XE_REG_MCR(0xb0b4)
> #define XEHP_LNESPARE REG_BIT(19)
>
> +#define L3SQCREG3 XE_REG_MCR(0xb108)
> +#define COMPPWOVERFETCHEN REG_BIT(28)
> +
> #define XEHP_L3SQCREG5 XE_REG_MCR(0xb158)
> #define L3_PWM_TIMER_INIT_VAL_MASK REG_GENMASK(9, 0)
>
> diff --git a/drivers/gpu/drm/xe/xe_tuning.c b/drivers/gpu/drm/xe/xe_tuning.c
> index 53ccd338fd8c..3ae1c0622c32 100644
> --- a/drivers/gpu/drm/xe/xe_tuning.c
> +++ b/drivers/gpu/drm/xe/xe_tuning.c
> @@ -37,7 +37,14 @@ static const struct xe_rtp_entry_sr gt_tunings[] = {
> XE_RTP_ACTIONS(FIELD_SET(XE2LPM_L3SQCREG5, L3_PWM_TIMER_INIT_VAL_MASK,
> REG_FIELD_PREP(L3_PWM_TIMER_INIT_VAL_MASK, 0x7f)))
> },
> -
> + { XE_RTP_NAME("Tuning: Compression Overfetch"),
> + XE_RTP_RULES(GRAPHICS_VERSION_RANGE(2004, XE_RTP_END_VERSION_UNDEFINED)),
> + XE_RTP_ACTIONS(SET(CCCHKNREG1, ENCOMPPERFFIX)),
I think you meant to use CLR instead of SET here, right? Since the
setting we want is the "Disable..." line item, which turns off bit 18
that the hardware already has set by default.
Matt
> + },
> + { XE_RTP_NAME("Tuning: Enable compressible partial write overfetch in L3"),
> + XE_RTP_RULES(GRAPHICS_VERSION_RANGE(2004, XE_RTP_END_VERSION_UNDEFINED)),
> + XE_RTP_ACTIONS(SET(L3SQCREG3, COMPPWOVERFETCHEN))
> + },
> {}
> };
>
> --
> 2.34.1
>
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2024-01-22 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 5:49 [PATCH v3 0/1] drm/xe/xe2_lpg: Introduce performance guide changes Shekhar Chauhan
2024-01-22 5:49 ` [PATCH v3 1/1] " Shekhar Chauhan
2024-01-22 16:33 ` Matt Roper [this message]
2024-01-23 4:59 ` Chauhan, Shekhar
2024-01-22 5:51 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-22 5:52 ` ✓ CI.checkpatch: " Patchwork
2024-01-22 5:53 ` ✓ CI.KUnit: " Patchwork
2024-01-22 6:00 ` ✓ CI.Build: " Patchwork
2024-01-22 6:00 ` ✓ CI.Hooks: " Patchwork
2024-01-22 6:01 ` ✓ CI.checksparse: " Patchwork
2024-01-22 6:24 ` ✓ 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=20240122163304.GA5506@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=shekhar.chauhan@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