From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-pm@lists.linux-foundation.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: shrinking memory for suspend?
Date: Thu, 3 May 2007 18:39:32 +0200 [thread overview]
Message-ID: <200705031839.32952.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0705031031500.3548-100000@iolanthe.rowland.org>
On Thursday, 3 May 2007 16:34, Alan Stern wrote:
> On Thu, 3 May 2007, Rafael J. Wysocki wrote:
>
> > On Thursday, 3 May 2007 12:34, Paul Mackerras wrote:
> > > Rafael J. Wysocki writes:
> > >
> > > > I think that on a uniprocessor system it's quite safe, but on SMP it doesn't
> > > > seem so. For example, imagine the situation in which one CPU is executing the
> > > > suspend code while another one is running userspace with system calls etc.
> > > > Pretty scary.
> > >
> > > 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.
>
> What happens without preemption enabled when a device driver's suspend()
> method calls schedule()?
>
> With or without preemption enabled, what happens when a user process tries
> to do I/O to a suspended device?
Yeah, right. So much for the unforzen user space during a suspend. :-)
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-03 16:39 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
2007-05-03 14:34 ` Alan Stern
2007-05-03 16:39 ` Rafael J. Wysocki [this message]
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=200705031839.32952.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--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