From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH v1 0/3] cpufreq: Locking-related changes in cpufreq_offline() and cpufreq_remove_dev()
Date: Wed, 11 May 2022 17:46:41 +0200 [thread overview]
Message-ID: <5585781.DvuYhMxLoT@kreacher> (raw)
Hi,
This series is based on the observation that the policy rwsem is used (or rather not
used) inconsistently in cpufreq_remove_dev() (in summary, it does things without
holding the policy rwsem that are done under that rwsem elsewhere).
The first two patches are preparatory (but patch [1/3] is a good enough improvement
by itself IMO) and patch [3/3] makes the essential change.
Please refer to the patch changelogs for details.
Thanks!
next reply other threads:[~2022-05-11 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 15:46 Rafael J. Wysocki [this message]
2022-05-11 15:48 ` [PATCH v1 1/3] cpufreq: Reorganize checks in cpufreq_offline() Rafael J. Wysocki
2022-05-12 7:05 ` Viresh Kumar
2022-05-11 15:50 ` [PATCH v1 2/3] cpufreq: Split cpufreq_offline() Rafael J. Wysocki
2022-05-12 7:28 ` Viresh Kumar
2022-05-11 15:51 ` [PATCH v1 3/3] cpufreq: Rearrange locking in cpufreq_remove_dev() Rafael J. Wysocki
2022-05-12 7:42 ` Viresh Kumar
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=5585781.DvuYhMxLoT@kreacher \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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