Changes in Kconfig

2202844e - vfio/migration: Add debugfs to live migration driver

Mon, 06 Nov 2023 07:22:23 +0000

vfio/migration: Add debugfs to live migration driverThere are multiple devices, software and operational steps involvedin the process of live migration. An error occurred on any node maycause the live migration operation to fail.This complex process makes it very difficult to locate and analyzethe cause when the function fails.In order to quickly locate the cause of the problem when thelive migration fails, I added a set of debugfs to the vfiolive migration driver. +-------------------------------------------+ | | | | | QEMU | | | | | +---+----------------------------+----------+ | ^ | ^ | | | | | | | | v | v | +---------+--+ +---------+--+ |src vfio_dev| |dst vfio_dev| +--+---------+ +--+---------+ | ^ | ^ | | | | v | | | +-----------+----+ +-----------+----+ |src dev debugfs | |dst dev debugfs | +----------------+ +----------------+The entire debugfs directory will be based on the definition ofthe CONFIG_DEBUG_FS macro. If this macro is not enabled, theinterfaces in vfio.h will be empty definitions, and the creationand initialization of the debugfs directory will not be executed. vfio | +--- | +---migration | +--state | +--- +---migration +--statedebugfs will create a public root directory "vfio" file.then create a dev_name() file for each live migration device.First, create a unified state acquisition file of "migration"in this device directory.Then, create a public live migration state lookup file "state".Signed-off-by: Longfang Liu Reviewed-by: Cédric Le Goater Link: https://lore.kernel.org/r/20231106072225.28577-2-liulongfang@huawei.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

c1cce6d0 - vfio: Compile vfio_group infrastructure optionally

Tue, 18 Jul 2023 13:55:50 +0000

vfio: Compile vfio_group infrastructure optionallyvfio_group is not needed for vfio device cdev, so with vfio device cdevintroduced, the vfio_group infrastructures can be compiled out if onlycdev is needed.Reviewed-by: Jason Gunthorpe Tested-by: Nicolin Chen Tested-by: Matthew Rosato Tested-by: Yanting Jiang Tested-by: Shameer Kolothum Tested-by: Terrence Xu Tested-by: Zhenzhong Duan Signed-off-by: Yi Liu Link: https://lore.kernel.org/r/20230718135551.6592-26-yi.l.liu@intel.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

8b6f173a - vfio: Add cdev for vfio_device

Tue, 18 Jul 2023 13:55:43 +0000

vfio: Add cdev for vfio_deviceThis adds cdev support for vfio_device. It allows the user to directlyopen a vfio device w/o using the legacy container/group interface, as aprerequisite for supporting new iommu features like nested translationand etc.The device fd opened in this manner doesn't have the capability to accessthe device as the fops open() doesn't open the device until the successfulVFIO_DEVICE_BIND_IOMMUFD ioctl which will be added in a later patch.With this patch, devices registered to vfio core would have both the legacygroup and the new device interfaces created.- group interface : /dev/vfio/$groupID- device interface: /dev/vfio/devices/vfioX - normal device ("X" is a unique number across vfio devices)For a given device, the user can identify the matching vfioX by searchingthe vfio-dev folder under the sysfs path of the device. Take PCI device(0000:6a:01.0) as an example, /sys/bus/pci/devices/0000\:6a\:01.0/vfio-dev/vfioXimplies the matching vfioX under /dev/vfio/devices/, and vfio-dev/vfioX/devcontains the major:minor number of the matching /dev/vfio/devices/vfioX.The user can get device fd by opening the /dev/vfio/devices/vfioX.The vfio_device cdev logic in this patch:*) __vfio_register_dev() path ends up doing cdev_device_add() for each vfio_device if VFIO_DEVICE_CDEV configured.*) vfio_unregister_group_dev() path does cdev_device_del();cdev interface does not support noiommu devices, so VFIO only creates thelegacy group interface for the physical devices that do not have IOMMU.noiommu users should use the legacy group interface.Reviewed-by: Kevin Tian Reviewed-by: Jason Gunthorpe Tested-by: Terrence Xu Tested-by: Nicolin Chen Tested-by: Matthew Rosato Tested-by: Yanting Jiang Tested-by: Shameer Kolothum Tested-by: Zhenzhong Duan Signed-off-by: Yi Liu Link: https://lore.kernel.org/r/20230718135551.6592-19-yi.l.liu@intel.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

234489ac - vfio/cdx: add support for CDX bus

Wed, 31 May 2023 12:45:57 +0000

vfio/cdx: add support for CDX busvfio-cdx driver enables IOCTLs for user space to queryMMIO regions for CDX devices and mmap them. This changealso adds support for reset of CDX devices. With VFIOenabled on CDX devices, user-space applications can alsoexercise DMA securely via IOMMU on these devices.This change adds the VFIO CDX driver and enables the followingioctls for CDX devices: - VFIO_DEVICE_GET_INFO: - VFIO_DEVICE_GET_REGION_INFO - VFIO_DEVICE_RESETSigned-off-by: Nipun Gupta Reviewed-by: Pieter Jansen van Vuuren Tested-by: Nikhil Agarwal Link: https://lore.kernel.org/r/20230531124557.11009-1-nipun.gupta@amd.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

c9a397ce - vfio: Support VFIO_NOIOMMU with iommufd

Wed, 18 Jan 2023 17:50:28 +0000

vfio: Support VFIO_NOIOMMU with iommufdAdd a small amount of emulation to vfio_compat to accept the SET_IOMMU toVFIO_NOIOMMU_IOMMU and have vfio just ignore iommufd if it is working on ano-iommu enabled device.Move the enable_unsafe_noiommu_mode module out of container.c intovfio_main.c so that it is always available even if VFIO_CONTAINER=n.This passes Alex's mini-test:https://github.com/awilliam/tests/blob/master/vfio-noiommu-pci-device-open.cLink: https://lore.kernel.org/r/0-v3-480cd64a16f7+1ad0-iommufd_noiommu_jgg@nvidia.comReviewed-by: Kevin Tian Acked-by: Alex Williamson Signed-off-by: Jason Gunthorpe List of files: /linux-6.15/drivers/vfio/Kconfig

e2d55709 - vfio: Fold vfio_virqfd.ko into vfio.ko

Mon, 05 Dec 2022 15:29:20 +0000

vfio: Fold vfio_virqfd.ko into vfio.koThis is only 1.8k, putting it in its own module is not reallynecessary. The kconfig infrastructure is still there to completely removeit for systems that are trying for small footprint.Put it in the main vfio.ko module now that kbuild can support multiple .cfiles.Signed-off-by: Jason Gunthorpe Reviewed-by: Cornelia Huck Link: https://lore.kernel.org/r/5-v5-fc5346cacfd4+4c482-vfio_modules_jgg@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

20601c45 - vfio: Remove CONFIG_VFIO_SPAPR_EEH

Mon, 05 Dec 2022 15:29:19 +0000

vfio: Remove CONFIG_VFIO_SPAPR_EEHWe don't need a kconfig symbol for this, just directly test CONFIG_EEH inthe few places that need it.Reviewed-by: Christoph Hellwig Reviewed-by: Cornelia Huck Signed-off-by: Jason Gunthorpe Link: https://lore.kernel.org/r/4-v5-fc5346cacfd4+4c482-vfio_modules_jgg@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

e5a9ec7e - vfio: Make vfio_container optionally compiled

Tue, 29 Nov 2022 20:31:54 +0000

vfio: Make vfio_container optionally compiledAdd a kconfig CONFIG_VFIO_CONTAINER that controls compiling the containercode. If 'n' then only iommufd will provide the container service. All thesupport for vfio iommu drivers, including type1, will not be built.This allows a compilation check that no inappropriate dependencies betweenthe device/group and container have been created.Link: https://lore.kernel.org/r/9-v4-42cd2eb0e3eb+335a-vfio_iommufd_jgg@nvidia.comReviewed-by: Kevin Tian Reviewed-by: Alex Williamson Tested-by: Alex Williamson Tested-by: Nicolin Chen Tested-by: Yi Liu Tested-by: Lixiao Yang Tested-by: Matthew Rosato Tested-by: Yu He Signed-off-by: Jason Gunthorpe List of files: /linux-6.15/drivers/vfio/Kconfig

2a3dab19 - vfio-iommufd: Allow iommufd to be used in place of a container fd

Tue, 29 Nov 2022 20:31:50 +0000

vfio-iommufd: Allow iommufd to be used in place of a container fdThis makes VFIO_GROUP_SET_CONTAINER accept both a vfio container FD and aniommufd.In iommufd mode an IOAS will exist after the SET_CONTAINER, but it willnot be attached to any groups.For VFIO this means that the VFIO_GROUP_GET_STATUS andVFIO_GROUP_FLAGS_VIABLE works subtly differently. With the container FDthe iommu_group_claim_dma_owner() is done during SET_CONTAINER but forIOMMUFD this is done during VFIO_GROUP_GET_DEVICE_FD. Meaning thatVFIO_GROUP_FLAGS_VIABLE could be set but GET_DEVICE_FD will fail due toviability.As GET_DEVICE_FD can fail for many reasons already this is not expected tobe a meaningful difference.Reorganize the tests for if the group has an assigned container or iommuinto a vfio_group_has_iommu() function and consolidate all the duplicatedWARN_ON's etc related to this.Call container functions only if a container is actually present on thegroup.Link: https://lore.kernel.org/r/5-v4-42cd2eb0e3eb+335a-vfio_iommufd_jgg@nvidia.comReviewed-by: Kevin Tian Reviewed-by: Alex Williamson Tested-by: Alex Williamson Tested-by: Nicolin Chen Tested-by: Yi Liu Tested-by: Lixiao Yang Tested-by: Matthew Rosato Tested-by: Yu He Signed-off-by: Jason Gunthorpe List of files: /linux-6.15/drivers/vfio/Kconfig

80c4b92a - vfio: Introduce the DMA logging feature support

Thu, 08 Sep 2022 18:34:43 +0000

vfio: Introduce the DMA logging feature supportIntroduce the DMA logging feature support in the vfio core layer.It includes the processing of the device start/stop/report DMA loggingUAPIs and calling the relevant driver 'op' to do the work.Specifically,Upon start, the core translates the given input ranges into an intervaltree, checks for unexpected overlapping, non aligned ranges and thenpass the translated input to the driver for start tracking the givenranges.Upon report, the core translates the given input user space bitmap andpage size into an IOVA kernel bitmap iterator. Then it iterates it andcall the driver to set the corresponding bits for the dirtied pages in aspecific IOVA range.Upon stop, the driver is called to stop the previous started tracking.The next patches from the series will introduce the mlx5 driverimplementation for the logging ops.Signed-off-by: Yishai Hadas Link: https://lore.kernel.org/r/20220908183448.195262-6-yishaih@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/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/Kconfig

ca4ddaac - vfio: Use select for eventfd

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

vfio: Use select for eventfdIf VFIO_VIRQFD is required then turn on eventfd automatically.The majority of kconfig users of the EVENTFD use select not depends on.Signed-off-by: Jason Gunthorpe Reviewed-by: Christoph Hellwig Signed-off-by: Yishai Hadas Link: https://lore.kernel.org/r/20210826103912.128972-12-yishaih@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

26c22cfd - vfio: Use config not menuconfig for VFIO_NOIOMMU

Fri, 16 Jul 2021 18:39:12 +0000

vfio: Use config not menuconfig for VFIO_NOIOMMUVFIO_NOIOMMU is supposed to be an element in the VFIO menu, not starta new menu. Correct this copy-paste mistake.Fixes: 03a76b60f8ba ("vfio: Include No-IOMMU mode")Signed-off-by: Jason Gunthorpe Reviewed-by: Cornelia Huck Link: https://lore.kernel.org/r/0-v1-3f0b685c3679+478-vfio_menuconfig_jgg@nvidia.comSigned-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

b2b12db5 - vfio: Depend on MMU

Fri, 05 Mar 2021 01:30:03 +0000

vfio: Depend on MMUVFIO_IOMMU_TYPE1 does not compile with !MMU:../drivers/vfio/vfio_iommu_type1.c: In function 'follow_fault_pfn':../drivers/vfio/vfio_iommu_type1.c:536:22: error: implicit declaration of function 'pte_write'; did you mean 'vfs_write'? [-Werror=implicit-function-declaration]So require it.Suggested-by: Cornelia Huck Signed-off-by: Jason Gunthorpe Message-Id: <0-v1-02cb5500df6e+78-vfio_no_mmu_jgg@nvidia.com>Signed-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

179209fa - vfio: IOMMU_API should be selected

Tue, 23 Feb 2021 19:17:46 +0000

vfio: IOMMU_API should be selectedAs IOMMU_API is a kconfig without a description (eg does not show in themenu) the correct operator is select not 'depends on'. Using 'depends on'for this kind of symbol means VFIO is not selectable unless some otherrandom kconfig has already enabled IOMMU_API for it.Fixes: cba3345cc494 ("vfio: VFIO core")Signed-off-by: Jason Gunthorpe Message-Id: <1-v1-df057e0f92c3+91-vfio_arm_compile_test_jgg@nvidia.com>Reviewed-by: Eric Auger Signed-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/Kconfig

fb1ff4c1 - vfio/fsl-mc: Add VFIO framework skeleton for fsl-mc devices

Mon, 05 Oct 2020 17:36:45 +0000

vfio/fsl-mc: Add VFIO framework skeleton for fsl-mc devicesDPAA2 (Data Path Acceleration Architecture) consists inmechanisms for processing Ethernet packets, queue management,accelerators, etc.The Management Complex (mc) is a hardware entity that manages the DPAA2hardware resources. It provides an object-based abstraction for softwaredrivers to use the DPAA2 hardware. The MC mediates operations such ascreate, discover, destroy of DPAA2 objects.The MC provides memory-mapped I/O command interfaces (MC portals) whichDPAA2 software drivers use to operate on DPAA2 objects.A DPRC is a container object that holds other types of DPAA2 objects.Each object in the DPRC is a Linux device and bound to a driver.The MC-bus driver is a platform driver (different from PCI or platformbus). The DPRC driver does runtime management of a bus instance. Itperforms the initial scan of the DPRC and handles changes in the DPRCconfiguration (adding/removing objects).All objects inside a container share the same hardware isolationcontext, meaning that only an entire DPRC can be assigned toa virtual machine.When a container is assigned to a virtual machine, all the objectswithin that container are assigned to that virtual machine.The DPRC container assigned to the virtual machine is not allowedto change contents (add/remove objects) by the guest. The restrictionis set by the host and enforced by the mc hardware.The DPAA2 objects can be directly assigned to the guest. Howeverthe MC portals (the memory mapped command interface to the MC) needto be emulated because there are commands that configure theinterrupts and the isolation IDs which are virtual in the guest.Example:echo vfio-fsl-mc > /sys/bus/fsl-mc/devices/dprc.2/driver_overrideecho dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bindThe dprc.2 is bound to the VFIO driver and all the objects withindprc.2 are going to be bound to the VFIO driver.This patch adds the infrastructure for VFIO support for fsl-mcdevices. Subsequent patches will add support for binding and secureassigning these devices using VFIO.More details about the DPAA2 objects can be found here:Documentation/networking/device_drivers/freescale/dpaa2/overview.rstSigned-off-by: Bharat Bhushan Signed-off-by: Diana Craciun Reviewed-by: Eric Auger Signed-off-by: Alex Williamson List of files: /linux-6.15/drivers/vfio/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/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/Kconfig

5dd50aae - Make anon_inodes unconditional

Mon, 05 Nov 2018 17:40:31 +0000

Make anon_inodes unconditionalMake the anon_inodes facility unconditional so that it can be used by coreVFS code and pidfd code.Signed-off-by: David Howells Signed-off-by: Al Viro [christian@brauner.io: adapt commit message to mention pidfds]Signed-off-by: Christian Brauner List of files: /linux-6.15/drivers/vfio/Kconfig

dadd2299 - Make anon_inodes unconditional

Mon, 05 Nov 2018 17:40:31 +0000

Make anon_inodes unconditionalMake the anon_inodes facility unconditional so that it can be used by coreVFS code.Signed-off-by: David Howells Signed-off-by: Al Viro List of files: /linux-6.15/drivers/vfio/Kconfig