On Wed, 19 May 2010, Darren Hart wrote:

On 05/18/2010 06:25 PM, Michael Ellerman wrote:

quoted

On Tue, 2010-05-18 at 15:22 -0700, Darren Hart wrote:

quoted

On 05/18/2010 02:52 PM, Brian King wrote:

quoted

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?

No, I don't believe so. Edge triggered interrupts that are reported as edge
triggered interrupts will use the edge handler (which was the approach
Sebastien took to make this work back in 2008). Since XICS presents all
interrupts as Level Triggered, they use the fasteoi path.

I wonder whether the XICS interrupts which are edge type can be
identified from the irq_desc->flags. Then we could avoid the masking
for those in the fasteoi_handler in general.

quoted

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

I'm still not clear on why the ultimate solution wasn't to have XICS report
edge triggered as edge triggered. Probably some complexity of the entire power
stack that I am ignorant of.

quoted

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.

Right, I'd love to avoid that but with real level interrupts we'd run
into an interrupt storm. Though another solution would be to issue the
EOI after the threaded handler finished, that'd work as well, but
needs testing.

Right, one of may reasons why we felt this was the right fix. The other is
that there is no real additional overhead in running this as non-threaded
since the receive handler is so short (just napi_schedule()).

Yes, in the case at hand it's the right thing to do, as we avoid
another wakeup/context switch.

Thanks,

	tglx