From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Scott Wood <scottwood@freescale.com>,
Stuart Yoder <b08248@gmail.com>,
Anton Blanchard <anton@au1.ibm.com>,
Laurentiu Tudor <Laurentiu.Tudor@freescale.com>,
Paul Mackerras <pmac@au1.ibm.com>
Subject: Re: [PATCH v3] powerpc: Rework lazy-interrupt handling
Date: Wed, 15 Feb 2012 11:01:45 +1100 [thread overview]
Message-ID: <1329264105.3772.12.camel@pasglop> (raw)
In-Reply-To: <1329201969.3772.7.camel@pasglop>
On Tue, 2012-02-14 at 17:46 +1100, Benjamin Herrenschmidt wrote:
> The current implementation of lazy interrupts handling has some
> issues that this tries to address.
>
> Except on iSeries, we don't do the various workarounds we need to
> do on re-enable when returning from an interrupt, which can do an
> implicit re-enable, and thus we may still lose or get delayed
> decrementer or doorbell interrupts.
.../...
So we were still losing doorbells on BookE due to a st00pid thinko on my
part :-) New patch following, hopefully that one's good !
Cheers,
Ben.
prev parent reply other threads:[~2012-02-15 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 6:46 [PATCH v3] powerpc: Rework lazy-interrupt handling Benjamin Herrenschmidt
2012-02-15 0:01 ` 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=1329264105.3772.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Laurentiu.Tudor@freescale.com \
--cc=anton@au1.ibm.com \
--cc=b08248@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pmac@au1.ibm.com \
--cc=scottwood@freescale.com \
/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).