From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmDvb-0007bB-5B for qemu-devel@nongnu.org; Tue, 20 Sep 2016 01:49:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bmDvV-0001Eq-3q for qemu-devel@nongnu.org; Tue, 20 Sep 2016 01:49:10 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:41437 helo=mx0a-001b2d01.pphosted.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmDvU-0001Ct-Vj for qemu-devel@nongnu.org; Tue, 20 Sep 2016 01:49:05 -0400 Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u8K5lwKN131449 for ; Tue, 20 Sep 2016 01:49:02 -0400 Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by mx0b-001b2d01.pphosted.com with ESMTP id 25jmqyycgf-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 20 Sep 2016 01:49:02 -0400 Received: from localhost by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 19 Sep 2016 23:49:01 -0600 Date: Tue, 20 Sep 2016 13:48:51 +0800 From: Dong Jia Shi References: <1472097235-6332-1-git-send-email-kwankhede@nvidia.com> <1472097235-6332-3-git-send-email-kwankhede@nvidia.com> <20160825172226.2cd06d71@oc7835276234> <57D0D0C2.6040201@intel.com> <57D765DF.7050801@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57D765DF.7050801@intel.com> Message-Id: <20160920054851.GA2186@bjsdjshi@linux.vnet.ibm.com> Subject: Re: [Qemu-devel] [PATCH v7 2/4] vfio: VFIO driver for mediated devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jike Song Cc: Dong Jia , Kirti Wankhede , alex.williamson@redhat.com, pbonzini@redhat.com, kraxel@redhat.com, cjia@nvidia.com, qemu-devel@nongnu.org, kvm@vger.kernel.org, kevin.tian@intel.com * Jike Song [2016-09-13 10:35:11 +0800]: > On 09/08/2016 10:45 AM, Jike Song wrote: > > On 08/25/2016 05:22 PM, Dong Jia wrote: > >> On Thu, 25 Aug 2016 09:23:53 +0530 > >> Kirti Wankhede wrote: > >> > >> [...] > >> > >> Dear Kirti, > >> > >> I just rebased my vfio-ccw patches to this series. > >> With a little fix, which was pointed it out in my reply to the #3 > >> patch, it works fine. > >> > > > > Hi Jia, > > > > Sorry I didn't follow a lot in previous discussion, but since > > vfio-mdev in v7 patchset is at least PCI-agnostic, would you share > > with us why you still need a vfio-ccw? > > Kind ping :) > > > Hi Dong Jia, > > Since Kirti has confirmed that in v7 it is designed to have only one > vfio-mdev driver for all mdev devices, would you please tell us the > reason of your vfio-ccw? It could possibly be an architectural gap and > the earlier we discuss it the better :) Hi Jike, Sorry for the late response. I think you may mix up vfio-ccw with vfio-mccw, which is in the same level with vfio-mpci in v6 (or vfio-mdev in v7). :> The term of vfio-ccw is in the same semantic level with vfio-pci. You can understand vfio-ccw as the parent device driver in the ccw case. As you mentioned above, v7 provides an universal mdev driver (vfio-mdev) for the mediated devices. So I don't need to provide a vfio-mccw (a vendor specific mediated device driver) anymore, but I'd still need my vfio-ccw (the parent device driver). > > -- > Thanks, > Jike > ...snip... -- Dong Jia