From: Mario Limonciello <mario.limonciello@amd.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Dhananjay Ugwekar <dhananjay.ugwekar@amd.com>
Cc: gautham.shenoy@amd.com, rafael@kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq/amd-pstate: Remove unnecessary driver_lock in set_boost
Date: Mon, 3 Feb 2025 09:34:32 -0600 [thread overview]
Message-ID: <f10aab50-5d82-489b-8543-76301bf22e70@amd.com> (raw)
In-Reply-To: <20250203104811.ccf3pj53cjlhwvti@vireshk-i7>
On 2/3/2025 04:48, Viresh Kumar wrote:
> On 30-01-25, 08:52, Dhananjay Ugwekar wrote:
>> set_boost is a per-policy function call, hence a driver wide lock is
>> unnecessary. Also this mutex_acquire can collide with the mutex_acquire
>> from the mode-switch path in status_store(), which can lead to a
>> deadlock. So, remove it.
>>
>> Signed-off-by: Dhananjay Ugwekar <dhananjay.ugwekar@amd.com>
>> ---
>> PS: This patch should ideally go before [1], as that patch uncovers this
>> bug and actually leads to a deadlock when switching the amd_pstate driver
>> mode.
>> [1] https://lore.kernel.org/linux-pm/e16c06d4b8ffdb20e802ffe648f14dc515e60426.1737707712.git.viresh.kumar@linaro.org/
>> ---
>> 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 d5be51bf8692..93788bce7e6a 100644
>> --- a/drivers/cpufreq/amd-pstate.c
>> +++ b/drivers/cpufreq/amd-pstate.c
>> @@ -740,7 +740,6 @@ static int amd_pstate_set_boost(struct cpufreq_policy *policy, int state)
>> pr_err("Boost mode is not supported by this processor or SBIOS\n");
>> return -EOPNOTSUPP;
>> }
>> - guard(mutex)(&amd_pstate_driver_lock);
>>
>> ret = amd_pstate_cpu_boost_update(policy, state);
>> refresh_frequency_limits(policy);
>
> Applied. Thanks.
>
Sorry for my delay with the recent holiday.
I have no concerns with this going to the start of the series.
Acked-by: Mario Limonciello <mario.limonciello@amd.com>
prev parent reply other threads:[~2025-02-03 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 8:52 Dhananjay Ugwekar
2025-01-31 5:06 ` Gautham R. Shenoy
2025-01-31 5:08 ` Viresh Kumar
2025-02-03 10:48 ` Viresh Kumar
2025-02-03 15:34 ` 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=f10aab50-5d82-489b-8543-76301bf22e70@amd.com \
--to=mario.limonciello@amd.com \
--cc=dhananjay.ugwekar@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
/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®