Home
last modified time | relevance | path

Searched refs:vfio (Results 1 – 25 of 38) sorted by relevance

12

/linux/drivers/vfio/
H A DMakefile2 obj-$(CONFIG_VFIO) += vfio.o
4 vfio-y += vfio_main.o
5 vfio-$(CONFIG_VFIO_DEVICE_CDEV) += device_cdev.o
6 vfio-$(CONFIG_VFIO_GROUP) += group.o
7 vfio-$(CONFIG_IOMMUFD) += iommufd.o
8 vfio-$(CONFIG_VFIO_CONTAINER) += container.o
9 vfio-$(CONFIG_VFIO_VIRQFD) += virqfd.o
10 vfio-$(CONFIG_VFIO_DEBUGFS) += debugfs.o
H A Dcontainer.c27 static struct vfio { struct
30 } vfio; argument
104 mutex_lock(&vfio.iommu_drivers_lock); in vfio_register_iommu_driver()
107 list_for_each_entry(tmp, &vfio.iommu_drivers_list, vfio_next) { in vfio_register_iommu_driver()
109 mutex_unlock(&vfio.iommu_drivers_lock); in vfio_register_iommu_driver()
115 list_add(&driver->vfio_next, &vfio.iommu_drivers_list); in vfio_register_iommu_driver()
117 mutex_unlock(&vfio.iommu_drivers_lock); in vfio_register_iommu_driver()
127 mutex_lock(&vfio.iommu_drivers_lock); in vfio_unregister_iommu_driver()
128 list_for_each_entry(driver, &vfio.iommu_drivers_list, vfio_next) { in vfio_unregister_iommu_driver()
131 mutex_unlock(&vfio.iommu_drivers_lock); in vfio_unregister_iommu_driver()
[all …]
H A Dvfio_main.c51 static struct vfio { struct
55 } vfio; argument
202 ida_free(&vfio.device_ida, device->index); in vfio_device_release()
208 simple_release_fs(&vfio.vfs_mount, &vfio.fs_count); in vfio_device_release()
268 ret = simple_pin_fs(&vfio_fs_type, &vfio.vfs_mount, &vfio.fs_count); in vfio_fs_inode_new()
272 inode = alloc_anon_inode(vfio.vfs_mount->mnt_sb); in vfio_fs_inode_new()
274 simple_release_fs(&vfio.vfs_mount, &vfio.fs_count); in vfio_fs_inode_new()
287 ret = ida_alloc_max(&vfio.device_ida, MINORMASK, GFP_KERNEL); in vfio_init_device()
317 simple_release_fs(&vfio.vfs_mount, &vfio.fs_count); in vfio_init_device()
320 ida_free(&vfio.device_ida, device->index); in vfio_init_device()
[all …]
/linux/Documentation/ABI/testing/
H A Ddebugfs-vfio1 What: /sys/kernel/debug/vfio
6 of vfio devices, it's a common directory for all vfio devices.
10 What: /sys/kernel/debug/vfio/<device>/migration
15 of vfio devices that support live migration.
16 The debugfs of each vfio device that supports live migration
19 What: /sys/kernel/debug/vfio/<device>/migration/state
23 Description: Read the live migration status of the vfio device.
27 What: /sys/kernel/debug/vfio/<device>/migration/features
31 Description: Read the migration features of the vfio device.
33 What: /sys/kernel/debug/vfio/<device>/pci
[all …]
H A Dsysfs-devices-vfio-dev1 What: /sys/.../<device>/vfio-dev/vfioX/
6 vfio driver. The layout under this directory matches what
8 index marking this device in vfio.
H A Dsysfs-bus-vfio-mdev61 by this type. For example, "vfio-pci" for a PCI device,
62 "vfio-platform" for platform device.
/linux/drivers/vfio/platform/
H A DMakefile2 vfio-platform-base-y := vfio_platform_common.o vfio_platform_irq.o
3 obj-$(CONFIG_VFIO_PLATFORM_BASE) += vfio-platform-base.o
6 vfio-platform-y := vfio_platform.o
7 obj-$(CONFIG_VFIO_PLATFORM) += vfio-platform.o
9 vfio-amba-y := vfio_amba.o
10 obj-$(CONFIG_VFIO_AMBA) += vfio-amba.o
/linux/Documentation/arch/s390/
H A Dvfio-ccw.rst2 vfio-ccw: the basic infrastructure
8 Here we describe the vfio support for I/O subchannel devices for
9 Linux/s390. Motivation for vfio-ccw is to passthrough subchannels to a
10 virtual machine, while vfio is the means.
20 Thus when we introduce vfio support for these devices, we realize it
21 with a mediated device (mdev) implementation. The vfio mdev will be
23 vfio framework. And we add read/write callbacks for special vfio I/O
40 For vfio mediated device framework:
41 - Documentation/driver-api/vfio-mediated-device.rst
43 Motivation of vfio-ccw
[all …]
/linux/Documentation/networking/device_drivers/ethernet/amd/
H A Dpds_vfio_pci.rst14 The ``pds-vfio-pci`` module is a PCI driver that supports Live Migration
20 The pds-vfio-pci device is enabled via multiple configuration steps and
26 example assumes the pds_core and pds-vfio-pci modules are already
38 # Prevent non-vfio VF driver from probing the VF device
44 # Allow the VF to be bound to the pds-vfio-pci driver
45 echo "pds-vfio-pci" > /sys/class/pci_bus/$PF_BUS/device/$VF_BDF/driver_override
47 # Bind the VF to the pds-vfio-pci driver
48 echo "$VF_BDF" > /sys/bus/pci/drivers/pds-vfio-pci/bind
50 After performing the steps above, a file in /dev/vfio/<iommu_group>
/linux/Documentation/driver-api/
H A Dvfio-pci-device-specific-driver-acceptance.rst3 Acceptance criteria for vfio-pci device specific driver variants
8 The vfio-pci driver exists as a device agnostic driver using the
11 vfio-pci driver does include some device specific support, further
13 sustainable. The vfio-pci driver has therefore split out
14 vfio-pci-core as a library that may be reused to implement features
21 accessible via the vfio-pci base driver. Authors of such drivers
32 available to the user via vfio-pci, what safeguards exist to validate
35 to the overall vfio maintainer.
/linux/drivers/vfio/platform/reset/
H A DMakefile2 vfio-platform-calxedaxgmac-y := vfio_platform_calxedaxgmac.o
3 vfio-platform-amdxgbe-y := vfio_platform_amdxgbe.o
5 obj-$(CONFIG_VFIO_PLATFORM_CALXEDAXGMAC_RESET) += vfio-platform-calxedaxgmac.o
6 obj-$(CONFIG_VFIO_PLATFORM_AMDXGBE_RESET) += vfio-platform-amdxgbe.o
/linux/tools/testing/selftests/vfio/scripts/
H A Dsetup.sh40 set_driver_override ${device_bdf} vfio-pci
43 bind ${device_bdf} vfio-pci
44 touch ${device_dir}/vfio-pci
H A Dcleanup.sh12 if [ -f ${device_dir}/vfio-pci ]; then
13 unbind ${device_bdf} vfio-pci
/linux/drivers/vfio/pci/xe/
H A DMakefile2 obj-$(CONFIG_XE_VFIO_PCI) += xe-vfio-pci.o
3 xe-vfio-pci-y := main.o
/linux/drivers/vfio/fsl-mc/
H A DMakefile3 vfio-fsl-mc-y := vfio_fsl_mc.o vfio_fsl_mc_intr.o
4 obj-$(CONFIG_VFIO_FSL_MC) += vfio-fsl-mc.o
/linux/drivers/vfio/pci/nvgrace-gpu/
H A DMakefile2 obj-$(CONFIG_NVGRACE_GPU_VFIO_PCI) += nvgrace-gpu-vfio-pci.o
3 nvgrace-gpu-vfio-pci-y := main.o
/linux/drivers/vfio/pci/hisilicon/
H A DMakefile2 obj-$(CONFIG_HISI_ACC_VFIO_PCI) += hisi-acc-vfio-pci.o
3 hisi-acc-vfio-pci-y := hisi_acc_vfio_pci.o
/linux/drivers/vfio/pci/mlx5/
H A DMakefile2 obj-$(CONFIG_MLX5_VFIO_PCI) += mlx5-vfio-pci.o
3 mlx5-vfio-pci-y := main.o cmd.o
/linux/drivers/vfio/pci/pds/
H A DMakefile4 obj-$(CONFIG_PDS_VFIO_PCI) += pds-vfio-pci.o
6 pds-vfio-pci-y := \
H A DKconfig18 will be called pds-vfio-pci.
/linux/Documentation/translations/zh_CN/driver-api/
H A Dindex.rst116 * vfio-mediated-device
117 * vfio
118 * vfio-pci-device-specific-driver-acceptance
/linux/samples/vfio-mdev/
H A DREADME.rst1 Using the mtty vfio-mdev sample code
4 mtty is a sample vfio-mdev driver that demonstrates how to use the mediated
50 -device vfio-pci,\
/linux/virt/kvm/
H A DMakefile.kvm9 kvm-$(CONFIG_KVM_VFIO) += $(KVM)/vfio.o
/linux/tools/testing/selftests/vfio/lib/
H A Dlibvfio.mk4 LIBVFIO_SRCDIR := $(selfdir)/vfio/lib
/linux/samples/
H A DMakefile33 obj-y += vfio-mdev/

12