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
12 Modern PCI device implementation. This module implements the
13 basic probe and control for devices which are based on modern
14 PCI device with possible vendor specific extensions. Any
15 module that selects this module must depend on PCI.
17 config VIRTIO_PCI_LIB_LEGACY
20 Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
22 This module implements the basic probe and control for devices
23 which are based on legacy PCI device. Any module that selects this
24 module must depend on PCI.
26 menuconfig VIRTIO_MENU
33 tristate "PCI driver for virtio devices"
38 This driver provides support for virtio based paravirtual device
39 drivers over PCI. This requires that your VMM has appropriate PCI
40 virtio backends. Most QEMU based VMMs should support these devices
45 config VIRTIO_PCI_LEGACY
46 bool "Support for legacy virtio draft 0.9.X and older devices"
49 select VIRTIO_PCI_LIB_LEGACY
51 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
53 This option enables building a transitional driver, supporting
54 both devices conforming to Virtio 1 specification, and legacy devices.
55 If disabled, you get a slightly smaller, non-transitional driver,
56 with no legacy compatibility.
58 So look out into your driveway. Do you have a flying car? If
59 so, you can happily disable this option and virtio will not
60 break. Otherwise, leave it set. Unless you're testing what
61 life will be like in The Future.
66 tristate "vDPA driver for virtio devices"
70 This driver provides support for virtio based paravirtual
71 device driver over vDPA bus. For this to be useful, you need
72 an appropriate vDPA device implementation that operates on a
73 physical device to allow the datapath of virtio to be
74 offloaded to hardware.
79 tristate "Support for virtio pmem driver"
83 This driver provides access to virtio-pmem devices, storage devices
84 that are mapped into the physical address space - similar to NVDIMMs
85 - with a virtio-based flushing interface.
90 tristate "Virtio balloon driver"
95 This driver supports increasing and decreasing the amount
96 of memory within a KVM guest.
101 tristate "Virtio mem driver"
102 depends on X86_64 || ARM64
104 depends on MEMORY_HOTPLUG
105 depends on MEMORY_HOTREMOVE
106 depends on CONTIG_ALLOC
107 depends on EXCLUSIVE_SYSTEM_RAM
109 This driver provides access to virtio-mem paravirtualized memory
110 devices, allowing to hotplug and hotunplug memory.
112 This driver was only tested under x86-64 and arm64, but should
113 theoretically work on all architectures that support memory hotplug
119 tristate "Virtio input driver"
123 This driver supports virtio input devices such as
124 keyboards, mice and tablets.
129 tristate "Platform bus driver for memory mapped virtio devices"
130 depends on HAS_IOMEM && HAS_DMA
133 This drivers provides support for memory mapped virtio
134 platform device driver.
138 config VIRTIO_MMIO_CMDLINE_DEVICES
139 bool "Memory mapped virtio devices parameter parsing"
140 depends on VIRTIO_MMIO
142 Allow virtio-mmio devices instantiation via the kernel command line
143 or module parameters. Be aware that using incorrect parameters (base
144 address in particular) can crash your system - you have been warned.
145 See Documentation/admin-guide/kernel-parameters.rst for details.
149 config VIRTIO_DMA_SHARED_BUFFER
151 depends on DMA_SHARED_BUFFER
153 This option adds a flavor of dma buffers that are backed by