From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [Qemu-devel] summary of current vfio mdev upstreaming status Date: Thu, 29 Sep 2016 17:46:03 +0800 Message-ID: <375548cd-a7fb-94d3-023f-428b053039fc@linux.intel.com> References: <57ECD70B.1080205@intel.com> <20160929093631.GC32640@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Jike Song , Alex Williamson , Kirti Wankhede , "Tian, Kevin" , "Xiao, Guangrong" , "kvm@vger.kernel.org" , "libvir-list@redhat.com" , qemu-devel , Paolo Bonzini , "bjsdjshi@linux.vnet.ibm.com" To: Neo Jia Return-path: Received: from mga04.intel.com ([192.55.52.120]:58824 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751220AbcI2JwV (ORCPT ); Thu, 29 Sep 2016 05:52:21 -0400 In-Reply-To: <20160929093631.GC32640@nvidia.com> Sender: kvm-owner@vger.kernel.org List-ID: On 09/29/2016 05:36 PM, Neo Jia wrote: > 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. We understand the progress goes okay. However, splitting such big patchset into small parts is a better way to push large code to upstream - it is better for review and validation and we can quickly iterate the code if there are new issues exposed during the review of new version. Particularly, based on the current situation that the sysfs interfaces are far from the way to be decided, it is definitely a good idea to push the basic infrastructure first, later let's focal on the ABI part - sysfs interface design. Thanks!