From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51963) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzbjV-0001dH-Jy for qemu-devel@nongnu.org; Thu, 19 Nov 2015 21:47:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzbjS-0007G2-Dc for qemu-devel@nongnu.org; Thu, 19 Nov 2015 21:47:29 -0500 Received: from mga01.intel.com ([192.55.52.88]:63768) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzbjS-0007Fo-7t for qemu-devel@nongnu.org; Thu, 19 Nov 2015 21:47:26 -0500 Message-ID: <564E899E.4090904@intel.com> Date: Fri, 20 Nov 2015 10:46:54 +0800 From: Jike Song MIME-Version: 1.0 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> <1447922452.25140.39.camel@redhat.com> <564DADCC.2030702@redhat.com> In-Reply-To: <564DADCC.2030702@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Intel-gfx] [Announcement] 2015-Q3 release of XenGT - a Mediated Graphics Passthrough Solution from Intel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: "igvt-g@ml01.01.org" , "Tian, Kevin" , "Reddy, Raghuveer" , qemu-devel , "Lv, Zhiyuan" , "White, Michael L" , "Cowperthwaite, David J" , "intel-gfx@lists.freedesktop.org" , "Li, Susie" , "Dong, Eddie" , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xen.org" , Alex Williamson , Gerd Hoffmann , "Zhu, Libo" , "Wang, Hongbo" , "Zhou, Chao" On 11/19/2015 07:09 PM, Paolo Bonzini wrote: > On 19/11/2015 09:40, Gerd Hoffmann wrote: >>>> But this code should be >>>> minor to be maintained in libvirt. >> As far I know libvirt only needs to discover those devices. If they >> look like sr/iov devices in sysfs this might work without any changes to >> libvirt. > > I don't think they will look like SR/IOV devices. > > The interface may look a little like the sysfs interface that GVT-g is > already using. However, it should at least be extended to support > multiple vGPUs in a single VM. This might not be possible for Intel > integrated graphics, but it should definitely be possible for discrete > graphics cards. Didn't hear about multiple vGPUs for a single VM before. Yes If we expect same vGPU interfaces for different vendors, abstraction and vendor specific stuff should be implemented. > Another nit is that the VM id should probably be replaced by a UUID > (because it's too easy to stumble on an existing VM id), assuming a VM > id is needed at all. For the last assumption, yes, a VM id is not necessary for gvt-g, it's only a temporary implementation. As long as libvirt is used, UUID should be enough for gvt-g. However, UUID is not mandatory? What should we do if user don't specify an UUID in QEMU cmdline? > > Paolo > -- Thanks, Jike