From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@osdl.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
johannes@sipsolutions.net, cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Make cpufreq_transition_notifier a raw notifier
Date: Fri, 26 May 2006 09:18:23 +1000 [thread overview]
Message-ID: <1148599103.10832.5.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0605251332260.8473-100000@iolanthe.rowland.org>
On Thu, 2006-05-25 at 13:53 -0400, Alan Stern wrote:
> The cpufreq code has problems with atomic vs. blocking notifier calls and
> enabling vs. disabling interrupts (show up on pmac). As a temporary
> band-aid, this patch (as697) makes the cpufreq_transition_notifier_list
> into a raw notifier.
Thanks Alan. That should fix our warning for now, though we'll have to
sync with brodo to get cpufreq right. As I explained separately, I think
part of the problem is bcs cpufreq is a sysdev, it shouldn't have to be,
at least not necessarily. I'm worried that even if they work in atomic
context, some drivers who hook on the cpufreq events might still be
buggy when notified so late in the sleep process.
prev parent reply other threads:[~2006-05-25 23:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1148531830.13249.237.camel@localhost.localdomain>
2006-05-25 4:59 ` [Fwd: Re: via-pmu runs device_power_down in atomic context] Andrew Morton
2006-05-25 5:19 ` Benjamin Herrenschmidt
2006-05-25 5:36 ` Andrew Morton
2006-05-25 5:46 ` Benjamin Herrenschmidt
2006-05-25 5:53 ` Benjamin Herrenschmidt
2006-05-25 5:44 ` Benjamin Herrenschmidt
2006-05-25 14:12 ` Alan Stern
2006-05-25 14:44 ` Andrew Morton
2006-05-25 16:44 ` Jon Loeliger
2006-05-25 17:53 ` [PATCH] Make cpufreq_transition_notifier a raw notifier Alan Stern
2006-05-25 18:41 ` Johannes Berg
2006-05-25 19:14 ` Alan Stern
2006-05-25 23:18 ` Benjamin Herrenschmidt [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=1148599103.10832.5.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).