From: Pavel Machek <pavel@ucw.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
pm list <linux-pm@lists.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/3] PM: Do not destroy/create devices while suspended
Date: Tue, 25 Dec 2007 13:33:20 +0100 [thread overview]
Message-ID: <20071225123320.GA1670@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0712241045150.25920-100000@netrider.rowland.org>
On Mon 2007-12-24 10:51:15, Alan Stern wrote:
> On Mon, 24 Dec 2007, Rafael J. Wysocki wrote:
>
> > Hi,
> >
> > Some device drivers register CPU hotplug notifiers and use them to destroy
> > device objects when removing the corresponding CPUs and to create these objects
> > when adding the CPUs back.
> >
> > Unfortunately, this is not the right thing to do during suspend/hibernation,
> > since in that cases the CPU hotplug notifiers are called after suspending
> > devices and before resuming them, so the operations in question are carried
> > out on the objects representing suspended devices which shouldn't be
> > unregistered behing the PM core's back. Although right now it usually doesn't
> > lead to any practical complications, it will predictably deadlock if
> > gregkh-driver-pm-acquire-device-locks-prior-to-suspending.patch is applied.
> >
> > The solution is to prevent drivers from removing/adding devices from within
> > CPU hotplug notifiers during suspend/hibernation using the FROZEN bit
> > in the notifier's action argument. The following three patches modify the
> > MSR, x86-64 MCE and cpuid drivers along these lines.
>
> Do we need to worry about the possibility that when the system wakes up
> from hibernation, the set of usable CPUs might be smaller than it was
> beforehand? Is any special handling needed for this, or is it already
> accounted for?
That should not happen... but it does in some error cases.... so
handling it would be a bonus.
Waking up with one cpu out of 8 is bad, but still way better than not
waking up at all ;-).
Pavel
--
(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:[~2007-12-25 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 0:55 [PATCH 0/3] PM: Do not destroy/create devices while suspended Rafael J. Wysocki
2007-12-24 0:56 ` [PATCH 1/3] PM: Do not destroy/create devices while suspended in msr.c Rafael J. Wysocki
2007-12-25 12:33 ` Pavel Machek
2007-12-24 0:57 ` [PATCH 2/3] PM: Do not destroy/create devices while suspended in mce_64.c Rafael J. Wysocki
2007-12-25 12:34 ` Pavel Machek
2007-12-24 0:57 ` [PATCH 3/3] PM: Do not destroy/create devices while suspended in cpuid.c Rafael J. Wysocki
2007-12-25 12:34 ` Pavel Machek
2007-12-24 15:51 ` [PATCH 0/3] PM: Do not destroy/create devices while suspended Alan Stern
2007-12-25 12:33 ` Pavel Machek [this message]
2007-12-25 16:21 ` Rafael J. Wysocki
2007-12-25 19:21 ` Rafael J. Wysocki
2007-12-26 3:33 ` Alan Stern
2007-12-26 15:12 ` 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=20071225123320.GA1670@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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