Re: [patch] __do_IRQ does not check IRQ_DISABLED when IRQ_PER_CPU is set

2007-10-31 Thread Russ Anderson
On Wed, Oct 31, 2007 at 09:20:27AM -0700, Luck, Tony wrote: > > One user encountering this behavior is the CPE handler (in > > arch/ia64/kernel/mca.c). When the CPE handler encounters too many > > CPEs (such as a solid single bit error), it sets up a polling timer > > and disables the CPE interru

RE: [patch] __do_IRQ does not check IRQ_DISABLED when IRQ_PER_CPU is set

2007-10-31 Thread Luck, Tony
> One user encountering this behavior is the CPE handler (in > arch/ia64/kernel/mca.c). When the CPE handler encounters too many > CPEs (such as a solid single bit error), it sets up a polling timer > and disables the CPE interrupt (to avoid excessive overhead logging > the stream of single bit e

Re: [patch] __do_IRQ does not check IRQ_DISABLED when IRQ_PER_CPU is set

2007-10-30 Thread Andrew Morton
On Tue, 30 Oct 2007 11:26:57 -0500 Russ Anderson <[EMAIL PROTECTED]> wrote: > [patch] __do_IRQ does not check IRQ_DISABLED when IRQ_PER_CPU is set > > In __do_IRQ(), the normal case is that IRQ_DISABLED is checked and if > set the handler (handle_IRQ_event()) is not called.

[patch] __do_IRQ does not check IRQ_DISABLED when IRQ_PER_CPU is set

2007-10-30 Thread Russ Anderson
[patch] __do_IRQ does not check IRQ_DISABLED when IRQ_PER_CPU is set In __do_IRQ(), the normal case is that IRQ_DISABLED is checked and if set the handler (handle_IRQ_event()) is not called. Earlier in __do_IRQ(), if IRQ_PER_CPU is set the code does not check IRQ_DISABLED and calls the handler