From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v4] drm/xe/ptl: Disable DCC on PTL
Date: Mon, 26 Jan 2026 16:39:05 -0500 [thread overview]
Message-ID: <aXfe-QSKb6qJkzNX@intel.com> (raw)
In-Reply-To: <20260124005917.398522-1-vinay.belgaumkar@intel.com>
On Fri, Jan 23, 2026 at 04:59:17PM -0800, Vinay Belgaumkar wrote:
> On PTL, the recommendation is to disable DCC(Duty Cycle Control) as
> it may cause some regressions due to added latencies. Upcoming GuC
> releases will disable DCC on PTL as well, but we need to force it in
> KMD so that this behavior is propagated to older kernels.
>
> v2: Update commit message (Rodrigo)
> v3: Rebase
> v4: Fix BAT issue
Since the only real change in v4 was the typo, I have modified this
note while pushing the patch.
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
and pushed
Thanks,
Rodrigo.
>
> Fixes: 5cdb71d3b0db ("drm/xe/ptl: Add GuC FW definition for PTL")
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Vinay Belgaumkar<vinay.belgaumkar@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_pc.c | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c b/drivers/gpu/drm/xe/xe_guc_pc.c
> index 54702a0fd05b..5e5495a39a3c 100644
> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
> @@ -1198,6 +1198,36 @@ int xe_guc_pc_set_power_profile(struct xe_guc_pc *pc, const char *buf)
> return ret;
> }
>
> +static int pc_action_set_dcc(struct xe_guc_pc *pc, bool enable)
> +{
> + int ret;
> +
> + ret = pc_action_set_param(pc,
> + SLPC_PARAM_TASK_ENABLE_DCC,
> + enable);
> + if (!ret)
> + return pc_action_set_param(pc,
> + SLPC_PARAM_TASK_DISABLE_DCC,
> + !enable);
> + else
> + return ret;
> +}
> +
> +static int pc_modify_defaults(struct xe_guc_pc *pc)
> +{
> + struct xe_device *xe = pc_to_xe(pc);
> + struct xe_gt *gt = pc_to_gt(pc);
> + int ret = 0;
> +
> + if (xe->info.platform == XE_PANTHERLAKE) {
> + ret = pc_action_set_dcc(pc, false);
> + if (unlikely(ret))
> + xe_gt_err(gt, "Failed to modify DCC default: %pe\n", ERR_PTR(ret));
> + }
> +
> + return ret;
> +}
> +
> /**
> * xe_guc_pc_start - Start GuC's Power Conservation component
> * @pc: Xe_GuC_PC instance
> @@ -1249,6 +1279,10 @@ int xe_guc_pc_start(struct xe_guc_pc *pc)
> ktime_ms_delta(ktime_get(), earlier));
> }
>
> + ret = pc_modify_defaults(pc);
> + if (ret)
> + return ret;
> +
> ret = pc_init_freqs(pc);
> if (ret)
> return ret;
> --
> 2.38.1
>
prev parent reply other threads:[~2026-01-26 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 0:59 [PATCH v4] drm/xe/ptl: Disable DCC on PTL Vinay Belgaumkar
2026-01-24 1:09 ` ✓ CI.KUnit: success for drm/xe/ptl: Disable DCC on PTL (rev5) Patchwork
2026-01-24 9:09 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-26 8:01 ` ✓ CI.KUnit: success " Patchwork
2026-01-26 8:26 ` Patchwork
2026-01-26 9:11 ` Patchwork
2026-01-26 9:54 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-26 11:33 ` ✓ Xe.CI.Full: " Patchwork
2026-01-26 11:42 ` Patchwork
2026-01-26 21:39 ` Rodrigo Vivi [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=aXfe-QSKb6qJkzNX@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=vinay.belgaumkar@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