android_kernel_xiaomi_sm8350/kernel/irq
Linus Torvalds b42172fc7b Don't call "note_interrupt()" with irq descriptor lock held
This reverts commit f72fa70760, and solves
the problem that it tried to fix by simply making "__do_IRQ()" call the
note_interrupt() function without the lock held, the way everybody else
does.

It should be noted that all interrupt handling code must never allow the
descriptor actors to be entered "recursively" (that's why we do all the
magic IRQ_PENDING stuff in the first place), so there actually is
exclusion at that much higher level, even in the absense of locking.

Acked-by: Vivek Goyal <vgoyal@in.ibm.com>
Acked-by:Pavel Emelianov <xemul@openvz.org>
Cc: Andrew Morton <akpm@osdl.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-11-22 09:32:06 -08:00
..
autoprobe.c
chip.c [PATCH] some irq_chip variables point to NULL 2006-11-16 11:43:37 -08:00
handle.c Don't call "note_interrupt()" with irq descriptor lock held 2006-11-22 09:32:06 -08:00
internals.h
Makefile
manage.c [PATCH] setup_irq(): better mismatch debugging 2006-11-14 09:09:26 -08:00
migration.c
proc.c
resend.c
spurious.c Don't call "note_interrupt()" with irq descriptor lock held 2006-11-22 09:32:06 -08:00