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 menuconfig VIRTIO_MENU
30 tristate "PCI driver for virtio devices"
35 This driver provides support for virtio based paravirtual device
36 drivers over PCI. This requires that your VMM has appropriate PCI
37 virtio backends. Most QEMU based VMMs should support these devices
42 config VIRTIO_PCI_LEGACY
43 bool "Support for legacy virtio draft 0.9.X and older devices"
47 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
49 This option enables building a transitional driver, supporting
50 both devices conforming to Virtio 1 specification, and legacy devices.
51 If disabled, you get a slightly smaller, non-transitional driver,
52 with no legacy compatibility.
54 So look out into your driveway. Do you have a flying car? If
55 so, you can happily disable this option and virtio will not
56 break. Otherwise, leave it set. Unless you're testing what
57 life will be like in The Future.
62 tristate "vDPA driver for virtio devices"
66 This driver provides support for virtio based paravirtual
67 device driver over vDPA bus. For this to be useful, you need
68 an appropriate vDPA device implementation that operates on a
69 physical device to allow the datapath of virtio to be
70 offloaded to hardware.
75 tristate "Support for virtio pmem driver"
79 This driver provides access to virtio-pmem devices, storage devices
80 that are mapped into the physical address space - similar to NVDIMMs
81 - with a virtio-based flushing interface.
86 tristate "Virtio balloon driver"
91 This driver supports increasing and decreasing the amount
92 of memory within a KVM guest.
97 tristate "Virtio mem driver"
101 depends on MEMORY_HOTPLUG_SPARSE
102 depends on MEMORY_HOTREMOVE
103 depends on CONTIG_ALLOC
105 This driver provides access to virtio-mem paravirtualized memory
106 devices, allowing to hotplug and hotunplug memory.
108 This driver was only tested under x86-64, but should theoretically
109 work on all architectures that support memory hotplug and hotremove.
114 tristate "Virtio input driver"
118 This driver supports virtio input devices such as
119 keyboards, mice and tablets.
124 tristate "Platform bus driver for memory mapped virtio devices"
125 depends on HAS_IOMEM && HAS_DMA
128 This drivers provides support for memory mapped virtio
129 platform device driver.
133 config VIRTIO_MMIO_CMDLINE_DEVICES
134 bool "Memory mapped virtio devices parameter parsing"
135 depends on VIRTIO_MMIO
137 Allow virtio-mmio devices instantiation via the kernel command line
138 or module parameters. Be aware that using incorrect parameters (base
139 address in particular) can crash your system - you have been warned.
140 See Documentation/admin-guide/kernel-parameters.rst for details.
144 config VIRTIO_DMA_SHARED_BUFFER
146 depends on DMA_SHARED_BUFFER
148 This option adds a flavor of dma buffers that are backed by