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>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Kirti Wankhede <kwankhede@nvidia.com>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [Qemu-devel] [RFC PATCH v2 1/3] vGPU Core driver
Date: Mon, 29 Feb 2016 15:17:58 -0800 [thread overview]
Message-ID: <20160229231757.GA19330@nvidia.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F7D448A@SHSMSX101.ccr.corp.intel.com>
On Mon, Feb 29, 2016 at 05:39:02AM +0000, Tian, Kevin wrote:
> > From: Kirti Wankhede
> > Sent: Wednesday, February 24, 2016 12:24 AM
> >
> > Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
> > Signed-off-by: Neo Jia <cjia@nvidia.com>
>
> Hi, Kirti/Neo,
>
> Thanks a lot for you updated version. Having not looked into detail
> code, first come with some high level comments.
>
> First, in a glimpse the majority of the code (possibly >95%) is device
> agnostic, though we call it vgpu today. Just thinking about the
> extensibility and usability of this framework, would it be better to
> name it in a way that any other type of I/O device can be fit into
> this framework? I don't have a good idea of the name now, but
> a simple idea is to replace vgpu with vdev (vdev-core, vfio-vdev,
> vfio-iommu-type1-vdev, etc.), and then underlying GPU drivers are
> just one category of users of this general vdev framework. In the
> future it's easily extended to support other I/O virtualization based
> on similar vgpu concept;
>
> Second, are these 3 patches already working with nvidia device,
> or are they just conceptual implementation w/o completing actual
> test yet? We'll start moving our implementation toward this direction
> too, so would be good to know the current status and how we can
> further cooperate to move forward. Based on that we can start
> giving more comments on next level detail.
>
Hi Kevin,
Yes, we do have an engineering prototype up and running with this set of kernel
patches we have posted.
Please let us know if you have any questions while integrating your vgpu solution
within this framework.
Thanks,
Neo
> Thanks
> Kevin
next prev parent reply other threads:[~2016-02-29 23:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:24 [Qemu-devel] [RFC PATCH v2 1/3] vGPU Core driver Kirti Wankhede
2016-02-23 16:24 ` [Qemu-devel] [RFC PATCH v2 2/3] VFIO driver for vGPU device Kirti Wankhede
2016-02-23 16:24 ` [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU Kirti Wankhede
2016-03-02 8:38 ` Jike Song
2016-03-04 7:00 ` Neo Jia
2016-03-07 6:07 ` Jike Song
2016-03-08 0:31 ` Neo Jia
2016-03-10 3:10 ` Jike Song
2016-03-11 4:19 ` Neo Jia
2016-03-11 4:46 ` Tian, Kevin
2016-03-11 6:10 ` Neo Jia
2016-03-11 8:06 ` Tian, Kevin
2016-03-11 16:13 ` Alex Williamson
2016-03-11 16:55 ` Neo Jia
2016-03-11 17:56 ` Alex Williamson
2016-03-11 18:18 ` Neo Jia
2016-02-29 5:39 ` [Qemu-devel] [RFC PATCH v2 1/3] vGPU Core driver Tian, Kevin
2016-02-29 23:17 ` Neo Jia [this message]
2016-03-01 3:10 ` Jike Song
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=20160229231757.GA19330@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).