On Thu, 7 Aug 2003, long wrote:
> - Change the interface name from msi_free_vectors to msix_free_vectors since
> this interface is used for MSI-X device drivers, which request for releasing
> the number of vector back to the PCI subsystem.
> - Change the function name from remove_hotplug_vectors to
> msi_remove_pci_irq_vectors to have a close match with function name
> msi_get_pci_irq_vector.
I think the vector allocator code can all be arch specific generic,
there is no particular reason as to why it has to be MSI specific.
> diff -X excludes -urN linux-2.6.0-test2/arch/i386/kernel/io_apic.c linux-2.6.0-test2-create-vectorbase/arch/i386/kernel/io_apic.c
> --- linux-2.6.0-test2/arch/i386/kernel/io_apic.c 2003-07-27 13:00:21.000000000 -0400
> +++ linux-2.6.0-test2-create-vectorbase/arch/i386/kernel/io_apic.c 2003-08-05 09:25:54.000000000 -0400
> @@ -76,6 +76,20 @@
> int apic, pin, next;
> } irq_2_pin[PIN_MAP_SIZE];
>
> +#ifdef CONFIG_PCI_USE_VECTOR
> +int vector_irq[NR_IRQS] = { [0 ... NR_IRQS -1] = -1};
> +
> +static int platform_irq(int irq)
> +{
> + if (platform_legacy_irq(irq))
> + return irq;
> + else
> + return vector_irq[irq];
> +}
> +#else
> +#define platform_irq(irq) (irq)
> +#endif
I wish you wouldn't mix up vector and irq like this :( This is really
beginning to look like IPF. When is an irq an irq and when is a vector a
vector? This can get very confusing very quickly. I spent a fair
amount of time debugging this last time due to the confusion in the
common_interrupt -> do_IRQ path, i'd hate for this to be a permanent
fixture. If you're going to change things just change everything
(including variable names) instead of making it conditional.
> diff -X excludes -urN linux-2.6.0-test2-create-vectorbase/arch/i386/kernel/io_apic.c linux-2.6.0-test2-create-msi/arch/i386/kernel/io_apic.c
> --- linux-2.6.0-test2-create-vectorbase/arch/i386/kernel/io_apic.c 2003-08-05 09:25:54.000000000 -0400
> +++ linux-2.6.0-test2-create-msi/arch/i386/kernel/io_apic.c 2003-08-05 09:45:25.000000000 -0400
> @@ -427,6 +427,11 @@
> /* Is this an active IRQ? */
> if (!irq_desc[j].action)
> continue;
> +#ifdef CONFIG_PCI_MSI
> + /* Is this an active MSI? */
> + if (msi_desc[j])
> + continue;
> +#endif
Is there any locking for msi_desc? Or are you relying on something else?
> +static int nr_alloc_vectors = 0;
> +static int nr_released_vectors = 0;
No need to initialise to 0 it'll be done for you when .bss gets zeroed.
> + if (current_vector == FIRST_SYSTEM_VECTOR)
> + panic("ran out of interrupt sources!");
Please just fail and return -ENOSPC or something like that.
Besides my whining thanks for cranking this out.
Zwane
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:41 EST