On Fri, May 13, 2016 at 07:13:44AM +0000, Tian, Kevin wrote: > > From: Neo Jia [mailto:cjia@xxxxxxxxxx] > > Sent: Friday, May 13, 2016 2:42 PM > > > > > > > > > > We possibly have the same requirement from the mediate driver backend: > > > > > > a) get a GFN, when guest try to tell hardware; > > > b) consult the vfio iommu with that GFN[1]: will you find me a proper dma_addr? > > > > We will provide you the pfn via vfio_pin_pages, so you can map it for dma > > purpose in your i915 driver, which is what we are doing today. > > > > Can such 'map' operation be consolidated in vGPU core driver? I don't think > Intel vGPU driver has any feature proactively relying on iommu. The reason > why we keep talking iommu is just because the kernel may enable iommu > for physical GPU so we need make sure our device model can work in such > configuration. And this requirement should apply to all vendors, not Intel > specific (like you said you are doing it already today). Hi Kevin, Actually, such requirement is already satisfied today as all vendor drivers should transparently work with and without system iommu on bare-metal, right? So I don't see any new requirement here, also such consolidation doesn't help any but adding complexity to the system as vendor driver will not remove their own dma_map_xxx functions as they are still required to support non-mediated cases. Thanks, Neo > > Thanks > Kevin -- 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
