Re: [PATCH RFC] kvm: enable irq injection from interrupt context

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

 



 On 09/16/2010 03:38 PM, Michael S. Tsirkin wrote:
>
>  That's just an implementation detail.  Devices either assert INT# or
>  they do not.  Tying the wires together constitutes an AND gate.
>  This gate has to be modelled somewhere, currently it's in qemu's pci
>  emulation.

Right. kvm in kernel has this as well, we need to keep this in
kvm kernel if we want to support level with irqfd.

Right, we added the irq_source_id hack for device assignment.

What's wrong with letting userspace mediate this, though?

Where it does not belong is individual devices: these
should be able to assert INTx multiple times
and it should have no effect, as per spec.



Yes.

--
error compiling committee.c: too many arguments to function

--
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