From: Mario Limonciello <mario.limonciello@amd.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: perry.yuan@amd.com, gautham.shenoy@amd.com,
Linux PM <linux-pm@vger.kernel.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Dhruva Gole <d-gole@ti.com>, Yipeng Zou <zouyipeng@huawei.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v14 5/5] cpufreq: Only disable boost during cpu online when using frequency tables
Date: Tue, 25 Jun 2024 22:14:22 -0500 [thread overview]
Message-ID: <056cc207-678f-48ad-bc44-6b3b06bcc5a3@amd.com> (raw)
In-Reply-To: <20240626031142.ytzpyuflgo73piaw@vireshk-i7>
On 6/25/2024 22:11, Viresh Kumar wrote:
> On 25-06-24, 07:31, Mario Limonciello wrote:
>> The core issue is that there are drivers that have boost functionality but
>> don't have a frequency table. As pointed out by Gautham there are also
>> drivers that have a frequency table but don't advertise boost pstates
>> (CPUFREQ_BOOST_FREQ isn't set on any frequency).
>>
>> So what happens is the driver may have choosen a policy to have boost
>> enabled but when cpufreq_online() is called it gets "marked" disabled from
>> this check introduced in f37a4d6b4a2c even though it's previously enabled.
>
> And who was setting policy->boost_enabled to true before that ? Also
> how will your patch fix the problem ? I don't see any other code
> setting it too, unless request comes from sysfs, which would work even
> now I think.
>
The earlier patches in this series do that with amd-pstate. Gautham had
suggested a change to acpi-cpufreq for the same too.
However I tested Gautham's suggestion (which is in this thread) and I
think it's the better way to do it than what I did in this v14 patch.
next prev parent reply other threads:[~2024-06-26 3:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 21:33 [PATCH v14 0/5] AMD Pstate Driver Core Performance Boost Mario Limonciello
2024-06-24 21:33 ` [PATCH v14 1/5] cpufreq: acpi: move MSR_K7_HWCR_CPB_DIS_BIT into msr-index.h Mario Limonciello
2024-06-24 21:33 ` [PATCH v14 2/5] cpufreq: amd-pstate: initialize core precision boost state Mario Limonciello
2024-06-24 21:33 ` [PATCH v14 3/5] cpufreq: amd-pstate: Cap the CPPC.max_perf to nominal_perf if CPB is off Mario Limonciello
2024-06-24 21:33 ` [PATCH v14 4/5] Documentation: cpufreq: amd-pstate: update doc for Per CPU boost control method Mario Limonciello
2024-06-25 12:03 ` Gautham R.Shenoy
2024-06-24 21:34 ` [PATCH v14 5/5] cpufreq: Only disable boost during cpu online when using frequency tables Mario Limonciello
2024-06-25 6:30 ` Viresh Kumar
2024-06-25 12:31 ` Mario Limonciello
2024-06-26 3:11 ` Viresh Kumar
2024-06-26 3:14 ` Mario Limonciello [this message]
2024-06-26 3:17 ` Viresh Kumar
2024-06-26 3:20 ` Mario Limonciello
2024-06-26 3:25 ` Viresh Kumar
2024-06-26 3:27 ` Viresh Kumar
2024-06-26 3:33 ` Mario Limonciello
2024-06-26 3:44 ` Viresh Kumar
2024-06-26 3:46 ` Mario Limonciello
2024-06-25 11:55 ` Gautham R.Shenoy
2024-06-25 12:32 ` Mario Limonciello
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=056cc207-678f-48ad-bc44-6b3b06bcc5a3@amd.com \
--to=mario.limonciello@amd.com \
--cc=d-gole@ti.com \
--cc=dietmar.eggemann@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=quic_sibis@quicinc.com \
--cc=rafael.j.wysocki@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=zouyipeng@huawei.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