public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Jan-Bernd Themann <themann@de.ibm.com>,
	dvhltc@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	Will Schmidt <will_schmidt@vnet.ibm.com>,
	Brian King <brking@linux.vnet.ibm.com>,
	niv@linux.vnet.ibm.com, Thomas Gleixner <tglx@linutronix.de>,
	Doug Maxey <doug.maxey@us.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH RT] ehea: make receive irq handler non-threaded (IRQF_NODELAY)
Date: Wed, 19 May 2010 11:25:24 +1000	[thread overview]
Message-ID: <1274232324.29980.9.camel@concordia> (raw)
In-Reply-To: <4BF31322.5090206@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 656 bytes --]

On Tue, 2010-05-18 at 15:22 -0700, Darren Hart wrote:
> On 05/18/2010 02:52 PM, Brian King wrote:
> > Is IRQF_NODELAY something specific to the RT kernel? I don't see it in mainline...
> 
> Yes, it basically says "don't make this handler threaded".

That is a good fix for EHEA, but the threaded handling is still broken
for anything else that is edge triggered isn't it?

The result of the discussion about two years ago on this was that we
needed a custom flow handler for XICS on RT.

Apart from the issue of loosing interrupts there is also the fact that
masking on the XICS requires an RTAS call which takes a global lock.

cheers



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-05-19  1:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4BF30793.5070300@us.ibm.com>
2010-05-18 21:52 ` [PATCH RT] ehea: make receive irq handler non-threaded (IRQF_NODELAY) Brian King
2010-05-18 22:19   ` Nivedita Singhvi
2010-05-18 22:22   ` Darren Hart
2010-05-19  1:25     ` Michael Ellerman [this message]
2010-05-19 14:16       ` Darren Hart
2010-05-19 14:38         ` Thomas Gleixner
2010-05-19 21:08           ` Thomas Gleixner
2010-05-20  1:34             ` Michael Ellerman
2010-05-20  7:37               ` Jan-Bernd Themann
2010-05-20  8:14                 ` Thomas Gleixner
2010-05-20  9:05                   ` Jan-Bernd Themann
2010-05-20  9:19                     ` Thomas Gleixner
2010-05-20 14:26                       ` Nivedita Singhvi
2010-05-20 14:53                     ` Will Schmidt
2010-05-20 14:39                   ` Darren Hart
2010-05-20 14:45                     ` Thomas Gleixner
2010-05-20 21:44                       ` Will Schmidt
2010-05-20  1:32           ` Michael Ellerman
2010-05-20  8:21             ` Thomas Gleixner
2010-05-21  9:18               ` [PATCH RT] ehea: make receive irq handler non-threaded (IRQF_NODELAY), " Milton Miller
2010-09-20 14:26                 ` Jan-Bernd Themann
2010-05-20  1:28         ` Michael Ellerman
2010-05-21  9:02           ` Milton Miller

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=1274232324.29980.9.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=brking@linux.vnet.ibm.com \
    --cc=doug.maxey@us.ibm.com \
    --cc=dvhltc@linux.vnet.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=niv@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=themann@de.ibm.com \
    --cc=will_schmidt@vnet.ibm.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