On Wed, 25 May 2016 07:13:58 +0000 "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote: > > From: Kirti Wankhede [mailto:kwankhede@xxxxxxxxxx] > > Sent: Wednesday, May 25, 2016 3:58 AM > > > > This series adds Mediated device support to v4.6 Linux host kernel. Purpose > > of this series is to provide a common interface for mediated device > > management that can be used by different devices. This series introduces > > Mdev core module that create and manage mediated devices, VFIO based driver > > for mediated PCI devices that are created by Mdev core module and update > > VFIO type1 IOMMU module to support mediated devices. > > Thanks. "Mediated device" is more generic than previous one. :-) > > > > > What's new in v4? > > - Renamed 'vgpu' module to 'mdev' module that represent generic term > > 'Mediated device'. > > - Moved mdev directory to drivers/vfio directory as this is the extension > > of VFIO APIs for mediated devices. > > - Updated mdev driver to be flexible to register multiple types of drivers > > to mdev_bus_type bus. > > - Updated mdev core driver with mdev_put_device() and mdev_get_device() for > > mediated devices. > > > > > > Just curious. In this version you move the whole mdev core under > VFIO now. Sorry if I missed any agreement on this change. IIRC Alex > doesn't want VFIO to manage mdev life-cycle directly. Instead VFIO is > just a mdev driver on created mediated devices.... I did originally suggest keeping them separate, but as we've progressed through the implementation, it's become more clear that the mediated device interface is very much tied to the vfio interface, acting mostly as a passthrough. So I thought it made sense to pull them together. Still open to discussion of course. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
