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 01/20/2016 05:05 PM, Tian, Kevin wrote:
> I would expect we can spell out next level tasks toward above
> direction, upon which Alex can easily judge whether there are
> some common VFIO framework changes that he can help :-)

Hi Alex,

Here is a draft task list after a short discussion w/ Kevin,
would you please have a look?

	Bus Driver

		{ in i915/vgt/xxx.c }

		- define a subset of vfio_pci interfaces
		- selective pass-through (say aperture)
		- trap MMIO: interface w/ QEMU

	IOMMU

		{ in a new vfio_xxx.c }

		- allocate: struct device & IOMMU group
		- map/unmap functions for vgpu
		- rb-tree to maintain iova/hpa mappings
		- interacts with kvmgt.c


	vgpu instance management

		{ in i915 }

		- path, create/destroy


--
Thanks,
Jike

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