From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: [Intel-gfx] [Announcement] 2015-Q3 release of XenGT - a Mediated Graphics Passthrough Solution from Intel Date: Thu, 19 Nov 2015 08:52:46 -0700 Message-ID: <1447948366.4697.119.camel__15983.9293025017$1447948442$gmane$org@redhat.com> References: <53D215D3.50608@intel.com> <547FCAAD.2060406@intel.com> <54AF967B.3060503@intel.com> <5527CEC4.9080700@intel.com> <559B3E38.1080707@intel.com> <562F4311.9@intel.com> <1447870341.4697.92.camel@redhat.com> <564D78D0.80904@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: "igvt-g@ml01.01.org" , Jike Song , "Reddy, Raghuveer" , qemu-devel , "White, Michael L" , "Cowperthwaite, David J" , "intel-gfx@lists.freedesktop.org" , "Li, Susie" , "Dong, Eddie" , "Tian, Kevin" , "linux-kernel@vger.kernel.org" , Gerd Hoffmann , "Zhou, Chao" , Paolo Bonzini , "Zhu, Libo" , "xen-devel@lists.xen.org" , "Wang, Hongbo" , "Lv, Zhiyuan" List-Id: xen-devel@lists.xenproject.org On Thu, 2015-11-19 at 15:32 +0000, Stefano Stabellini wrote: > On Thu, 19 Nov 2015, Jike Song wrote: > > Hi Alex, thanks for the discussion. > > > > In addition to Kevin's replies, I have a high-level question: can VFIO > > be used by QEMU for both KVM and Xen? > > No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU > is owned by Xen. Right, but in this case we're talking about device MMUs, which are owned by the device driver which I think is running in dom0, right? This proposal doesn't require support of the system IOMMU, the dom0 driver maps IOVA translations just as it would for itself. We're largely proposing use of the VFIO API to provide a common interface to expose a PCI(e) device to QEMU, but what happens in the vGPU vendor device and IOMMU backends is specific to the device and perhaps even specific to the hypervisor. Thanks, Alex