From: Eric Blake <eblake@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>, 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>,
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 22:09:43 -0700 [thread overview]
Message-ID: <56C40097.3090900@redhat.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F7B565E@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
On 02/16/2016 10:04 PM, Tian, Kevin wrote:
>> From: Neo Jia
[meta-comment]
...
>>>>>>>>>>>> On Wed, 2016-02-03 at 09:28 +0100, Gerd Hoffmann wrote:
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Actually I have a long puzzle in this area. Definitely libvirt will
>> use
>>>> UUID
>>>>>> to
With this much quoting, your mailer is breaking down. It's not only
okay, but encouraged, to trim your message to just what you are directly
replying to...
>> Hi Kevin,
>>
>> 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.
>>
>> vgpu-vendor-0 and vgpu-vendor-1 will not be unique as we can have multiple
>> virtual gpu devices per VM coming from same or different physical devices.
>
> That is not a problem. We can add physical device info too like vgpu-vendor-0-0,
> vgpu-vendor-1-0, ...
...rather than making readers scroll through 16k bytes of repetitions of
the same things they saw earlier in the thread, but getting worse with
each iteration due to excessive quoting.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-02-17 5:09 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 [this message]
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
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=56C40097.3090900@redhat.com \
--to=eblake@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.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).