From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v2 08/10] PM: sleep: Move some assignments from under a lock
Date: Tue, 30 Jan 2024 08:21:30 +0100 [thread overview]
Message-ID: <Zbijetaso8dpog9m@linux.intel.com> (raw)
In-Reply-To: <3750318.MHq7AAxBmi@kreacher>
On Mon, Jan 29, 2024 at 05:27:33PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The async_error and pm_transition variables are set under dpm_list_mtx
> in multiple places in the system-wide device PM core code, which is
> unnecessary and confusing, so rearrange the code so that the variables
> in question are set before acquiring the lock.
>
> While at it, add some empty code lines around locking to improve the
> consistency of the code.
>
> No intentional functional impact.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> ---
>
> v1 -> v2: No changes.
>
> ---
> drivers/base/power/main.c | 28 +++++++++++++++++++++-------
> 1 file changed, 21 insertions(+), 7 deletions(-)
>
> Index: linux-pm/drivers/base/power/main.c
> ===================================================================
> --- linux-pm.orig/drivers/base/power/main.c
> +++ linux-pm/drivers/base/power/main.c
> @@ -707,9 +707,9 @@ static void dpm_noirq_resume_devices(pm_
> trace_suspend_resume(TPS("dpm_resume_noirq"), state.event, true);
>
> async_error = 0;
> + pm_transition = state;
>
> mutex_lock(&dpm_list_mtx);
> - pm_transition = state;
>
> /*
> * Trigger the resume of "async" devices upfront so they don't have to
> @@ -847,9 +847,9 @@ void dpm_resume_early(pm_message_t state
> trace_suspend_resume(TPS("dpm_resume_early"), state.event, true);
>
> async_error = 0;
> + pm_transition = state;
>
> mutex_lock(&dpm_list_mtx);
> - pm_transition = state;
>
> /*
> * Trigger the resume of "async" devices upfront so they don't have to
> @@ -1012,10 +1012,11 @@ void dpm_resume(pm_message_t state)
> trace_suspend_resume(TPS("dpm_resume"), state.event, true);
> might_sleep();
>
> - mutex_lock(&dpm_list_mtx);
> pm_transition = state;
> async_error = 0;
>
> + mutex_lock(&dpm_list_mtx);
> +
> /*
> * Trigger the resume of "async" devices upfront so they don't have to
> * wait for the "non-async" ones they don't depend on.
> @@ -1294,10 +1295,12 @@ static int dpm_noirq_suspend_devices(pm_
> int error = 0;
>
> trace_suspend_resume(TPS("dpm_suspend_noirq"), state.event, true);
> - mutex_lock(&dpm_list_mtx);
> +
> pm_transition = state;
> async_error = 0;
>
> + mutex_lock(&dpm_list_mtx);
> +
> while (!list_empty(&dpm_late_early_list)) {
> struct device *dev = to_device(dpm_late_early_list.prev);
>
> @@ -1320,7 +1323,9 @@ static int dpm_noirq_suspend_devices(pm_
> if (error || async_error)
> break;
> }
> +
> mutex_unlock(&dpm_list_mtx);
> +
> async_synchronize_full();
> if (!error)
> error = async_error;
> @@ -1470,11 +1475,14 @@ int dpm_suspend_late(pm_message_t state)
> int error = 0;
>
> trace_suspend_resume(TPS("dpm_suspend_late"), state.event, true);
> - wake_up_all_idle_cpus();
> - mutex_lock(&dpm_list_mtx);
> +
> pm_transition = state;
> async_error = 0;
>
> + wake_up_all_idle_cpus();
> +
> + mutex_lock(&dpm_list_mtx);
> +
> while (!list_empty(&dpm_suspended_list)) {
> struct device *dev = to_device(dpm_suspended_list.prev);
>
> @@ -1498,7 +1506,9 @@ int dpm_suspend_late(pm_message_t state)
> if (error || async_error)
> break;
> }
> +
> mutex_unlock(&dpm_list_mtx);
> +
> async_synchronize_full();
> if (!error)
> error = async_error;
> @@ -1745,9 +1755,11 @@ int dpm_suspend(pm_message_t state)
> devfreq_suspend();
> cpufreq_suspend();
>
> - mutex_lock(&dpm_list_mtx);
> pm_transition = state;
> async_error = 0;
> +
> + mutex_lock(&dpm_list_mtx);
> +
> while (!list_empty(&dpm_prepared_list)) {
> struct device *dev = to_device(dpm_prepared_list.prev);
>
> @@ -1771,7 +1783,9 @@ int dpm_suspend(pm_message_t state)
> if (error || async_error)
> break;
> }
> +
> mutex_unlock(&dpm_list_mtx);
> +
> async_synchronize_full();
> if (!error)
> error = async_error;
>
>
>
>
next prev parent reply other threads:[~2024-01-30 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 16:00 [PATCH v2 00/10] PM: sleep: Fix up suspend stats handling and clean up core suspend code Rafael J. Wysocki
2024-01-29 16:09 ` [PATCH v2 01/10] PM: sleep: stats: Use array of suspend step names Rafael J. Wysocki
2024-01-29 16:11 ` [PATCH v2 02/10] PM: sleep: stats: Use an array of step failure counters Rafael J. Wysocki
2024-01-30 7:02 ` Stanislaw Gruszka
2024-01-30 13:42 ` Rafael J. Wysocki
2024-01-29 16:13 ` [PATCH v2 03/10] PM: sleep: stats: Use unsigned int for success and " Rafael J. Wysocki
2024-01-30 7:02 ` Stanislaw Gruszka
2024-01-29 16:24 ` [PATCH v2 05/10] PM: sleep: stats: Call dpm_save_failed_step() at most once per phase Rafael J. Wysocki
2024-01-30 7:20 ` Stanislaw Gruszka
2024-01-29 16:24 ` [PATCH v2 06/10] PM: sleep: stats: Use locking in dpm_save_failed_dev() Rafael J. Wysocki
2024-01-29 16:25 ` [PATCH v2 07/10] PM: sleep: stats: Log errors right after running suspend callbacks Rafael J. Wysocki
2024-01-30 7:36 ` Stanislaw Gruszka
2024-01-29 16:27 ` [PATCH v2 08/10] PM: sleep: Move some assignments from under a lock Rafael J. Wysocki
2024-01-30 7:21 ` Stanislaw Gruszka [this message]
2024-01-29 16:28 ` [PATCH v2 09/10] PM: sleep: Move devices to new lists earlier in each suspend phase Rafael J. Wysocki
2024-01-29 16:29 ` [PATCH v2 10/10] PM: sleep: Call dpm_async_fn() directly " Rafael J. Wysocki
2024-01-30 7:37 ` Stanislaw Gruszka
2024-01-29 16:30 ` [PATCH v2 04/10] PM: sleep: stats: Define suspend_stats next to the code using it Rafael J. Wysocki
2024-01-31 12:42 ` [PATCH v2 00/10] PM: sleep: Fix up suspend stats handling and clean up core suspend code Ulf Hansson
2024-01-31 13:31 ` Rafael J. Wysocki
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=Zbijetaso8dpog9m@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@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