From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60601) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmEi5-0005e8-Mx for qemu-devel@nongnu.org; Tue, 20 Sep 2016 02:39:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bmEi1-0000pJ-KG for qemu-devel@nongnu.org; Tue, 20 Sep 2016 02:39:16 -0400 Received: from mga14.intel.com ([192.55.52.115]:62683) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmEi1-0000oY-FH for qemu-devel@nongnu.org; Tue, 20 Sep 2016 02:39:13 -0400 Message-ID: <57E0D910.5050203@intel.com> Date: Tue, 20 Sep 2016 14:37:04 +0800 From: Jike Song MIME-Version: 1.0 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> <20160920054851.GA2186@bjsdjshi@linux.vnet.ibm.com> In-Reply-To: <20160920054851.GA2186@bjsdjshi@linux.vnet.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: 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 On 09/20/2016 01:48 PM, Dong Jia Shi wrote: > * 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. > NP, thanks for the info :) > 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. > So 'vfio-ccw' is actually the driver of physical device. > 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). Glad to know that vfio-mdev works for all mdev devices :) -- Thanks, Jike