From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50314)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cjia@nvidia.com>) id 1aQW5T-0004zC-Am
	for qemu-devel@nongnu.org; Tue, 02 Feb 2016 03:13:24 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <cjia@nvidia.com>) id 1aQW5P-0005Vc-6J
	for qemu-devel@nongnu.org; Tue, 02 Feb 2016 03:13:23 -0500
Received: from hqemgate16.nvidia.com ([216.228.121.65]:3124)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cjia@nvidia.com>) id 1aQW5O-0005UJ-Vs
	for qemu-devel@nongnu.org; Tue, 02 Feb 2016 03:13:19 -0500
Date: Tue, 2 Feb 2016 00:13:12 -0800
From: Neo Jia <cjia@nvidia.com>
Message-ID: <20160202081312.GA9895@nvidia.com>
References: <56AFD231.3010404@nvidia.com> <56B00AD7.6070103@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7940CB@SHSMSX101.ccr.corp.intel.com>
	<1454400043.9300.31.camel@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1454400043.9300.31.camel@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide
 common interface for vGPU.
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Ruan, Shuai" <shuai.ruan@intel.com>, "Song,
	Jike" <jike.song@intel.com>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "Tian, Kevin" <kevin.tian@intel.com>, Kirti Wankhede <kwankhede@nvidia.com>, qemu-devel <qemu-devel@nongnu.org>, Alex Williamson <alex.williamson@redhat.com>, "Lv,
	Zhiyuan" <zhiyuan.lv@intel.com>, Paolo Bonzini <pbonzini@redhat.com>

On Tue, Feb 02, 2016 at 09:00:43AM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > And for UUID, I remember Alex had a concern on using it in kernel. 
> > Honestly speaking I don't have a good idea here. In Xen side there is a VM ID
> > which can be easily used as the index. But for KVM, what would be the best
> > identifier to associate with a VM?
> 
> The vgpu code doesn't need to associate the vgpu device with a vm in the
> first place.  You get all guest address space information from qemu, via
> vfio iommu interface.
> 
> When qemu does't use kvm (tcg mode), things should still work fine.
> Using vfio-based vgpu devices with non-qemu apps (some kind of test
> suite for example) should work fine too.

Hi Gerd and Kevin,

I thought Alex had agreed with the UUID as long as it is not tied with VM,
probably it is just his comment gets lost in our previous long email thread.

Thanks,
Neo

> 
> cheers,
>   Gerd
>