diff options
| author | Thomas Gleixner <tglx@linutronix.de> | 2008-01-30 13:30:19 +0100 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-01-30 13:30:19 +0100 |
| commit | 87ebecf14ca4f669cb52be46c954f3d9201394b8 (patch) | |
| tree | f36b8072bc081b3f483c29e5394ab96cdf501201 /arch/x86/kernel/apic_64.c | |
| parent | x86: move ioapic code where it belongs (diff) | |
| download | linux-87ebecf14ca4f669cb52be46c954f3d9201394b8.tar.xz linux-87ebecf14ca4f669cb52be46c954f3d9201394b8.zip | |
x86: move ack_bad_irq into irq code
Match i386, where we have this in the irq code. It belongs there.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86/kernel/apic_64.c')
| -rw-r--r-- | arch/x86/kernel/apic_64.c | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/arch/x86/kernel/apic_64.c b/arch/x86/kernel/apic_64.c index e0191cdd6f7a..032bf1e765df 100644 --- a/arch/x86/kernel/apic_64.c +++ b/arch/x86/kernel/apic_64.c @@ -169,26 +169,6 @@ int lapic_get_maxlvt(void) return maxlvt; } -/* - * 'what should we do if we get a hw irq event on an illegal vector'. - * each architecture has to answer this themselves. - */ -void ack_bad_irq(unsigned int irq) -{ - printk("unexpected IRQ trap at vector %02x\n", irq); - /* - * Currently unexpected vectors happen only on SMP and APIC. - * We _must_ ack these because every local APIC has only N - * irq slots per priority level, and a 'hanging, unacked' IRQ - * holds up an irq slot - in excessive cases (when multiple - * unexpected vectors occur) that might lock up the APIC - * completely. - * But don't ack when the APIC is disabled. -AK - */ - if (!disable_apic) - ack_APIC_irq(); -} - void clear_local_APIC(void) { int maxlvt; |