qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Neo Jia <cjia@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "Ruan, Shuai" <shuai.ruan@intel.com>,
	"Song, Jike" <jike.song@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.
Date: Tue, 16 Feb 2016 23:54:48 -0800	[thread overview]
Message-ID: <20160217075448.GC9416@nvidia.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F7B6535@SHSMSX101.ccr.corp.intel.com>

On Wed, Feb 17, 2016 at 07:46:15AM +0000, Tian, Kevin wrote:
> > From: Neo Jia
> > Sent: Wednesday, February 17, 2016 3:26 PM
> > 
> > 
> 
> > 
> > If your most concern is having this kind of path doesn't provide enough
> > information of the virtual device, we can add more sysfs attributes within the
> > directory of /sys/devices/virtual/vgpu/$UUID-$vgpu_idx/ to reflect the
> > information you want.
> 
> Like Gerd said, you can have something like this:
> 
> -device vfio-pci,sysfsdev=/sys/devices/virtual/vgpu/vgpu_idx/UUID

Hi Kevin,

The vgpu_idx is not unique number at all.

For example, how to locate the path of a given VM? Whoever is going to configure
the qemu has to walk through *all* the current vgpu path to locate the UUID to
match the QEMU's VM UUID. This is not required if you have UUID as part of the
device path.

> 
> > 
> > Even with UUID, you don't need libvirt at all. you can get uuid by running
> > uuidgen command, I don't need libvirt to code up and test the RFC that I have
> > sent out early. :-)
> 
> although simple, it still creates unnecessary user space dependency for
> kernel resource management...

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, it just make sure that
virtual gpu device directory can be uniquely addressed.

Thanks,
Neo

> 
> Thanks
> Kevin

  reply	other threads:[~2016-02-17  7:54 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56AFD231.3010404@nvidia.com>
2016-02-02  1:48 ` [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU Kirti Wankhede
2016-02-02  7:42   ` Tian, Kevin
2016-02-02  8:00     ` Gerd Hoffmann
2016-02-02  8:13       ` Neo Jia
2016-02-02  8:18         ` Tian, Kevin
2016-02-02  8:31           ` Neo Jia
2016-02-02 17:11             ` Alex Williamson
2016-02-03  5:41               ` Tian, Kevin
2016-02-03  8:28                 ` Gerd Hoffmann
2016-02-03 19:32                   ` Alex Williamson
2016-02-16  6:49                     ` Tian, Kevin
2016-02-16  7:13                       ` Neo Jia
2016-02-16  7:27                         ` Tian, Kevin
2016-02-16  7:36                           ` Neo Jia
2016-02-16  7:40                             ` Tian, Kevin
2016-02-16  7:53                               ` Neo Jia
2016-02-16  8:10                                 ` Tian, Kevin
2016-02-16  8:48                                   ` Neo Jia
2016-02-17  3:31                                     ` Tian, Kevin
2016-02-17  4:17                                       ` Neo Jia
2016-02-17  5:04                                         ` Tian, Kevin
2016-02-17  5:09                                           ` Eric Blake
2016-02-17  5:40                                             ` Neo Jia
2016-02-17  5:37                                           ` Neo Jia
2016-02-17  6:02                                             ` Tian, Kevin
2016-02-17  7:26                                               ` Neo Jia
2016-02-17  7:46                                                 ` Tian, Kevin
2016-02-17  7:54                                                   ` Neo Jia [this message]
2016-02-17  8:57                                                     ` Tian, Kevin
2016-02-17  9:34                                                       ` Neo Jia
2016-02-17  9:52                                                         ` Tian, Kevin
2016-02-17 10:34                                                           ` Neo Jia
2016-02-17 10:47                                                             ` Tian, Kevin
2016-02-17 13:08                                                     ` Gerd Hoffmann
2016-02-17 15:36                                                       ` Neo Jia
2016-02-17  6:52                                         ` Gerd Hoffmann
2016-02-17  7:32                                           ` Neo Jia
2016-02-17  7:51                                             ` Tian, Kevin
2016-02-17  8:41                                               ` Neo Jia
2016-02-17  9:01                                                 ` Tian, Kevin
2016-02-02  8:29         ` Gerd Hoffmann
2016-02-02  9:25     ` Kirti Wankhede
2016-02-03  5:56       ` Tian, Kevin
2016-02-03 13:21         ` Kirti Wankhede
2016-02-04  3:08           ` Tian, Kevin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160217075448.GC9416@nvidia.com \
    --to=cjia@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=jike.song@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shuai.ruan@intel.com \
    --cc=zhiyuan.lv@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).