From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] More fixes for lazy IRQ vs. idle
Date: Tue, 10 Jul 2012 17:49:40 +1000 [thread overview]
Message-ID: <1341906580.2561.13.camel@pasglop> (raw)
In-Reply-To: <21083.1341900615@neuling.org>
On Tue, 2012-07-10 at 16:10 +1000, Michael Neuling wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > Looks like we still have issues with pSeries and Cell idle code
> > vs. the lazy irq state. In fact, the reset fixes that went upstream
> > are exposing the problem more by causing BUG_ON() to trigger (which
> > this patch turns into a WARN_ON instead).
>
> Do we need to cc stable for 3.4 or is this new stuff only effecting us
> since the 3.5 merge window?
That's probably stable business, I'll check that before I send it to
Linus.
Cheers,
Ben.
next prev parent reply other threads:[~2012-07-10 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 3:38 [PATCH] More fixes for lazy IRQ vs. idle Benjamin Herrenschmidt
2012-07-10 6:10 ` Michael Neuling
2012-07-10 7:49 ` Benjamin Herrenschmidt [this message]
2012-07-10 8:26 ` Benjamin Herrenschmidt
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=1341906580.2561.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
/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).