From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: summary of current vfio mdev upstreaming status Date: Thu, 29 Sep 2016 12:16:31 +0100 Message-ID: <20160929111631.GO5312@redhat.com> References: <57ECD70B.1080205@intel.com> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Alex Williamson , Neo Jia , Kirti Wankhede , Paolo Bonzini , "kvm@vger.kernel.org" , qemu-devel , "libvir-list@redhat.com" , "bjsdjshi@linux.vnet.ibm.com" , "Tian, Kevin" , "Xiao, Guangrong" To: Jike Song Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53044 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750700AbcI2LQk (ORCPT ); Thu, 29 Sep 2016 07:16:40 -0400 Content-Disposition: inline In-Reply-To: <57ECD70B.1080205@intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Sep 29, 2016 at 04:55:39PM +0800, 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. > > > > PART 1: mdev core driver > > [task] > - the mdev bus/device support > - the utilities of mdev lifecycle management > - the physical device register/unregister interfaces > > [status] > - basically agreed by community > > > PART 2: vfio bus driver for mdev > > [task] > - interfaces with vendor drivers > - the vfio bus implementation > > [status] > > - basically agreed by community > > > PART 3: iommu support for mdev > > [task] > - iommu support for mdev > > [status] > - Kirti's v7 implementation, not yet fully reviewed > > > PART 4: sysfs interfaces for mdev > > [task] > - define the hierarchy of minimal sysfs directories/files > - check the validity from vendor drivers, init/de-init them > [status] > - interfaces are in discussion > > > PART 6: Documentation > > [task] > - clearly document the architecture and interfaces > - coding example for vendor drivers > > [status] > - N/A > IMHO documentation should really be near the front as that's spelling out the design. The implementation patches are then reviewed in reference to the design documentation. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :| From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34124) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpZKW-0007lr-JN for qemu-devel@nongnu.org; Thu, 29 Sep 2016 07:16:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpZKR-00018s-O7 for qemu-devel@nongnu.org; Thu, 29 Sep 2016 07:16:43 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpZKR-00018o-HH for qemu-devel@nongnu.org; Thu, 29 Sep 2016 07:16:39 -0400 Date: Thu, 29 Sep 2016 12:16:31 +0100 From: "Daniel P. Berrange" Message-ID: <20160929111631.GO5312@redhat.com> Reply-To: "Daniel P. Berrange" References: <57ECD70B.1080205@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <57ECD70B.1080205@intel.com> Subject: Re: [Qemu-devel] summary of current vfio mdev upstreaming status List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jike Song Cc: Alex Williamson , Neo Jia , Kirti Wankhede , Paolo Bonzini , "kvm@vger.kernel.org" , qemu-devel , "libvir-list@redhat.com" , "bjsdjshi@linux.vnet.ibm.com" , "Tian, Kevin" , "Xiao, Guangrong" On Thu, Sep 29, 2016 at 04:55:39PM +0800, 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. > > > > PART 1: mdev core driver > > [task] > - the mdev bus/device support > - the utilities of mdev lifecycle management > - the physical device register/unregister interfaces > > [status] > - basically agreed by community > > > PART 2: vfio bus driver for mdev > > [task] > - interfaces with vendor drivers > - the vfio bus implementation > > [status] > > - basically agreed by community > > > PART 3: iommu support for mdev > > [task] > - iommu support for mdev > > [status] > - Kirti's v7 implementation, not yet fully reviewed > > > PART 4: sysfs interfaces for mdev > > [task] > - define the hierarchy of minimal sysfs directories/files > - check the validity from vendor drivers, init/de-init them > [status] > - interfaces are in discussion > > > PART 6: Documentation > > [task] > - clearly document the architecture and interfaces > - coding example for vendor drivers > > [status] > - N/A > IMHO documentation should really be near the front as that's spelling out the design. The implementation patches are then reviewed in reference to the design documentation. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|