[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1183472474.3722.13.camel@johannes.berg>
Date: Tue, 03 Jul 2007 16:21:14 +0200
From: Johannes Berg <johannes@...solutions.net>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>,
linux-pm@...ts.linux-foundation.org
Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to
RAM pathway
On Tue, 2007-07-03 at 14:56 +0200, Rafael J. Wysocki wrote:
> Still, can you please read this post from Alan Stern:
>
> https://lists.linux-foundation.org/pipermail/linux-pm/2007-June/012847.html
>
> ? I don't think I'm able to repeat the arguments given in there in a
> convincing way.
As I read it, Alan basically has two objections:
(1) drivers shouldn't need to worry about this
(2) suspend should be transparent to userspace
His proposed solution (freezing tasks when they cross the kernel
boundary) helps for the s-t-r case, but in fact doesn't solve (1)
because devices can be suspended at runtime and then you certainly do
not want to freeze tasks that try to access the device.
(2) is related but not identical, what if you have a device suspended at
runtime and some tasks tries to access it; should the task block until
you wake up that device?
I think the core of the discussion isn't appreciated by everybody here
yet---we need to solve both run-time and suspend-to-ram-time device
suspend, not just one of them.
johannes
Download attachment "signature.asc" of type "application/pgp-signature" (191 bytes)
Powered by blists - more mailing lists