1 # SPDX-License-Identifier: GPL-2.0-only
5 This option is selected by any driver which implements the virtio
6 bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG
9 config ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS
12 This option is selected if the architecture may need to enforce
13 VIRTIO_F_ACCESS_PLATFORM
18 Modern PCI device implementation. This module implements the
19 basic probe and control for devices which are based on modern
20 PCI device with possible vendor specific extensions. Any
21 module that selects this module must depend on PCI.
23 config VIRTIO_PCI_LIB_LEGACY
26 Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
28 This module implements the basic probe and control for devices
29 which are based on legacy PCI device. Any module that selects this
30 module must depend on PCI.
32 menuconfig VIRTIO_MENU
39 tristate "PCI driver for virtio devices"
44 This driver provides support for virtio based paravirtual device
45 drivers over PCI. This requires that your VMM has appropriate PCI
46 virtio backends. Most QEMU based VMMs should support these devices
51 config VIRTIO_PCI_LEGACY
52 bool "Support for legacy virtio draft 0.9.X and older devices"
55 select VIRTIO_PCI_LIB_LEGACY
57 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
59 This option enables building a transitional driver, supporting
60 both devices conforming to Virtio 1 specification, and legacy devices.
61 If disabled, you get a slightly smaller, non-transitional driver,
62 with no legacy compatibility.
64 So look out into your driveway. Do you have a flying car? If
65 so, you can happily disable this option and virtio will not
66 break. Otherwise, leave it set. Unless you're testing what
67 life will be like in The Future.
72 tristate "vDPA driver for virtio devices"
76 This driver provides support for virtio based paravirtual
77 device driver over vDPA bus. For this to be useful, you need
78 an appropriate vDPA device implementation that operates on a
79 physical device to allow the datapath of virtio to be
80 offloaded to hardware.
85 tristate "Support for virtio pmem driver"
89 This driver provides access to virtio-pmem devices, storage devices
90 that are mapped into the physical address space - similar to NVDIMMs
91 - with a virtio-based flushing interface.
96 tristate "Virtio balloon driver"
101 This driver supports increasing and decreasing the amount
102 of memory within a KVM guest.
107 tristate "Virtio mem driver"
108 depends on X86_64 || ARM64
110 depends on MEMORY_HOTPLUG
111 depends on MEMORY_HOTREMOVE
112 depends on CONTIG_ALLOC
113 depends on EXCLUSIVE_SYSTEM_RAM
115 This driver provides access to virtio-mem paravirtualized memory
116 devices, allowing to hotplug and hotunplug memory.
118 This driver was only tested under x86-64 and arm64, but should
119 theoretically work on all architectures that support memory hotplug
125 tristate "Virtio input driver"
129 This driver supports virtio input devices such as
130 keyboards, mice and tablets.
135 tristate "Platform bus driver for memory mapped virtio devices"
136 depends on HAS_IOMEM && HAS_DMA
139 This drivers provides support for memory mapped virtio
140 platform device driver.
144 config VIRTIO_MMIO_CMDLINE_DEVICES
145 bool "Memory mapped virtio devices parameter parsing"
146 depends on VIRTIO_MMIO
148 Allow virtio-mmio devices instantiation via the kernel command line
149 or module parameters. Be aware that using incorrect parameters (base
150 address in particular) can crash your system - you have been warned.
151 See Documentation/admin-guide/kernel-parameters.rst for details.
155 config VIRTIO_DMA_SHARED_BUFFER
157 depends on DMA_SHARED_BUFFER
159 This option adds a flavor of dma buffers that are backed by