On Fri, May 6, 2011 at 10:36 AM, Sasha Levin <[email protected]> wrote: > afaik, we need to have same IRQ pins for devices which may have > different IRQ lines (All virtio-blk share same IRQ pin but different > line, I assume it'll be same with different virtio devices). > > So mptable has to manage association between device type and the > corresponding IRQ pin/line assignment, So dynamic assignment will be > more of a call with device type and return IRQ pin + line - which makes > it more complex than just allocating next free IRQ line.
Well then make kvm__request_irq() return a pointer to struct irq and have a hard-coded array of IRQ pin + line pairs in irq.c, for example. That'll reduce complexity in the virtio drivers and it'll serve as a starting point for proper IRQ allocator. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
