summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/include/asm/asm-compat.h
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2010-01-31 21:34:36 +0100
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2010-02-17 04:02:49 +0100
commit17081102a6e0fe32cf47cdbdf8f2e9ab55273b08 (patch)
tree6bbe3f22d4414598cdfdb69510f0679b90c68175 /arch/powerpc/include/asm/asm-compat.h
parentpowerpc: Add timer, performance monitor and machine check counts to /proc/int... (diff)
downloadlinux-17081102a6e0fe32cf47cdbdf8f2e9ab55273b08.tar.xz
linux-17081102a6e0fe32cf47cdbdf8f2e9ab55273b08.zip
powerpc: Convert global "BAD" interrupt to per cpu spurious
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>
Diffstat (limited to 'arch/powerpc/include/asm/asm-compat.h')
0 files changed, 0 insertions, 0 deletions