From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36907)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1aW1qE-00025T-0E
	for qemu-devel@nongnu.org; Wed, 17 Feb 2016 08:08:26 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1aW1q9-0003cW-0x
	for qemu-devel@nongnu.org; Wed, 17 Feb 2016 08:08:25 -0500
Received: from mx1.redhat.com ([209.132.183.28]:53846)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1aW1q8-0003c4-S5
	for qemu-devel@nongnu.org; Wed, 17 Feb 2016 08:08:20 -0500
Message-ID: <1455714498.9127.28.camel@redhat.com>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Wed, 17 Feb 2016 14:08:18 +0100
In-Reply-To: <20160217075448.GC9416@nvidia.com>
References: <20160216075310.GC6867@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B3709@SHSMSX101.ccr.corp.intel.com>
	<20160216084855.GA7717@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B51AE@SHSMSX101.ccr.corp.intel.com>
	<20160217041743.GA7903@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B565E@SHSMSX101.ccr.corp.intel.com>
	<20160217053742.GA8839@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B5757@SHSMSX101.ccr.corp.intel.com>
	<20160217072610.GA9416@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B6535@SHSMSX101.ccr.corp.intel.com>
	<20160217075448.GC9416@nvidia.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
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: Neo Jia <cjia@nvidia.com>
Cc: "Ruan, Shuai" <shuai.ruan@intel.com>, "Tian, Kevin" <kevin.tian@intel.com>, Alex Williamson <alex.williamson@redhat.com>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>, "Song, Jike" <jike.song@intel.com>, Kirti Wankhede <kwankhede@nvidia.com>, "Lv,
	Zhiyuan" <zhiyuan.lv@intel.com>, Paolo Bonzini <pbonzini@redhat.com>

  Hi,

> For example, how to locate the path of a given VM?

You go ask libvirt, the domain xml will have the info.

> Whoever is going to configure
> the qemu has to walk through *all* the current vgpu path to locate the UU=
ID to
> match the QEMU's VM UUID.

No.  qemu simply uses the path it get passed from libvirt.  libvirt
simply uses whatever is stored in the domain xml.

i.e. you'll have a config like this:

<domain type=3D'kvm'>=20
  <name>rhel7-vfio</name>
  <uuid>0990b05d-4fbd-49bf-88e4-e87974c64fba</uuid>
  [ ... ]
  <devices>
    [ ... ]
    <hostdev mode=3D'subsystem' type=3D'pci' managed=3D'yes'>
      <source>
        <address sysfs=3D'/sys/devices/virtual/vgpu/${name}'/>
      </source>
      <address type=3D'pci' domain=3D'0x0000'
               bus=3D'0x00' slot=3D'0x04' function=3D'0x0'/>
    </hostdev>

> I think I has answered this, UUID is not a user space or kernel space
> concept, it is just a generic way to represent object,

Yes.  But the above sounds like you want to use UUIDs to *link* two
objects, by assigning the same uuid to both vm and vgpu.  This is *not*
how uuids should be used.  Each object should have its own uuid.

You can use uuids to name the vgpus if you want of course.  But the vgpu
uuid will will have no relationship whatsoever to the vm uuid then.

cheers,
  Gerd