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

2016-02-04 Thread Tian, Kevin
> From: Song, Jike > Sent: Thursday, February 04, 2016 11:05 PM > > On 02/04/2016 12:16 PM, Tian, Kevin wrote: > > 5) Pin/unpin guest memory > > -- > > IGD or any PCI passthru should have same requirement. So we should be > > able to leverage existing code in VFIO. The only tricky

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

2016-02-04 Thread Jike Song
On 02/04/2016 12:16 PM, Tian, Kevin wrote: > 5) Pin/unpin guest memory > -- > IGD or any PCI passthru should have same requirement. So we should be > able to leverage existing code in VFIO. The only tricky thing (Jike may > elaborate after he is back), is that KVMGT requires to

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

2016-02-03 Thread Tian, Kevin
> From: Neo Jia [mailto:c...@nvidia.com] > Sent: Thursday, February 04, 2016 11:52 AM > > > > > 4) Map/unmap guest memory > > > > -- > > > > It's there for KVM. > > > > > > Map and unmap for who?  For the vGPU or for the VM?  It seems like we > > > know how to map guest memory for the vGPU without

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

2016-02-03 Thread Neo Jia
On Thu, Feb 04, 2016 at 03:01:36AM +, Tian, Kevin wrote: > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > Sent: Thursday, February 04, 2016 4:45 AM > > > > > > First, Jike told me before his vacation, that we cannot do any change to > > > KVM module according to community comme