Re: [patch] x86, apic: use 0x20 for the IRQ_MOVE_CLEANUP_VECTOR instead of 0x1f

[Yinghai Lu]

On Fri, Jan 8, 2010 at 6:09 PM, Suresh Siddha <suresh.b.siddha@xxxxxxxxx> wrote:
> From: Suresh Siddha <suresh.b.siddha@xxxxxxxxx>
> Subject: x86, apic: use 0x20 for the IRQ_MOVE_CLEANUP_VECTOR instead of 0x1f
>
> After talking to some more folks inside intel (Peter Anvin, Asit Mallick),
> the safest option (for future compatibility etc) seen was to use vector 0x20
> for IRQ_MOVE_CLEANUP_VECTOR instead of using vector 0x1f (which is documented as
> reserved vector in the Intel IA32 manuals).
>
> Also we don't need to reserve the entire privilege level (all 16 vectors in
> the priority bucket that IRQ_MOVE_CLEANUP_VECTOR falls into), as the
> x86 architecture (section 10.9.3 in SDM Vol3a) specifies that with in the
> priority level, the higher the vector number the higher the priority.
> And hence we don't need to reserve the complete priority level 0x20-0x2f for
> the IRQ migration cleanup logic.
>
> So change the IRQ_MOVE_CLEANUP_VECTOR to 0x20 and  allow 0x21-0x2f to be used
> for device interrupts. 0x30-0x3f will be used for ISA interrupts (these
> also can be migrated in the context of IOAPIC and hence need to be at a higher
> priority level than IRQ_MOVE_CLEANUP_VECTOR).
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@xxxxxxxxx>
> ---
>
> diff --git a/arch/x86/include/asm/irq_vectors.h b/arch/x86/include/asm/irq_vectors.h
> index 585a428..708322a 100644
> --- a/arch/x86/include/asm/irq_vectors.h
> +++ b/arch/x86/include/asm/irq_vectors.h
> @@ -28,19 +28,15 @@
>  #define MCE_VECTOR                     0x12
>
>  /*
> - * IDT vectors usable for external interrupt sources start
> - * at 0x20:
> - * hpa said we can start from 0x1f.
> - *   0x1f is documented as reserved.  However, the ability for the APIC
> - *   to generate vectors starting at 0x10 is documented, as is the
> - *   ability for the CPU to receive any vector number as an interrupt.
> - *   0x1f is used for IRQ_MOVE_CLEANUP_VECTOR since that vector needs
> - *   an entire privilege level (16 vectors) all by itself at a higher
> - *   priority than any actual device vector.  Thus, by placing it in the
> - *   otherwise-unusable 0x10 privilege level, we avoid wasting a full
> - *   16-vector block.
> + * IDT vectors usable for external interrupt sources start at 0x20.
>  */
> -#define FIRST_EXTERNAL_VECTOR          0x1f
> +#define FIRST_EXTERNAL_VECTOR          0x20
> +
> +/*
> + * Reserve the lowest usable vector (and hence lowest priority)  0x20 for
> + * triggering cleanup after irq migration.
> + */
> +#define IRQ_MOVE_CLEANUP_VECTOR                FIRST_EXTERNAL_VECTOR
>
>  #define IA32_SYSCALL_VECTOR            0x80
>  #ifdef CONFIG_X86_32
> @@ -48,17 +44,7 @@
>  #endif
>
>  /*
> - * Reserve the lowest usable priority level 0x10 - 0x1f for triggering
> - * cleanup after irq migration.
> - * this overlaps with the reserved range for cpu exceptions so this
> - * will need to be changed to 0x20 - 0x2f if the last cpu exception is
> - * ever allocated.
> - */
> -
> -#define IRQ_MOVE_CLEANUP_VECTOR                FIRST_EXTERNAL_VECTOR
> -
> -/*
> - * Vectors 0x20-0x2f are used for ISA interrupts.
> + * Vectors 0x30-0x3f are used for ISA interrupts.
>  *   round up to the next 16-vector boundary
>  */
>  #define IRQ0_VECTOR                    ((FIRST_EXTERNAL_VECTOR + 16) & ~15)
> @@ -80,6 +66,12 @@
>  #define IRQ15_VECTOR                   (IRQ0_VECTOR + 15)
>
>  /*
> + * First APIC vector available to drivers: (vectors 0x21-0xee).
> + * (0x80 is the syscall vector, 0x30-0x3f are for ISA)
> + */
> +#define FIRST_DEVICE_VECTOR            (FIRST_EXTERNAL_VECTOR + 1)
> +
> +/*
>  * Special IRQ vectors used by the SMP architecture, 0xf0-0xff
>  *
>  *  some of the following vectors are 'rare', they are merged
> @@ -132,14 +124,6 @@
>  */
>  #define MCE_SELF_VECTOR                        0xeb
>
> -/*
> - * First APIC vector available to drivers: (vectors 0x30-0xee).  We
> - * start allocating at 0x31 to spread out vectors evenly between
> - * priority levels. (0x80 is the syscall vector)
> - */
> -#define FIRST_DEVICE_VECTOR            (IRQ15_VECTOR + 1)
> -#define VECTOR_OFFSET_START            1
> -
>  #define NR_VECTORS                      256
>
>  #define FPU_IRQ                                  13
> diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
> index d5bfa29..5c090a1 100644
> --- a/arch/x86/kernel/apic/io_apic.c
> +++ b/arch/x86/kernel/apic/io_apic.c
> @@ -1162,8 +1162,8 @@ __assign_irq_vector(int irq, struct irq_cfg *cfg, const struct cpumask *mask)
>         * Also, we've got to be careful not to trash gate
>         * 0x80, because int 0x80 is hm, kind of importantish. ;)
>         */
> -       static int current_vector = FIRST_DEVICE_VECTOR + VECTOR_OFFSET_START;
> -       static int current_offset = VECTOR_OFFSET_START % 8;
> +       static int current_vector = FIRST_DEVICE_VECTOR;
> +       static int current_offset = 0;
>        unsigned int old_vector;
>        int cpu, err;
>        cpumask_var_t tmp_mask;
>

looks like it returned to first version i suggested?

http://lkml.org/lkml/2010/1/4/26

maybe we can just kill FIRST_DEVICE_VECTOR...

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/