projects/linux·commit d7226fb6

Revert "genirq: assert that irq handlers are indeed running in hardirq context"

d7226fb6 · Thomas Gleixner <[email protected]> · 2009-05-01 15:16:04 +02:00

This reverts commit 044d408409cc4e1bc75c886e27ca85c270db104c.

The commit added a warning when handle_IRQ_event() is called outside
of hard interrupt context. This breaks the generic tasklet based
interrupt resend mechanism which is used when the hardware has no way
to retrigger the interrupt. So we get a warning for a use case which
is correct and worked for years. Remove it.

Signed-off-by: Thomas Gleixner <[email protected]>
Commit
d7226fb6ec5d4f325e4e7fd905894e2ea3eb3ae0
Parents
091438dd

Changes

1 files changed · +0 −2

FileStatusAddDelContent
kernel/irq/handle.cmodified+0−2View file

kernel/irq/handle.c

View file
diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
index d82142b..26e0875 100644
--- a/kernel/irq/handle.c
+++ b/kernel/irq/handle.c
@@ -363,8 +363,6 @@ irqreturn_t handle_IRQ_event(unsigned int irq, struct irqaction *action)
irqreturn_t ret, retval = IRQ_NONE;
unsigned int status = 0;
- WARN_ONCE(!in_irq(), "BUG: IRQ handler called from non-hardirq context!");
-
if (!(action->flags & IRQF_DISABLED))
local_irq_enable_in_hardirq();