Re: [RFC] killing the NR_IRQS arrays.

> I expect the most it makes sense to aim for 2.6.22 are the genirq
> changes so the internal arch code is passing struct irq_desc
> everywhere internally. 

Are there any livetime issues with passing pointers around? 
e.g. what happens on APIC hotunplug etc.? We don't necessarily
support that yet, but for a big interface change it should 
be probably kept in mind first.

-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: [RFC] killing the NR_IRQS arrays.
    • From: [email protected] (Eric W. Biederman)

• References:
  • [RFC] killing the NR_IRQS arrays.
    • From: [email protected] (Eric W. Biederman)

• Prev by Date: [RFC] killing the NR_IRQS arrays.
• Next by Date: RE: [PATCH] aio: fix kernel bug when page is temporally busy
• Previous by thread: [RFC] killing the NR_IRQS arrays.
• Next by thread: Re: [RFC] killing the NR_IRQS arrays.
• 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]