mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-25 21:54:06 +08:00
17081102a6
I often get asked if BAD interrupts are really bad. On some boxes (eg IBM machines running a hypervisor) there are valid cases where are presented with an interrupt that is not for us. These cases are common enough to show up as thousands of BAD interrupts a day. Tone them down by calling them spurious. Since they can be a significant cause of OS jitter, we may as well log them per cpu so we know where they are occurring. Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
30 lines
718 B
C
30 lines
718 B
C
#ifndef _ASM_POWERPC_HARDIRQ_H
|
|
#define _ASM_POWERPC_HARDIRQ_H
|
|
|
|
#include <linux/threads.h>
|
|
#include <linux/irq.h>
|
|
|
|
typedef struct {
|
|
unsigned int __softirq_pending;
|
|
unsigned int timer_irqs;
|
|
unsigned int pmu_irqs;
|
|
unsigned int mce_exceptions;
|
|
unsigned int spurious_irqs;
|
|
} ____cacheline_aligned irq_cpustat_t;
|
|
|
|
DECLARE_PER_CPU_SHARED_ALIGNED(irq_cpustat_t, irq_stat);
|
|
|
|
#define __ARCH_IRQ_STAT
|
|
|
|
#define local_softirq_pending() __get_cpu_var(irq_stat).__softirq_pending
|
|
|
|
static inline void ack_bad_irq(unsigned int irq)
|
|
{
|
|
printk(KERN_CRIT "unexpected IRQ trap at vector %02x\n", irq);
|
|
}
|
|
|
|
extern u64 arch_irq_stat_cpu(unsigned int cpu);
|
|
#define arch_irq_stat_cpu arch_irq_stat_cpu
|
|
|
|
#endif /* _ASM_POWERPC_HARDIRQ_H */
|