Changes in Kconfig

8bf8c5ee - vfio-mdev: turn VFIO_MDEV into a selectable symbol

Tue, 10 Jan 2023 09:10:07 +0000

vfio-mdev: turn VFIO_MDEV into a selectable symbolVFIO_MDEV is just a library with helpers for the drivers. Stop makingit a user choice and just select it by the drivers that use the helpers.Signed-off-by: Christoph Hellwig Reviewed-by: Jason Gunthorpe Reviewed-by: Tony Krowiak Link: https://lore.kernel.org/r/20230110091009.474427-3-hch@lst.deSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/mdev/Kconfig

85c94dcf - vfio: Use kconfig if XX/endif blocks instead of repeating 'depends on'

Thu, 26 Aug 2021 10:39:11 +0000

vfio: Use kconfig if XX/endif blocks instead of repeating 'depends on'This results in less kconfig wordage and a simpler understanding of therequired "depends on" to create the menu structure.The next patch increases the nesting level a lot so this is a nicepreparatory simplification.Signed-off-by: Jason Gunthorpe Reviewed-by: Christoph Hellwig Signed-off-by: Yishai Hadas Link: https://lore.kernel.org/r/20210826103912.128972-13-yishaih@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/mdev/Kconfig

af3ab3f9 - vfio/mdev: Remove CONFIG_VFIO_MDEV_DEVICE

Thu, 17 Jun 2021 14:22:14 +0000

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 Signed-off-by: Christoph Hellwig Reviewed-by: Cornelia Huck Reviewed-by: Greg Kroah-Hartman Reviewed-by: Kirti Wankhede Link: https://lore.kernel.org/r/20210617142218.1877096-7-hch@lst.deSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/mdev/Kconfig

baa293e9 - docs: driver-api: add a series of orphaned documents

Thu, 27 Jun 2019 18:39:22 +0000

docs: driver-api: add a series of orphaned documentsThere are lots of documents under Documentation/*.txt and a few otherorphan documents elsehwere that belong to the driver-API book.Move them to their right place.Reviewed-by: Cornelia Huck # vfio-related partsAcked-by: Logan Gunthorpe # switchtecSigned-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/vfio/mdev/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

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 Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/vfio/mdev/Kconfig

8e1c5a40 - docs: Add Documentation for Mediated devices

Wed, 16 Nov 2016 20:46:31 +0000

docs: Add Documentation for Mediated devicesAdd file Documentation/vfio-mediated-device.txt that include details ofmediated device framework.Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Signed-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/mdev/Kconfig

fa3da00c - vfio: VFIO based driver for Mediated devices

Wed, 16 Nov 2016 20:46:14 +0000

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 Signed-off-by: Neo Jia Reviewed-by: Jike Song Reviewed-by: Dong Jia Shi Signed-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/mdev/Kconfig

7b96953b - vfio: Mediated device Core driver

Wed, 16 Nov 2016 20:46:13 +0000

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() +--------------+ | | | +<------------------------+ __init() | | | mdev | | | | | | bus | +------------------------>+ |<-> VFIO user | | driver | | probe()/remove() | vfio_mdev.ko | APIs | | | | | | | +-----------+ | +--------------+ | | | MDEV CORE | | MODULE | | mdev.ko | | +-----------+ | mdev_register_device() +--------------+ | | | +<------------------------+ | | | | | | nvidia.ko |<-> physical | | | +------------------------>+ | device | | | | callback +--------------+ | | Physical | | | | device | | mdev_register_device() +--------------+ | | interface | |<------------------------+ | | | | | | i915.ko |<-> physical | | | +------------------------>+ | device | | | | callback +--------------+ | | | | | | | | mdev_register_device() +--------------+ | | | +<------------------------+ | | | | | | ccw_device.ko|<-> physical | | | +------------------------>+ | device | | | | callback +--------------+ | +-----------+ | +---------------+Core driver provides two types of registration interfaces:1. Registration interface for mediated bus driver:/** * struct mdev_driver - Mediated device'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 Signed-off-by: Neo Jia Reviewed-by: Jike Song Reviewed-by: Dong Jia Shi Signed-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/mdev/Kconfig