From: Mario Limonciello <mario.limonciello@amd.com>
To: Lifeng Zheng <zhenglifeng1@huawei.com>,
rafael@kernel.org, viresh.kumar@linaro.org, perry.yuan@amd.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, jonathan.cameron@huawei.com,
zhanjie9@hisilicon.com, lihuisong@huawei.com,
fanghao11@huawei.com
Subject: Re: [PATCH v2] cpufreq/amd-pstate: Fix per-policy boost flag incorrect when fail
Date: Fri, 10 Jan 2025 09:51:54 -0600 [thread overview]
Message-ID: <ca98621c-bf1a-4cf0-abbc-81cf4dabc63f@amd.com> (raw)
In-Reply-To: <20250110091949.3610770-1-zhenglifeng1@huawei.com>
On 1/10/2025 03:19, Lifeng Zheng wrote:
> Commit c8c68c38b56f ("cpufreq: amd-pstate: initialize core precision
> boost state") sets per-policy boost flag to false when boost fail.
> However, this boost flag will be set to reverse value in
> store_local_boost() and cpufreq_boost_trigger_state() in cpufreq.c. This
> will cause the per-policy boost flag set to true when fail to set boost.
> Remove the extra assignment in amd_pstate_set_boost() and keep all
> operations on per-policy boost flag outside of set_boost() to fix this
> problem.
>
> Fixes: c8c68c38b56f ("cpufreq: amd-pstate: initialize core precision boost state")
> Signed-off-by: Lifeng Zheng <zhenglifeng1@huawei.com>
Thanks, looks good to me. I've queued this up on my bleeding-edge
branch for testing. I'll include this in one of the future 6.14-rc pull
requests with other fixes.
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/cpufreq/amd-pstate.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index d7b1de97727a..a2573393ce30 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -747,7 +747,6 @@ static int amd_pstate_set_boost(struct cpufreq_policy *policy, int state)
> guard(mutex)(&amd_pstate_driver_lock);
>
> ret = amd_pstate_cpu_boost_update(policy, state);
> - policy->boost_enabled = !ret ? state : false;
> refresh_frequency_limits(policy);
>
> return ret;
prev parent reply other threads:[~2025-01-10 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 9:19 Lifeng Zheng
2025-01-10 15:51 ` Mario Limonciello [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=ca98621c-bf1a-4cf0-abbc-81cf4dabc63f@amd.com \
--to=mario.limonciello@amd.com \
--cc=fanghao11@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@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
all inboxes | Powered by JetHome®