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

> >- 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision
    • From: [email protected] (Eric W. Biederman)

• References:
  • RE: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision
    • From: "Brown, Len" <[email protected]>

• Prev by Date: who have M-Sytem MDOC G3 driver?
• Next by Date: [Patch 1/8] Setup
• Previous by thread: RE: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision
• Next by thread: Re: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]