You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Alan Cox 4f27c00bf8 Improve behaviour of spurious IRQ detect ... Currently we handle spurious IRQ activity based upon seeing a lot of invalid interrupts, and we clear things back on the base of lots of valid interrupts. Unfortunately in some cases you get legitimate invalid interrupts caused by timing asynchronicity between the PCI bus and the APIC bus when disabling interrupts and pulling other tricks. In this case although the spurious IRQs are not a problem our unhandled counters didn't clear and they act as a slow running timebomb. (This is effectively what the serial port/tty problem that was fixed by clearing counters when registering a handler showed up) It's easy enough to add a second parameter - time. This means that if we see a regular stream of harmless spurious interrupts which are not harming processing we don't go off and do something stupid like disable the IRQ after a month of running. OTOH lockups and performance killers show up a lot more than 10/second [akpm@linux-foundation.org: cleanup] Signed-off-by: Alan Cox <alan@redhat.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		18 years ago
..
Makefile	…
autoprobe.c	…
chip.c	MSI: arch must connect the irq and the msi_desc	18 years ago
devres.c	…
handle.c	Fix Linuxdoc comment	18 years ago
internals.h	…
manage.c	IRQ: check for PERCPU flag only when adding first irqaction	18 years ago
migration.c	…
proc.c	[IA64] SN: validate smp_affinity mask on intr redirect	18 years ago
resend.c	…
spurious.c	Improve behaviour of spurious IRQ detect	18 years ago