Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161950AbbKTC64 (ORCPT ); Thu, 19 Nov 2015 21:58:56 -0500 Received: from mga14.intel.com ([192.55.52.115]:2650 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161936AbbKTC6y (ORCPT ); Thu, 19 Nov 2015 21:58:54 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,320,1444719600"; d="scan'208";a="855402971" Message-ID: <564E8C51.6070706@intel.com> Date: Fri, 20 Nov 2015 10:58:25 +0800 From: Jike Song User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Alex Williamson CC: Stefano Stabellini , "Tian, Kevin" , "xen-devel@lists.xen.org" , "igvt-g@ml01.01.org" , "intel-gfx@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "White, Michael L" , "Dong, Eddie" , "Li, Susie" , "Cowperthwaite, David J" , "Reddy, Raghuveer" , "Zhu, Libo" , "Zhou, Chao" , "Wang, Hongbo" , "Lv, Zhiyuan" , qemu-devel , Paolo Bonzini , Gerd Hoffmann Subject: Re: [Intel-gfx] [Announcement] 2015-Q3 release of XenGT - a Mediated Graphics Passthrough Solution from Intel 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> <1447948366.4697.119.camel@redhat.com> In-Reply-To: <1447948366.4697.119.camel@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1434 Lines: 37 On 11/19/2015 11:52 PM, Alex Williamson wrote: > 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, Let me conclude this, and please correct me in case of any misread: the vGPU interface between kernel and QEMU will be through VFIO, with a new VFIO backend (instead of the existing type1), for both KVMGT and XenGT? > > Alex > -- Thanks, Jike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/