Re: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision

[Andi Kleen]

> >- Modify do_IRQ to get passed an interrupt vector# from the
> >  interrupt vector instead of an irq number, and then lookup
> >  the irq number in vector_irq.  This means we don't need
> >  a code stub per irq, and allows us to handle more irqs
> >  by simply increasing NR_IRQS.
> 
> isn't the vector number already on the stack from
> ENTRY(interrupt)
> 	pushl $vector-256

Yes - and interrupts/vectors are currently always identical. If we go
to per CPU IDTs I suspect the stubs will just need to be generated
at runtime and start passing interrupts.

-Andi
-
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/