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 05/10] PM: sleep: stats: Call dpm_save_failed_step() at most once per phase
Date: Tue, 30 Jan 2024 08:20:10 +0100 [thread overview]
Message-ID: <ZbijKpi2CvwoV/gB@linux.intel.com> (raw)
In-Reply-To: <23401570.6Emhk5qWAg@kreacher>
On Mon, Jan 29, 2024 at 05:24:04PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> If the handling of two or more devices fails in one suspend-resume
> phase, it should be counted once in the statistics which is not
> guaranteed to happen during system-wide resume of devices due to
> the possible asynchronous execution of device callbacks.
>
> Address this by using the async_error static variable during system-wide
> device resume to indicate that there has been a device resume error and
> the given suspend-resume phase should be counted as failing.
>
> 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 | 20 +++++++++++++++++---
> 1 file changed, 17 insertions(+), 3 deletions(-)
>
> Index: linux-pm/drivers/base/power/main.c
> ===================================================================
> --- linux-pm.orig/drivers/base/power/main.c
> +++ linux-pm/drivers/base/power/main.c
> @@ -685,7 +685,7 @@ Out:
> TRACE_RESUME(error);
>
> if (error) {
> - dpm_save_failed_step(SUSPEND_RESUME_NOIRQ);
> + async_error = error;
> dpm_save_failed_dev(dev_name(dev));
> pm_dev_err(dev, state, async ? " async noirq" : " noirq", error);
> }
> @@ -705,6 +705,9 @@ static void dpm_noirq_resume_devices(pm_
> ktime_t starttime = ktime_get();
>
> trace_suspend_resume(TPS("dpm_resume_noirq"), state.event, true);
> +
> + async_error = 0;
> +
> mutex_lock(&dpm_list_mtx);
> pm_transition = state;
>
> @@ -734,6 +737,9 @@ static void dpm_noirq_resume_devices(pm_
> mutex_unlock(&dpm_list_mtx);
> async_synchronize_full();
> dpm_show_time(starttime, state, 0, "noirq");
> + if (async_error)
> + dpm_save_failed_step(SUSPEND_RESUME_NOIRQ);
> +
> trace_suspend_resume(TPS("dpm_resume_noirq"), state.event, false);
> }
>
> @@ -815,7 +821,7 @@ Out:
> complete_all(&dev->power.completion);
>
> if (error) {
> - dpm_save_failed_step(SUSPEND_RESUME_EARLY);
> + async_error = error;
> dpm_save_failed_dev(dev_name(dev));
> pm_dev_err(dev, state, async ? " async early" : " early", error);
> }
> @@ -839,6 +845,9 @@ void dpm_resume_early(pm_message_t state
> ktime_t starttime = ktime_get();
>
> trace_suspend_resume(TPS("dpm_resume_early"), state.event, true);
> +
> + async_error = 0;
> +
> mutex_lock(&dpm_list_mtx);
> pm_transition = state;
>
> @@ -868,6 +877,9 @@ void dpm_resume_early(pm_message_t state
> mutex_unlock(&dpm_list_mtx);
> async_synchronize_full();
> dpm_show_time(starttime, state, 0, "early");
> + if (async_error)
> + dpm_save_failed_step(SUSPEND_RESUME_EARLY);
> +
> trace_suspend_resume(TPS("dpm_resume_early"), state.event, false);
> }
>
> @@ -971,7 +983,7 @@ static void device_resume(struct device
> TRACE_RESUME(error);
>
> if (error) {
> - dpm_save_failed_step(SUSPEND_RESUME);
> + async_error = error;
> dpm_save_failed_dev(dev_name(dev));
> pm_dev_err(dev, state, async ? " async" : "", error);
> }
> @@ -1030,6 +1042,8 @@ void dpm_resume(pm_message_t state)
> mutex_unlock(&dpm_list_mtx);
> async_synchronize_full();
> dpm_show_time(starttime, state, 0, NULL);
> + if (async_error)
> + dpm_save_failed_step(SUSPEND_RESUME);
>
> cpufreq_resume();
> devfreq_resume();
>
>
>
next prev parent reply other threads:[~2024-01-30 7:20 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 [this message]
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
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=ZbijKpi2CvwoV/gB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.