From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36535)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1aVvyu-0006YO-6g
	for qemu-devel@nongnu.org; Wed, 17 Feb 2016 01:53:00 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1aVvyr-0001ja-0p
	for qemu-devel@nongnu.org; Wed, 17 Feb 2016 01:53:00 -0500
Received: from mx1.redhat.com ([209.132.183.28]:38195)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1aVvyq-0001jT-Rf
	for qemu-devel@nongnu.org; Wed, 17 Feb 2016 01:52:56 -0500
Message-ID: <1455691973.9127.10.camel@redhat.com>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Wed, 17 Feb 2016 07:52:53 +0100
In-Reply-To: <20160217041743.GA7903@nvidia.com>
References: <1454527963.18969.8.camel@redhat.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B3536@SHSMSX101.ccr.corp.intel.com>
	<20160216071304.GA6867@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B3633@SHSMSX101.ccr.corp.intel.com>
	<20160216073647.GB6867@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B3659@SHSMSX101.ccr.corp.intel.com>
	<20160216075310.GC6867@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B3709@SHSMSX101.ccr.corp.intel.com>
	<20160216084855.GA7717@nvidia.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D15F7B51AE@SHSMSX101.ccr.corp.intel.com>
	<20160217041743.GA7903@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>, "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>

  Hi,

> The answer is simple, having a UUID as part of the device name will give =
you a
> unique sysfs path that will be opened by QEMU.

A descriptive name will work too, and I think it'll be easier to make
those names persistent because you don't have to store the uuids
somewhere to re-create the same setup afer reboot.

> If you are worried about losing meaningful name here, we can create a sys=
fs file
> to capture the vendor device description if you like.

You can also store the uuid in a sysfs file ...

cheers,
  Gerd