public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: David Brownell <david-b@pacbell.net>
Cc: suspend-devel List <suspend-devel@lists.sourceforge.net>,
	linux-pm@lists.osdl.org, Stephen Hemminger <shemminger@osdl.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [Suspend-devel] [PATCH -mm 2/2]: PM: SMP-safe freezer
Date: Tue, 5 Dec 2006 12:14:47 +0100	[thread overview]
Message-ID: <200612051214.47380.rjw@sisk.pl> (raw)
In-Reply-To: <200612042143.19264.david-b@pacbell.net>

On Tuesday, 5 December 2006 06:43, David Brownell wrote:
> [ off $SUBJECT ]
> 
> On Monday 04 December 2006 11:44 am, Pavel Machek wrote:
> > > But I think I'll need to add TIF_FROZEN for all architectures, because suspend
> > > to RAM is supposed to work on all of them, isn't it?
> > 
> > Well, yes, it should be added, but no, I do not think s2ram works on
> > that many machines.
> 
> Userspace "s2ram" != PM_SUSPEND_MEM ("suspend-to-RAM") though.
> 
> I'm not even sure there's a globally acceptable definition of
> what PM_SUSPEND_MEM indicates, beyond the fact that one expects
> it saves more power than PM_SUSPEND_STANDBY.
> 
> Yes, the Documentation/power/states.txt regurgitates ACPI spec text.
> But lots of non-ACPI systems don't have any reason to do things
> like ACPI says.  And in terms of latency, I've seen a lot of that
> be due to the PM framework taking so long to walk the device tree,
> with no substantial difference between "standby" and "str" costs.

Well, in this particular case the question is only which architectures will
actually use the freezer. :-)

Greetings,
Rafael


-- 
If you don't have the time to read,
you don't have the time or the tools to write.
		- Stephen King

      reply	other threads:[~2006-12-05 11:14 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 22:18 [PATCH -mm 0/2]: SMP-safe freezer Rafael J. Wysocki
2006-12-03 22:50 ` [PATCH -mm 1/2]: PM: Fix handling of stopped tasks Rafael J. Wysocki
2006-12-05 10:25   ` Pavel Machek
2006-12-05 10:34   ` Pavel Machek
2006-12-05 11:06     ` Rafael J. Wysocki
2006-12-05 14:13       ` Pavel Machek
2006-12-05 14:22         ` Rafael J. Wysocki
2006-12-05 11:24     ` Pavel Machek
2006-12-05 11:38       ` Rafael J. Wysocki
2006-12-05 14:12         ` Pavel Machek
2006-12-05 14:26           ` Rafael J. Wysocki
2006-12-05 14:33             ` Rafael J. Wysocki
2006-12-05 15:27             ` Pavel Machek
2006-12-05 17:22               ` Rafael J. Wysocki
2006-12-05 21:03     ` Rafael J. Wysocki
2006-12-05 21:26       ` Rafael J. Wysocki
2006-12-05 21:42         ` [Suspend-devel] " Rafael J. Wysocki
2006-12-05 22:19       ` Pavel Machek
2006-12-05 22:18         ` Rafael J. Wysocki
2006-12-06  0:07           ` [linux-pm] " Nigel Cunningham
2006-12-05 22:36       ` Pavel Machek
2006-12-05 22:45         ` Rafael J. Wysocki
2006-12-05 23:08           ` Rafael J. Wysocki
2006-12-05 23:45             ` Pavel Machek
2006-12-06  0:02               ` [Suspend-devel] " Nigel Cunningham
2006-12-06 23:13               ` Rafael J. Wysocki
2006-12-08 11:21                 ` Pavel Machek
2006-12-08 11:49                   ` Rafael J. Wysocki
2006-12-08 13:05                     ` Rafael J. Wysocki
2006-12-08 22:07                     ` Rafael J. Wysocki
2006-12-08 23:36                       ` Pavel Machek
2006-12-09 15:35                         ` Rafael J. Wysocki
2006-12-10  0:27                           ` Rafael J. Wysocki
2006-12-10 10:45                             ` Rafael J. Wysocki
2006-12-10 20:00                               ` Pavel Machek
2006-12-10 11:26                     ` Rafael J. Wysocki
2006-12-03 23:10 ` [PATCH -mm 2/2]: PM: SMP-safe freezer Rafael J. Wysocki
2006-12-04 10:30   ` Pavel Machek
2006-12-04 14:03     ` Rafael J. Wysocki
2006-12-04 19:44       ` Pavel Machek
2006-12-04 19:56         ` Rafael J. Wysocki
2006-12-05  5:43         ` [linux-pm] " David Brownell
2006-12-05 11:14           ` Rafael J. Wysocki [this message]

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=200612051214.47380.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    --cc=shemminger@osdl.org \
    --cc=suspend-devel@lists.sourceforge.net \
    /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