From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Johannes Berg <johannes@sipsolutions.net>,
David Woodhouse <dwmw2@infradead.org>,
linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] Re: [RFC] powermac: proper sleep management
Date: Tue, 13 Nov 2007 07:56:38 +1100 [thread overview]
Message-ID: <1194900998.18185.57.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0711121534070.3128-100000@netrider.rowland.org>
On Mon, 2007-11-12 at 15:40 -0500, Alan Stern wrote:
> On Tue, 13 Nov 2007, Benjamin Herrenschmidt wrote:
>
> >
> > On Mon, 2007-11-12 at 17:32 +0100, Johannes Berg wrote:
> > > > Looks good to me, +/- a couple of things:
> > > >
> > > > - We _REALLY_ want the freezer to be optional and not enabled by
> > > > default on PowerPC. Maybe make it a compile option ?
> > >
> > > Well, Alan is going to tell you that USB will break. If we need
> > > confirmation for that I can do the test he suggested to you or Paul a
> > > while ago.
> >
> > Then USB is broken today on powermacs and need to be fixed. We had a
> > clear agreement at KS this year that the freezer was at best a band-aid
> > and that drivers -had- to be fixed to cope regardless.
>
> More accurately, freezing user tasks is at best a band-aid. However
> some kernel threads do need to be frozen, and keeping the freezer
> around for their use makes sense. It has less overhead -- I think
> -- than adding new code to do the freezing in each of these threads.
I remember fixing various issues so that khubd would be safe when non
frozen (among other things) a while ago. Did you guys break it all
again ?
Ben.
next prev parent reply other threads:[~2007-11-12 20:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 12:08 [RFC] powermac: proper sleep management Johannes Berg
2007-11-08 12:08 ` Johannes Berg
2007-11-08 19:15 ` Scott Wood
2007-11-08 23:19 ` Benjamin Herrenschmidt
2007-11-08 23:19 ` Benjamin Herrenschmidt
2007-11-08 19:15 ` Scott Wood
2007-11-11 13:35 ` Pavel Machek
2007-11-11 13:35 ` [linux-pm] " Pavel Machek
2007-11-11 20:59 ` Benjamin Herrenschmidt
2007-11-11 20:59 ` Benjamin Herrenschmidt
2007-11-12 16:32 ` Johannes Berg
2007-11-12 19:52 ` Alan Stern
2007-11-12 19:52 ` [linux-pm] " Alan Stern
2007-11-13 13:19 ` Johannes Berg
2007-11-13 13:19 ` [linux-pm] " Johannes Berg
2007-11-12 20:24 ` Benjamin Herrenschmidt
2007-11-12 20:24 ` Benjamin Herrenschmidt
2007-11-12 20:40 ` Alan Stern
2007-11-12 20:40 ` [linux-pm] " Alan Stern
2007-11-12 20:56 ` Benjamin Herrenschmidt
2007-11-12 20:56 ` Benjamin Herrenschmidt [this message]
2007-11-12 21:52 ` [linux-pm] " Alan Stern
2007-11-12 21:52 ` Alan Stern
2007-11-12 16:32 ` 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=1194900998.18185.57.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.