On Tue, Jun 20, 2006 at 07:01:52PM -0600, Eric W. Biederman wrote: > So to be very clear what we mean, because I have gotten bitten in the > past. I understand the linux irq number to be: > a) An index in the irq_desc array. > b) An enumeration of the hardware interrupts sources. > c) Human visible so ideally it is neither arbitrary, nor > very dynamic if the hardware is not. > > Then there is the destination cookie (vector on x86) that is > available to the cpu when the interrupt is delivered. > > I think we are on a similar track but I'm not at all certain I like > the idea of a fully dynamic linux irq number except in cases like MSI > where your sources are dynamic. But I may be making the wrong > assumptions about what you are doing. Hi Eric. Unfortunately, I've only received [0/25] so far, depsite both being on the cc list and on linux-pci. I'm getting all the replies though, so I'm hopeful I'll receive the original posts soon. Did you look at the parisc scheme? We have a fixed area for CPU interrupts and then an area for dynamic interrupt assignment. Since devices are typically discovered in the same order between boots, the interrupt number doesn't end up varying between boots. - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
