On Fri, 2015-07-10 at 14:47 +0200, Paolo Bonzini wrote: > > On 10/07/2015 10:28, Wu, Feng wrote: > > > Yes, you are right. All we need is the producer information which has been > > > passed in the register routine. And we can easily make this update logic > > > inside the consumer. Thanks for your comments! > > > > BTW, Paolo & Alex, in VFIO framework, how can we know a vCPU or a guest > > has assigned devices to it? > > See here: > http://article.gmane.org/gmane.comp.emulators.kvm.devel/137930/raw In general, VFIO has zero visibility into KVM. VFIO doesn't know or care what the userspace driver is, whether it's QEMU/KVM, a set of ruby bindings for VFIO, a DPDK library, etc. As Paolo points out, KVM does have ways to be told about assigned devices from userspace and probe some properties, like whether the IOMMU allows non-coherent DMA. These are handled by the KVM-VFIO pseudo device (virt/kvm/vfio.c). Thanks, Alex -- 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
