Re: [PATCH 1/2] kvm tools: Fix IRQ assignments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 6, 2011 at 10:47 AM, Cyrill Gorcunov <gorcunov@xxxxxxxxx> wrote:
>  Nod, making it dynamic force us to implement some kind of collector for
> pci devices, so that it would know pin/vector pair for every device. So
> in device init time we need to call kinda mptable_request_irq_pin()
> where we could "hint" allocator which pin and irq we need, and say "exclusive"
> flag which would tell allocator to fail if irq/pin already borrowed.
>
>  The "hints" for every device might left hardcoded in some enum, for other
> irqs we might need pure dynamic vector allocator.

That's a separate problem, I think. What I'm proposing is moving the
complexity from the drivers to a centralized irq.c. We can still have
hard-coded pin/line pairs but we'd let drivers take advantage of them
in a more dynamic way.

                        Pekka
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux