* Jike Song <jike.s...@intel.com> [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 <kwankh...@nvidia.com> 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
