From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: [PATCH 0/2] PM: sleep: Rework cpuidle handling during system-wide PM transitions
Date: Fri, 22 Oct 2021 18:02:43 +0200 [thread overview]
Message-ID: <2230995.ElGaqSPkdT@kreacher> (raw)
Hi All,
Currently, cpuidle is paused before the last phase of suspending device
(suspend_noirq), but first it doesn't make sense to pause it for
suspend-to-idle, because suspend-to-idle resumes it anyway later, and
then it need not be paused while suspending devices anyway.
Patch [1/2] removes the pausing and resuming of cpuidle from the suspend-to-idle
path and patch [1/2] combines these operations with the disabling and enabling
of secondary CPUs (which does not take place in the suspend-to-idle path),
respectively.
Thanks!
next reply other threads:[~2021-10-22 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 16:02 Rafael J. Wysocki [this message]
2021-10-22 16:04 ` [PATCH 1/2] PM: suspend: Do not pause cpuidle in the suspend-to-idle path Rafael J. Wysocki
2021-10-25 14:23 ` Ulf Hansson
2021-10-22 16:07 ` [PATCH 2/2] PM: sleep: Pause cpuidle later and resume it earlier during system transitions Rafael J. Wysocki
2021-10-25 14:24 ` Ulf Hansson
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=2230995.ElGaqSPkdT@kreacher \
--to=rjw@rjwysocki.net \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).