From: Pavel Machek <pavel@ucw.cz>
To: Soren Brinkmann <soren.brinkmann@xilinx.com>
Cc: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH RFC v2] PM / sleep: Fix racing timers
Date: Mon, 28 Jul 2014 12:05:39 +0200 [thread overview]
Message-ID: <20140728100538.GA16237@amd.pavel.ucw.cz> (raw)
In-Reply-To: <1406322408-15408-1-git-send-email-soren.brinkmann@xilinx.com>
On Fri 2014-07-25 14:06:48, Soren Brinkmann wrote:
> On platforms that do not power off during suspend, successfully entering
> suspend races with timers.
>
> The race happening in a couple of location is:
>
> 1. disable IRQs (e.g. arch_suspend_disable_irqs())
> ...
> 2. syscore_suspend()
> -> timekeeping_suspend()
> -> clockevents_notify(SUSPEND)
> -> tick_suspend() (timers are turned off here)
> ...
> 3. wfi (wait for wake-IRQ here)
>
> Between steps 1 and 2 the timers can still generate interrupts that are
> not handled and stay pending until step 3. That pending IRQ causes an
> immediate - spurious - wake.
>
> The solution is to move the clockevents suspend/resume notification
> out of the syscore_suspend step and explictly call them at the appropriate
> time in the suspend/hibernation paths. I.e. timers are suspend _before_
> IRQs get disabled. And accordingly in the resume path.
>
> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
Did you test the hibernation?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-07-28 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 17:35 [PATCH RFC] suspend/hibernation: " Soren Brinkmann
2014-07-24 3:55 ` John Stultz
2014-07-24 15:59 ` Sören Brinkmann
2014-07-25 21:06 ` [PATCH RFC v2] PM / sleep: " Soren Brinkmann
2014-07-27 23:18 ` Rafael J. Wysocki
2014-07-28 19:26 ` John Stultz
2014-07-28 10:05 ` Pavel Machek [this message]
2014-07-28 15:51 ` Sören Brinkmann
2014-07-28 19:19 ` Stephen Boyd
2014-07-28 19:24 ` John Stultz
2014-07-28 19:38 ` Stephen Boyd
2014-07-28 20:02 ` Sören Brinkmann
2014-07-29 23:05 ` Stephen Boyd
2014-07-29 23:22 ` Sören Brinkmann
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=20140728100538.GA16237@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=soren.brinkmann@xilinx.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®