[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090217142453.GA25530@srcf.ucam.org>
Date: Tue, 17 Feb 2009 14:24:53 +0000
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Brian Swetland <swetland@...gle.com>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Arjan van de Ven <arjan@...radead.org>,
"Woodruff, Richard" <r-woodruff2@...com>,
Alan Stern <stern@...land.harvard.edu>,
Kyle Moffett <kyle@...fetthome.net>,
Oliver Neukum <oliver@...kum.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Arve Hjønnevåg <arve@...roid.com>,
Pavel Machek <pavel@....cz>,
Nigel Cunningham <nigel@...el.suspend2.net>,
mark gross <mgross@...ux.intel.com>,
Uli Luckas <u.luckas@...d.de>,
Igor Stoppa <igor.stoppa@...ia.com>,
Len Brown <lenb@...nel.org>
Subject: Re: [RFD] Automatic suspend
On Tue, Feb 17, 2009 at 06:20:01AM -0800, Brian Swetland wrote:
> Of course that still doesn't address userspace. Aggressively going to
> suspend lets us compensate for userspace programs that do somewhat silly
> things (I agree that it would be best if they didn't but they do and
> getting *everyone* to write their userspace code to avoid spinning or
> avoid waking up on short-duration timers to poll is a losing battle).
Like Pavel pointed out, you could (in principle) handle this by sending
a SIGSTOP to everything. The obvious problem with doing so is that this
wouldn't result in the processes letting go of the devices, so you
wouldn't neccessarily actually get to enter the runtime idle state as a
result. Hmm. I'll think about this.
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists