1 # SPDX-License-Identifier: GPL-2.0-only
9 This option is selected by any driver which implements the virtio
10 bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG
16 Modern PCI device implementation. This module implements the
17 basic probe and control for devices which are based on modern
18 PCI device with possible vendor specific extensions. Any
19 module that selects this module must depend on PCI.
21 config VIRTIO_PCI_LIB_LEGACY
24 Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
26 This module implements the basic probe and control for devices
27 which are based on legacy PCI device. Any module that selects this
28 module must depend on PCI.
30 menuconfig VIRTIO_MENU
36 config VIRTIO_HARDEN_NOTIFICATION
37 bool "Harden virtio notification"
40 Enable this to harden the device notifications and suppress
41 those that happen at a time where notifications are illegal.
43 Experimental: Note that several drivers still have issues that
44 may cause crashes or hangs when correct handling of
45 notifications is enforced; depending on the subset of
46 drivers and devices you use, this may or may not work.
51 tristate "PCI driver for virtio devices"
56 This driver provides support for virtio based paravirtual device
57 drivers over PCI. This requires that your VMM has appropriate PCI
58 virtio backends. Most QEMU based VMMs should support these devices
63 config VIRTIO_PCI_ADMIN_LEGACY
65 depends on VIRTIO_PCI && (X86 || COMPILE_TEST)
68 config VIRTIO_PCI_LEGACY
69 bool "Support for legacy virtio draft 0.9.X and older devices"
72 select VIRTIO_PCI_LIB_LEGACY
74 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
76 This option enables building a transitional driver, supporting
77 both devices conforming to Virtio 1 specification, and legacy devices.
78 If disabled, you get a slightly smaller, non-transitional driver,
79 with no legacy compatibility.
81 So look out into your driveway. Do you have a flying car? If
82 so, you can happily disable this option and virtio will not
83 break. Otherwise, leave it set. Unless you're testing what
84 life will be like in The Future.
89 tristate "vDPA driver for virtio devices"
93 This driver provides support for virtio based paravirtual
94 device driver over vDPA bus. For this to be useful, you need
95 an appropriate vDPA device implementation that operates on a
96 physical device to allow the datapath of virtio to be
97 offloaded to hardware.
102 tristate "Support for virtio pmem driver"
106 This driver provides access to virtio-pmem devices, storage devices
107 that are mapped into the physical address space - similar to NVDIMMs
108 - with a virtio-based flushing interface.
112 config VIRTIO_BALLOON
113 tristate "Virtio balloon driver"
115 select MEMORY_BALLOON
116 select PAGE_REPORTING
118 This driver supports increasing and decreasing the amount
119 of memory within a KVM guest.
124 tristate "Virtio mem driver"
125 depends on X86_64 || ARM64 || RISCV
127 depends on MEMORY_HOTPLUG
128 depends on MEMORY_HOTREMOVE
129 depends on CONTIG_ALLOC
130 depends on EXCLUSIVE_SYSTEM_RAM
132 This driver provides access to virtio-mem paravirtualized memory
133 devices, allowing to hotplug and hotunplug memory.
135 This driver currently only supports x86-64 and arm64. Although it
136 should compile on other architectures that implement memory
137 hot(un)plug, architecture-specific and/or common
138 code changes may be required for virtio-mem, kdump and kexec to work as
144 tristate "Virtio input driver"
148 This driver supports virtio input devices such as
149 keyboards, mice and tablets.
154 tristate "Platform bus driver for memory mapped virtio devices"
155 depends on HAS_IOMEM && HAS_DMA
158 This drivers provides support for memory mapped virtio
159 platform device driver.
163 config VIRTIO_MMIO_CMDLINE_DEVICES
164 bool "Memory mapped virtio devices parameter parsing"
165 depends on VIRTIO_MMIO
167 Allow virtio-mmio devices instantiation via the kernel command line
168 or module parameters. Be aware that using incorrect parameters (base
169 address in particular) can crash your system - you have been warned.
170 See Documentation/admin-guide/kernel-parameters.rst for details.
174 config VIRTIO_DMA_SHARED_BUFFER
176 depends on DMA_SHARED_BUFFER
178 This option adds a flavor of dma buffers that are backed by
182 bool "Debug facilities"
185 Enable this to expose debug facilities over debugfs.
186 This allows to debug features, to see what features the device
187 advertises and to set filter for features used by driver.