Re: VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

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

 



On 2016/1/27 8:06, Jike Song wrote:
On 01/26/2016 10:05 PM, Yang Zhang wrote:
On 2016/1/26 15:41, Jike Song wrote:

We will need to extend:

	- VFIO_DEVICE_GET_REGION_INFO


a) adding a flag: DONT_MAP. For example, the MMIO of vgpu
should be trapped instead of being mmap-ed.

I may not in the context, but i am curious how to handle the DONT_MAP in
vfio driver? Since there are no real MMIO maps into the region and i
suppose the access to the region should be handled by vgpu in i915
driver, but currently most of the mmio accesses are handled by Qemu.


Hi Yang,

MMIO accesses are supposed to be handled in kernel, without vm-exiting
to QEMU, similar to in-kernel irqchip :)

The question is current vfio doesn't support it. The long discussion between Alex and Kevin is what i am to understand how KVMGT works under vfio framework.


--
best regards
yang
--
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