From: Neo Jia <cjia@nvidia.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: Jike Song <jike.song@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Xiao, Guangrong" <guangrong.xiao@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"libvir-list@redhat.com" <libvir-list@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"bjsdjshi@linux.vnet.ibm.com" <bjsdjshi@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] summary of current vfio mdev upstreaming status
Date: Thu, 29 Sep 2016 02:36:31 -0700 [thread overview]
Message-ID: <20160929093631.GC32640@nvidia.com> (raw)
In-Reply-To: <ca6ab182-6292-1f71-c421-48963865b837@linux.intel.com>
On Thu, Sep 29, 2016 at 05:05:47PM +0800, Xiao Guangrong wrote:
>
>
> On 09/29/2016 04:55 PM, Jike Song wrote:
> > Hi all,
> >
> > In order to have a clear understanding about the VFIO mdev upstreaming
> > status, I'd like to summarize it. Please share your opinions on this,
> > and correct my misunderstandings.
> >
> > The whole vfio mdev series can be logically divided into several parts,
> > they work together to provide the mdev support.
>
> I think what Jike want to suggest is how about partially push/develop the
> mdev. As jike listed, there are some parts can be independent and they have
> mostly been agreed.
>
> Such development plan can make the discussion be much efficient in the
> community. Also it make the possibility that Intel, Nvdia, IBM can focus
> on different parts and co-develop it.
Hi Guangrong,
JFYI. we are preparing v8 patches to accommodate most comments we have discussed
so far and we will also include several things that we have decided on sysfs.
I definitely would like to see more interactive discussions especially on the
sysfs class front from intel folks.
Regarding the patch development and given the current status, especially where
we are and what we have been through, I am very confident that we should be able
to fully handle this ourselves, but thanks for offering help anyway!
We should be able to react as fast as possible based on the public mailing list
discussions, so again I don't think that part is an issue.
Thanks,
Neo
>
> The maintainer can hold these development patches in local branch before
> pushing the full-functionality version to upstream.
>
> Thanks!
>
>
next prev parent reply other threads:[~2016-09-29 9:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 8:55 summary of current vfio mdev upstreaming status Jike Song
2016-09-29 8:55 ` [Qemu-devel] " Jike Song
2016-09-29 9:05 ` Xiao Guangrong
2016-09-29 9:36 ` Neo Jia [this message]
2016-09-29 9:46 ` Xiao Guangrong
2016-09-29 11:06 ` Kirti Wankhede
2016-09-29 9:17 ` Neo Jia
2016-09-29 9:17 ` [Qemu-devel] " Neo Jia
2016-09-29 10:58 ` Kirti Wankhede
2016-09-29 10:58 ` [Qemu-devel] " Kirti Wankhede
2016-09-30 2:30 ` Jike Song
2016-09-30 2:30 ` [Qemu-devel] " Jike Song
2016-09-29 14:43 ` Tian, Kevin
2016-09-29 14:43 ` [Qemu-devel] " Tian, Kevin
2016-09-29 11:16 ` Daniel P. Berrange
2016-09-29 11:16 ` [Qemu-devel] " Daniel P. Berrange
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=20160929093631.GC32640@nvidia.com \
--to=cjia@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=guangrong.xiao@intel.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=jike.song@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.