From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [RFC PATCH v1 1/1] vGPU core driver : to provide common
 interface for vGPU.
Date: Wed, 17 Feb 2016 07:52:53 +0100
Message-ID: <1455691973.9127.10.camel@redhat.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Ruan, Shuai" <shuai.ruan@intel.com>,
	"Song, Jike" <jike.song@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
To: Neo Jia <cjia@nvidia.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:58106 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756532AbcBQGwz convert rfc822-to-8bit (ORCPT
	<rfc822;kvm@vger.kernel.org>); Wed, 17 Feb 2016 01:52:55 -0500
In-Reply-To: <20160217041743.GA7903@nvidia.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

  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 sysfs file
> to capture the vendor device description if you like.

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

cheers,
  Gerd