Re: [KVM PATCH v4 3/3] kvm: add iosignalfd support

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

 



Hi Greg,

On Wed, 2009-06-03 at 18:04 -0400, Gregory Haskins wrote:
> Hi Mark,
>   So with the v5 release of iosignalfd, we now have the notion of a
> "trigger", the API of which is as follows:
> 
> -----------------------
> /*!
>  * \brief Assign an eventfd to an IO port (PIO or MMIO)
>  *
>  * Assigns an eventfd based file-descriptor to a specific PIO or MMIO
>  * address range.  Any guest writes to the specified range will generate
>  * an eventfd signal.
>  *
>  * A data-match pointer can be optionally provided in "trigger" and only
>  * writes which match this value exactly will generate an event.  The length
>  * of the trigger is established by the length of the overall IO range, and
>  * therefore must be in a natural byte-width for the IO routines of your
>  * particular architecture (e.g. 1, 2, 4, or 8 bytes on x86_64).

This looks like it'll work fine for virtio-pci.

Thanks,
Mark.

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