linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 0/2][v3] Fix IPI missing issue when woken from suspend to idle
Date: Tue, 23 Jun 2020 14:31:08 +0800	[thread overview]
Message-ID: <cover.1592892767.git.yu.c.chen@intel.com> (raw)

After an recent optimization on IPIs among idle Cores, the Goldmont failed to
resume from suspend to idle due to missing IPIs. This is because
Goldmont could only be woken up from idle via IPIs rather than POLLING.
Clear the POLLING flag before suspend to idle so that Goldmont will always
get IPIs during suspend to idle.

Chen Yu (2):
  PM / s2idle: Clear _TIF_POLLING_NRFLAG before suspend to idle
  PM / s2idle: Code cleanup to make s2idle consistent with normal idle
    path

 drivers/cpuidle/cpuidle.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-06-23  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  6:31 Chen Yu [this message]
2020-06-23  6:31 ` [PATCH 1/2][v3] PM / s2idle: Clear _TIF_POLLING_NRFLAG before suspend to idle Chen Yu
2020-06-23 15:13   ` Rafael J. Wysocki
2020-06-23  6:31 ` [PATCH 2/2][v3] PM / s2idle: Code cleanup to make s2idle consistent with normal idle path Chen Yu
2020-06-23 17:57   ` Rafael J. Wysocki
2020-06-25  5:15     ` Chen Yu
2020-06-25 10:49       ` 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=cover.1592892767.git.yu.c.chen@intel.com \
    --to=yu.c.chen@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.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).