|
@@ -25,29 +25,6 @@ EXPORT_PER_CPU_SYMBOL(irq_stat);
|
|
|
DEFINE_PER_CPU(struct pt_regs *, irq_regs);
|
|
|
EXPORT_PER_CPU_SYMBOL(irq_regs);
|
|
|
|
|
|
-/*
|
|
|
- * '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(KERN_ERR "unexpected IRQ trap at vector %02x\n", irq);
|
|
|
-
|
|
|
-#ifdef CONFIG_X86_LOCAL_APIC
|
|
|
- /*
|
|
|
- * 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 only ack when the APIC is enabled -AK
|
|
|
- */
|
|
|
- if (cpu_has_apic)
|
|
|
- ack_APIC_irq();
|
|
|
-#endif
|
|
|
-}
|
|
|
-
|
|
|
#ifdef CONFIG_DEBUG_STACKOVERFLOW
|
|
|
/* Debugging check for stack overflow: is there less than 1KB free? */
|
|
|
static int check_stack_overflow(void)
|