<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6c7f98b3 - vfio/mdev: Remove vfio_mdev.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vfio/mdev/Makefile#6c7f98b3</link>
        <description>vfio/mdev: Remove vfio_mdev.cNow that all mdev drivers directly create their own mdev_device driver anddirectly register with the vfio core&apos;s vfio_device_ops this is all deadcode.Delete vfio_mdev.c and the mdev_parent_ops members that are connected toit.Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Link: http://patchwork.freedesktop.org/patch/msgid/20220411141403.86980-31-hch@lst.deReviewed-by: Kirti Wankhede &lt;kwankhede@nvidia.com&gt;Reviewed-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;

            List of files:
            /linux-6.15/drivers/vfio/mdev/Makefile</description>
        <pubDate>Mon, 11 Apr 2022 14:13:59 +0000</pubDate>
        <dc:creator>Jason Gunthorpe &lt;jgg@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>af3ab3f9 - vfio/mdev: Remove CONFIG_VFIO_MDEV_DEVICE</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vfio/mdev/Makefile#af3ab3f9</link>
        <description>vfio/mdev: Remove CONFIG_VFIO_MDEV_DEVICEFor some reason the vfio_mdev shim mdev_driver has its own module andkconfig. As the next patch requires access to it from mdev.ko merge thetwo modules together and remove VFIO_MDEV_DEVICE.A later patch deletes this driver entirely.Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Cornelia Huck &lt;cohuck@redhat.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Kirti Wankhede &lt;kwankhede@nvidia.com&gt;Link: https://lore.kernel.org/r/20210617142218.1877096-7-hch@lst.deSigned-off-by: Alex Williamson &lt;alex.williamson@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vfio/mdev/Makefile</description>
        <pubDate>Thu, 17 Jun 2021 14:22:14 +0000</pubDate>
        <dc:creator>Jason Gunthorpe &lt;jgg@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vfio/mdev/Makefile#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/vfio/mdev/Makefile</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>fa3da00c - vfio: VFIO based driver for Mediated devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vfio/mdev/Makefile#fa3da00c</link>
        <description>vfio: VFIO based driver for Mediated devicesvfio_mdev driver registers with mdev core driver.mdev core driver creates mediated device and calls probe routine ofvfio_mdev driver for each device.Probe routine of vfio_mdev driver adds mediated device to VFIO core moduleThis driver forms a shim layer that pass through VFIO devices operationsto vendor driver for mediated devices.Signed-off-by: Kirti Wankhede &lt;kwankhede@nvidia.com&gt;Signed-off-by: Neo Jia &lt;cjia@nvidia.com&gt;Reviewed-by: Jike Song &lt;jike.song@intel.com&gt;Reviewed-by: Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;Signed-off-by: Alex Williamson &lt;alex.williamson@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vfio/mdev/Makefile</description>
        <pubDate>Wed, 16 Nov 2016 20:46:14 +0000</pubDate>
        <dc:creator>Kirti Wankhede &lt;kwankhede@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>7b96953b - vfio: Mediated device Core driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vfio/mdev/Makefile#7b96953b</link>
        <description>vfio: Mediated device Core driverDesign for Mediated Device Driver:Main purpose of this driver is to provide a common interface for mediateddevice management that can be used by different drivers of differentdevices.This module provides a generic interface to create the device, add it tomediated bus, add device to IOMMU group and then add it to vfio group.Below is the high Level block diagram, with Nvidia, Intel and IBM devicesas example, since these are the devices which are going to actively usethis module as of now. +---------------+ |               | | +-----------+ |  mdev_register_driver() +--------------+ | |           | +&lt;------------------------+ __init()     | | |  mdev     | |                         |              | | |  bus      | +------------------------&gt;+              |&lt;-&gt; VFIO user | |  driver   | |     probe()/remove()    | vfio_mdev.ko |    APIs | |           | |                         |              | | +-----------+ |                         +--------------+ |               | |  MDEV CORE    | |   MODULE      | |   mdev.ko     | | +-----------+ |  mdev_register_device() +--------------+ | |           | +&lt;------------------------+              | | |           | |                         |  nvidia.ko   |&lt;-&gt; physical | |           | +------------------------&gt;+              |    device | |           | |        callback         +--------------+ | | Physical  | | | |  device   | |  mdev_register_device() +--------------+ | | interface | |&lt;------------------------+              | | |           | |                         |  i915.ko     |&lt;-&gt; physical | |           | +------------------------&gt;+              |    device | |           | |        callback         +--------------+ | |           | | | |           | |  mdev_register_device() +--------------+ | |           | +&lt;------------------------+              | | |           | |                         | ccw_device.ko|&lt;-&gt; physical | |           | +------------------------&gt;+              |    device | |           | |        callback         +--------------+ | +-----------+ | +---------------+Core driver provides two types of registration interfaces:1. Registration interface for mediated bus driver:/**  * struct mdev_driver - Mediated device&apos;s driver  * @name: driver name  * @probe: called when new device created  * @remove:called when device removed  * @driver:device driver structure  *  **/struct mdev_driver {         const char *name;         int  (*probe)  (struct device *dev);         void (*remove) (struct device *dev);         struct device_driver    driver;};Mediated bus driver for mdev device should use this interface to registerand unregister with core driver respectively:int  mdev_register_driver(struct mdev_driver *drv, struct module *owner);void mdev_unregister_driver(struct mdev_driver *drv);Mediated bus driver is responsible to add/delete mediated devices to/fromVFIO group when devices are bound and unbound to the driver.2. Physical device driver interfaceThis interface provides vendor driver the set APIs to manage physicaldevice related work in its driver. APIs are :* dev_attr_groups: attributes of the parent device.* mdev_attr_groups: attributes of the mediated device.* supported_type_groups: attributes to define supported type. This is			 mandatory field.* create: to allocate basic resources in vendor driver for a mediated         device. This is mandatory to be provided by vendor driver.* remove: to free resources in vendor driver when mediated device is         destroyed. This is mandatory to be provided by vendor driver.* open: open callback of mediated device* release: release callback of mediated device* read : read emulation callback.* write: write emulation callback.* ioctl: ioctl callback.* mmap: mmap emulation callback.Drivers should use these interfaces to register and unregister device tomdev core driver respectively:extern int  mdev_register_device(struct device *dev,                                 const struct parent_ops *ops);extern void mdev_unregister_device(struct device *dev);There are no locks to serialize above callbacks in mdev driver andvfio_mdev driver. If required, vendor driver can have locks to serializeabove APIs in their driver.Signed-off-by: Kirti Wankhede &lt;kwankhede@nvidia.com&gt;Signed-off-by: Neo Jia &lt;cjia@nvidia.com&gt;Reviewed-by: Jike Song &lt;jike.song@intel.com&gt;Reviewed-by: Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;Signed-off-by: Alex Williamson &lt;alex.williamson@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vfio/mdev/Makefile</description>
        <pubDate>Wed, 16 Nov 2016 20:46:13 +0000</pubDate>
        <dc:creator>Kirti Wankhede &lt;kwankhede@nvidia.com&gt;</dc:creator>
    </item>
</channel>
</rss>
