From: Pavel Machek <pavel@ucw.cz>
To: Paul Mackerras <paulus@samba.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-pm@lists.linux-foundation.org
Subject: Re: shrinking memory for suspend?
Date: Thu, 3 May 2007 18:34:46 +0200 [thread overview]
Message-ID: <20070503163446.GD32401@elf.ucw.cz> (raw)
In-Reply-To: <17977.56024.199983.463385@cargo.ozlabs.ibm.com>
Hi!
> > > Which is why the powermac/powerbook sleep code insists on there only
> > > being one cpu active. I have an SMP powermac which can sleep; I use a
> > > little script to take the second cpu down before sleeping and bring it
> > > back up after waking up.
> >
> > That's quite intrusive. Ideally, user space processes should not notice that
> > there have been a suspend at one point.
>
> Certainly, *most* userspace processes should not notice, and they
> don't. But the process initiating the suspend most certainly knows
> about the suspend happening. And that's the one that arranges for
> taking the second cpu down and bringing it up. So your objection
> seems silly to me, unless you meant something other than what your
> words seem to say.
Not silly at all.
xterm #1 xterm #2
suspend-to-RAM
script does echo 0 > CPU1/online as part of process echo 0 > CPU1/online
If this happens, resume will most likely online CPU1, contrary to
user's commands.
Plus, if your script is bad and leaves other CPUs running, you
get rather nasty oops, or worse. Userspace should not be able to crash
kernel like _that_.
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-05-03 16:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 14:24 shrinking memory for suspend? Johannes Berg
2007-04-30 15:09 ` Alan Stern
2007-04-30 15:10 ` Rafael J. Wysocki
2007-04-30 15:09 ` Johannes Berg
2007-04-30 19:57 ` Rafael J. Wysocki
2007-05-02 11:29 ` Pavel Machek
2007-05-02 14:02 ` Johannes Berg
2007-05-03 10:17 ` Rafael J. Wysocki
2007-05-03 10:34 ` Paul Mackerras
2007-05-03 10:45 ` Rafael J. Wysocki
2007-05-03 12:51 ` Paul Mackerras
2007-05-03 13:15 ` Rafael J. Wysocki
2007-05-03 16:34 ` Pavel Machek [this message]
2007-05-03 14:34 ` Alan Stern
2007-05-03 16:39 ` Rafael J. Wysocki
2007-05-03 23:32 ` Paul Mackerras
2007-05-04 9:02 ` Rafael J. Wysocki
2007-05-04 10:49 ` Paul Mackerras
2007-05-04 12:11 ` Rafael J. Wysocki
2007-05-04 15:05 ` Alan Stern
2007-05-03 11:33 ` Johannes Berg
2007-05-03 12:56 ` Rafael J. Wysocki
2007-05-04 10:48 ` Johannes Berg
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=20070503163446.GD32401@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.org \
--cc=paulus@samba.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