From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Sk Anirban <sk.anirban@intel.com>,
Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<badal.nilawar@intel.com>, <riana.tauro@intel.com>,
<karthik.poosa@intel.com>, <raag.jadav@intel.com>,
<soham.purkait@intel.com>, <mallesh.koujalagi@intel.com>,
<vinay.belgaumkar@intel.com>
Subject: Re: [PATCH] drm/xe/guc: Refresh RPe frequency while setting min frequency
Date: Thu, 9 Oct 2025 15:56:48 -0400 [thread overview]
Message-ID: <aOgTgFc_-FgrV9wJ@intel.com> (raw)
In-Reply-To: <20251009180853.578184-2-sk.anirban@intel.com>
On Thu, Oct 09, 2025 at 11:38:54PM +0530, Sk Anirban wrote:
> Replace cached pc->rpe_freq with xe_guc_pc_get_rpe_freq() call to ensure
> current RPe values are used when setting
> SLPC_PARAM_IGNORE_EFFICIENT_FREQUENCY.
>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/5166
> Signed-off-by: Sk Anirban <sk.anirban@intel.com>
Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_pc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c b/drivers/gpu/drm/xe/xe_guc_pc.c
> index 3c0feb50a1e2..ea1ff96bec32 100644
> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
> @@ -330,7 +330,7 @@ static int pc_set_min_freq(struct xe_guc_pc *pc, u32 freq)
> * Our goal is to have the admin choices respected.
> */
> pc_action_set_param(pc, SLPC_PARAM_IGNORE_EFFICIENT_FREQUENCY,
> - freq < pc->rpe_freq);
> + freq < xe_guc_pc_get_rpe_freq(pc));
I believe this is correct... But wondering if we should entirely kill the
pc->rpe_freq ?!
Vinay, thoughts?
>
> return pc_action_set_param(pc,
> SLPC_PARAM_GLOBAL_MIN_GT_UNSLICE_FREQ_MHZ,
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-10-09 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 18:08 [PATCH] drm/xe/guc: Refresh RPe frequency while setting min frequency Sk Anirban
2025-10-09 18:18 ` ✓ CI.KUnit: success for " Patchwork
2025-10-09 18:52 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-09 19:56 ` Rodrigo Vivi [this message]
2025-10-09 20:47 ` [PATCH] " Belgaumkar, Vinay
2025-10-10 4:59 ` Nilawar, Badal
2025-10-10 20:06 ` Rodrigo Vivi
2025-10-13 5:44 ` Nilawar, Badal
2025-10-13 19:57 ` Anirban, Sk
2025-10-13 10:03 ` Anirban, Sk
2025-10-10 2:49 ` ✓ Xe.CI.Full: success for " 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=aOgTgFc_-FgrV9wJ@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=sk.anirban@intel.com \
--cc=soham.purkait@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.