2008-10-23 13:26:29 +08:00
|
|
|
#ifndef _ASM_X86_IRQ_VECTORS_H
|
|
|
|
|
#define _ASM_X86_IRQ_VECTORS_H
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2011-01-17 10:52:02 +08:00
|
|
|
#include <linux/threads.h>
|
2009-01-31 09:48:17 +08:00
|
|
|
/*
|
|
|
|
|
* Linux IRQ vector layout.
|
|
|
|
|
*
|
|
|
|
|
* There are 256 IDT entries (per CPU - each entry is 8 bytes) which can
|
|
|
|
|
* be defined by Linux. They are used as a jump table by the CPU when a
|
|
|
|
|
* given vector is triggered - by a CPU-external, CPU-internal or
|
|
|
|
|
* software-triggered event.
|
|
|
|
|
*
|
|
|
|
|
* Linux sets the kernel code address each entry jumps to early during
|
|
|
|
|
* bootup, and never changes them. This is the general layout of the
|
|
|
|
|
* IDT entries:
|
|
|
|
|
*
|
|
|
|
|
* Vectors 0 ... 31 : system traps and exceptions - hardcoded events
|
|
|
|
|
* Vectors 32 ... 127 : device interrupts
|
|
|
|
|
* Vector 128 : legacy int80 syscall interface
|
2011-06-06 01:50:24 +08:00
|
|
|
* Vectors 129 ... INVALIDATE_TLB_VECTOR_START-1 except 204 : device interrupts
|
2011-01-17 10:52:07 +08:00
|
|
|
* Vectors INVALIDATE_TLB_VECTOR_START ... 255 : special interrupts
|
2009-01-31 09:48:17 +08:00
|
|
|
*
|
|
|
|
|
* 64-bit x86 has per CPU IDT tables, 32-bit has one shared IDT table.
|
|
|
|
|
*
|
|
|
|
|
* This file enumerates the exact layout of them:
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#define NMI_VECTOR 0x02
|
2009-05-28 03:56:58 +08:00
|
|
|
#define MCE_VECTOR 0x12
|
2008-05-03 02:10:09 +08:00
|
|
|
|
|
|
|
|
/*
|
2010-01-14 08:19:11 +08:00
|
|
|
* IDT vectors usable for external interrupt sources start at 0x20.
|
|
|
|
|
* (0x80 is the syscall vector, 0x30-0x3f are for ISA)
|
2008-05-03 02:10:09 +08:00
|
|
|
*/
|
2010-01-14 08:19:11 +08:00
|
|
|
#define FIRST_EXTERNAL_VECTOR 0x20
|
|
|
|
|
/*
|
|
|
|
|
* We start allocating at 0x21 to spread out vectors evenly between
|
|
|
|
|
* priority levels. (0x80 is the syscall vector)
|
|
|
|
|
*/
|
|
|
|
|
#define VECTOR_OFFSET_START 1
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Reserve the lowest usable vector (and hence lowest priority) 0x20 for
|
|
|
|
|
* triggering cleanup after irq migration. 0x21-0x2f will still be used
|
|
|
|
|
* for device interrupts.
|
|
|
|
|
*/
|
|
|
|
|
#define IRQ_MOVE_CLEANUP_VECTOR FIRST_EXTERNAL_VECTOR
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2010-01-05 08:16:06 +08:00
|
|
|
#define IA32_SYSCALL_VECTOR 0x80
|
2008-05-03 02:10:09 +08:00
|
|
|
|
|
|
|
|
/*
|
2010-01-14 08:19:11 +08:00
|
|
|
* Vectors 0x30-0x3f are used for ISA interrupts.
|
2010-01-05 08:16:06 +08:00
|
|
|
* round up to the next 16-vector boundary
|
2008-05-03 02:10:09 +08:00
|
|
|
*/
|
2015-05-09 23:36:53 +08:00
|
|
|
#define ISA_IRQ_VECTOR(irq) (((FIRST_EXTERNAL_VECTOR + 16) & ~15) + irq)
|
2008-05-03 02:10:09 +08:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Special IRQ vectors used by the SMP architecture, 0xf0-0xff
|
|
|
|
|
*
|
|
|
|
|
* some of the following vectors are 'rare', they are merged
|
|
|
|
|
* into a single vector (CALL_FUNCTION_VECTOR) to save vector space.
|
|
|
|
|
* TLB, reschedule and local APIC vectors are performance-critical.
|
|
|
|
|
*/
|
2009-01-21 16:26:06 +08:00
|
|
|
|
2009-01-31 09:10:03 +08:00
|
|
|
#define SPURIOUS_APIC_VECTOR 0xff
|
2009-01-31 09:06:50 +08:00
|
|
|
/*
|
|
|
|
|
* Sanity check
|
|
|
|
|
*/
|
|
|
|
|
#if ((SPURIOUS_APIC_VECTOR & 0x0F) != 0x0F)
|
|
|
|
|
# error SPURIOUS_APIC_VECTOR definition error
|
|
|
|
|
#endif
|
|
|
|
|
|
2009-01-31 09:10:03 +08:00
|
|
|
#define ERROR_APIC_VECTOR 0xfe
|
|
|
|
|
#define RESCHEDULE_VECTOR 0xfd
|
|
|
|
|
#define CALL_FUNCTION_VECTOR 0xfc
|
|
|
|
|
#define CALL_FUNCTION_SINGLE_VECTOR 0xfb
|
|
|
|
|
#define THERMAL_APIC_VECTOR 0xfa
|
2009-04-29 05:32:56 +08:00
|
|
|
#define THRESHOLD_APIC_VECTOR 0xf9
|
x86: fix panic with interrupts off (needed for MCE)
For some time each panic() called with interrupts disabled
triggered the !irqs_disabled() WARN_ON in smp_call_function(),
producing ugly backtraces and confusing users.
This is a common situation with machine checks for example which
tend to call panic with interrupts disabled, but will also hit
in other situations e.g. panic during early boot. In fact it
means that panic cannot be called in many circumstances, which
would be bad.
This all started with the new fancy queued smp_call_function,
which is then used by the shutdown path to shut down the other
CPUs.
On closer examination it turned out that the fancy RCU
smp_call_function() does lots of things not suitable in a panic
situation anyways, like allocating memory and relying on complex
system state.
I originally tried to patch this over by checking for panic
there, but it was quite complicated and the original patch
was also not very popular. This also didn't fix some of the
underlying complexity problems.
The new code in post 2.6.29 tries to patch around this by
checking for oops_in_progress, but that is not enough to make
this fully safe and I don't think that's a real solution
because panic has to be reliable.
So instead use an own vector to reboot. This makes the reboot
code extremly straight forward, which is definitely a big plus
in a panic situation where it is important to avoid relying on
too much kernel state. The new simple code is also safe to be
called from interupts off region because it is very very simple.
There can be situations where it is important that panic
is reliable. For example on a fatal machine check the panic
is needed to get the system up again and running as quickly
as possible. So it's important that panic is reliable and
all function it calls simple.
This is why I came up with this simple vector scheme.
It's very hard to beat in simplicity. Vectors are not
particularly precious anymore since all big systems are
using per CPU vectors.
Another possibility would have been to use an NMI similar
to kdump, but there is still the problem that NMIs don't
work reliably on some systems due to BIOS issues. NMIs
would have been able to stop CPUs running with interrupts
off too. In the sake of universal reliability I opted for
using a non NMI vector for now.
I put the reboot vector into the highest priority bucket of
the APIC vectors and moved the 64bit UV_BAU message down
instead into the next lower priority.
[ Impact: bug fix, fixes an old regression ]
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-05-28 03:56:52 +08:00
|
|
|
#define REBOOT_VECTOR 0xf8
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2009-01-31 09:23:27 +08:00
|
|
|
/*
|
2009-03-05 02:56:05 +08:00
|
|
|
* Generic system vector for platform specific use
|
2009-01-31 09:23:27 +08:00
|
|
|
*/
|
2011-01-17 10:52:02 +08:00
|
|
|
#define X86_PLATFORM_IPI_VECTOR 0xf7
|
2009-01-31 09:23:27 +08:00
|
|
|
|
2015-05-19 17:07:16 +08:00
|
|
|
#define POSTED_INTR_WAKEUP_VECTOR 0xf1
|
2009-03-05 02:56:05 +08:00
|
|
|
/*
|
2010-10-14 14:01:34 +08:00
|
|
|
* IRQ work vector:
|
2009-03-05 02:56:05 +08:00
|
|
|
*/
|
2011-01-17 10:52:02 +08:00
|
|
|
#define IRQ_WORK_VECTOR 0xf6
|
2009-03-05 02:56:05 +08:00
|
|
|
|
2011-01-17 10:52:02 +08:00
|
|
|
#define UV_BAU_MESSAGE 0xf5
|
2015-05-06 19:58:56 +08:00
|
|
|
#define DEFERRED_ERROR_VECTOR 0xf4
|
x86: fix panic with interrupts off (needed for MCE)
For some time each panic() called with interrupts disabled
triggered the !irqs_disabled() WARN_ON in smp_call_function(),
producing ugly backtraces and confusing users.
This is a common situation with machine checks for example which
tend to call panic with interrupts disabled, but will also hit
in other situations e.g. panic during early boot. In fact it
means that panic cannot be called in many circumstances, which
would be bad.
This all started with the new fancy queued smp_call_function,
which is then used by the shutdown path to shut down the other
CPUs.
On closer examination it turned out that the fancy RCU
smp_call_function() does lots of things not suitable in a panic
situation anyways, like allocating memory and relying on complex
system state.
I originally tried to patch this over by checking for panic
there, but it was quite complicated and the original patch
was also not very popular. This also didn't fix some of the
underlying complexity problems.
The new code in post 2.6.29 tries to patch around this by
checking for oops_in_progress, but that is not enough to make
this fully safe and I don't think that's a real solution
because panic has to be reliable.
So instead use an own vector to reboot. This makes the reboot
code extremly straight forward, which is definitely a big plus
in a panic situation where it is important to avoid relying on
too much kernel state. The new simple code is also safe to be
called from interupts off region because it is very very simple.
There can be situations where it is important that panic
is reliable. For example on a fatal machine check the panic
is needed to get the system up again and running as quickly
as possible. So it's important that panic is reliable and
all function it calls simple.
This is why I came up with this simple vector scheme.
It's very hard to beat in simplicity. Vectors are not
particularly precious anymore since all big systems are
using per CPU vectors.
Another possibility would have been to use an NMI similar
to kdump, but there is still the problem that NMIs don't
work reliably on some systems due to BIOS issues. NMIs
would have been able to stop CPUs running with interrupts
off too. In the sake of universal reliability I opted for
using a non NMI vector for now.
I put the reboot vector into the highest priority bucket of
the APIC vectors and moved the 64bit UV_BAU message down
instead into the next lower priority.
[ Impact: bug fix, fixes an old regression ]
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-05-28 03:56:52 +08:00
|
|
|
|
2013-02-04 09:22:39 +08:00
|
|
|
/* Vector on which hypervisor callbacks will be delivered */
|
|
|
|
|
#define HYPERVISOR_CALLBACK_VECTOR 0xf3
|
2011-01-17 10:52:02 +08:00
|
|
|
|
2015-05-06 19:58:57 +08:00
|
|
|
/* Vector for KVM to deliver posted interrupt IPI */
|
|
|
|
|
#ifdef CONFIG_HAVE_KVM
|
|
|
|
|
#define POSTED_INTR_VECTOR 0xf2
|
|
|
|
|
#endif
|
|
|
|
|
|
2011-01-17 10:52:02 +08:00
|
|
|
/*
|
|
|
|
|
* Local APIC timer IRQ vector is on a different priority level,
|
|
|
|
|
* to work around the 'lost local interrupt if more than 2 IRQ
|
|
|
|
|
* sources per level' errata.
|
|
|
|
|
*/
|
|
|
|
|
#define LOCAL_TIMER_VECTOR 0xef
|
|
|
|
|
|
2009-01-31 09:48:17 +08:00
|
|
|
#define NR_VECTORS 256
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2014-11-03 16:39:43 +08:00
|
|
|
#ifdef CONFIG_X86_LOCAL_APIC
|
|
|
|
|
#define FIRST_SYSTEM_VECTOR LOCAL_TIMER_VECTOR
|
|
|
|
|
#else
|
|
|
|
|
#define FIRST_SYSTEM_VECTOR NR_VECTORS
|
|
|
|
|
#endif
|
|
|
|
|
|
2009-01-31 09:48:17 +08:00
|
|
|
#define FPU_IRQ 13
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2009-01-31 09:56:44 +08:00
|
|
|
/*
|
|
|
|
|
* Size the maximum number of interrupts.
|
|
|
|
|
*
|
|
|
|
|
* If the irq_desc[] array has a sparse layout, we can size things
|
|
|
|
|
* generously - it scales up linearly with the maximum number of CPUs,
|
|
|
|
|
* and the maximum number of IO-APICs, whichever is higher.
|
|
|
|
|
*
|
|
|
|
|
* In other cases we size more conservatively, to not create too large
|
|
|
|
|
* static arrays.
|
|
|
|
|
*/
|
|
|
|
|
|
2015-04-14 10:30:04 +08:00
|
|
|
#define NR_IRQS_LEGACY 16
|
2008-12-06 10:58:32 +08:00
|
|
|
|
2015-04-14 10:30:04 +08:00
|
|
|
#define CPU_VECTOR_LIMIT (64 * NR_CPUS)
|
|
|
|
|
#define IO_APIC_VECTOR_LIMIT (32 * MAX_IO_APICS)
|
2009-01-31 09:56:44 +08:00
|
|
|
|
2015-04-14 10:30:04 +08:00
|
|
|
#if defined(CONFIG_X86_IO_APIC) && defined(CONFIG_PCI_MSI)
|
|
|
|
|
#define NR_IRQS \
|
2009-01-31 09:56:44 +08:00
|
|
|
(CPU_VECTOR_LIMIT > IO_APIC_VECTOR_LIMIT ? \
|
|
|
|
|
(NR_VECTORS + CPU_VECTOR_LIMIT) : \
|
|
|
|
|
(NR_VECTORS + IO_APIC_VECTOR_LIMIT))
|
2015-04-14 10:30:04 +08:00
|
|
|
#elif defined(CONFIG_X86_IO_APIC)
|
|
|
|
|
#define NR_IRQS (NR_VECTORS + IO_APIC_VECTOR_LIMIT)
|
|
|
|
|
#elif defined(CONFIG_PCI_MSI)
|
|
|
|
|
#define NR_IRQS (NR_VECTORS + CPU_VECTOR_LIMIT)
|
|
|
|
|
#else
|
|
|
|
|
#define NR_IRQS NR_IRQS_LEGACY
|
2008-11-05 06:10:13 +08:00
|
|
|
#endif
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2008-10-23 13:26:29 +08:00
|
|
|
#endif /* _ASM_X86_IRQ_VECTORS_H */
|