From: "Anirban, Sk" <sk.anirban@intel.com>
To: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<riana.tauro@intel.com>, <karthik.poosa@intel.com>,
<raag.jadav@intel.com>
Subject: Re: [PATCH] drm/i915/slpc: Update min_freq_softlimit when ignore_eff_freq is enabled
Date: Wed, 10 Sep 2025 11:52:15 +0530 [thread overview]
Message-ID: <da9a3936-fb21-4495-bdc7-fab5f71c6fd4@intel.com> (raw)
In-Reply-To: <3971a679-1bf4-401a-9df6-9632c596de41@intel.com>
Hi,
On 10-09-2025 04:07, Belgaumkar, Vinay wrote:
>
> On 9/9/2025 6:28 AM, Sk Anirban wrote:
>> When slpc_ignore_eff_freq is enabled, min frequency is set to RPn but
>> min_freq_softlimit is not updated, causing sysfs to show stale
>> values.
>
> sysfs(get_min_freq) does a query_task_state and then displays the min
> freq. That shouldn't be stale info. Within slpc code, we are using
> min_freq_softlimit to track user changes to min freq. We shouldn't be
> overwriting this when efficient freq is toggled.
>
> Thanks,
>
> Vinay.
While fetching min_freq, we currently return slpc->min_freq_softlimit
from intel_rps_get_min_frequency. However, if the internal minimum
frequency has been updated to RPn, imo this change should be reflected
to the user as well.
Thanks,
Anirban
>
>>
>> Update min freq softlimit when ignore_eff_freq is successfully enabled.
>>
>> Signed-off-by: Sk Anirban <sk.anirban@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c
>> b/drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c
>> index d5ee6e5e1443..07fa0423b1a3 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c
>> @@ -495,10 +495,13 @@ int intel_guc_slpc_set_ignore_eff_freq(struct
>> intel_guc_slpc *slpc, bool val)
>> slpc->ignore_eff_freq = val;
>> /* Set min to RPn when we disable efficient freq */
>> - if (val)
>> + if (val) {
>> ret = slpc_set_param(slpc,
>> SLPC_PARAM_GLOBAL_MIN_GT_UNSLICE_FREQ_MHZ,
>> slpc->min_freq);
>> + if (!ret)
>> + slpc->min_freq_softlimit = slpc->min_freq;
>> + }
>> }
>> intel_runtime_pm_put(&i915->runtime_pm, wakeref);
next prev parent reply other threads:[~2025-09-10 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:28 [PATCH] drm/i915/slpc: Update min_freq_softlimit when ignore_eff_freq is enabled Sk Anirban
2025-09-09 18:35 ` ✓ i915.CI.BAT: success for drm/i915/slpc: Update min_freq_softlimit when ignore_eff_freq is enabled (rev2) Patchwork
2025-09-09 22:37 ` [PATCH] drm/i915/slpc: Update min_freq_softlimit when ignore_eff_freq is enabled Belgaumkar, Vinay
2025-09-10 6:22 ` Anirban, Sk [this message]
2025-09-10 23:49 ` Belgaumkar, Vinay
2025-09-10 5:59 ` ✗ i915.CI.Full: failure for drm/i915/slpc: Update min_freq_softlimit when ignore_eff_freq is enabled (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-09-09 10:06 [PATCH] drm/i915/slpc: Update min_freq_softlimit when ignore_eff_freq is enabled Sk Anirban
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=da9a3936-fb21-4495-bdc7-fab5f71c6fd4@intel.com \
--to=sk.anirban@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox