4 This option is selected by any driver which implements the virtio
5 bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG
15 tristate "PCI driver for virtio devices"
19 This driver provides support for virtio based paravirtual device
20 drivers over PCI. This requires that your VMM has appropriate PCI
21 virtio backends. Most QEMU based VMMs should support these devices
26 config VIRTIO_PCI_LEGACY
27 bool "Support for legacy virtio draft 0.9.X and older devices"
31 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
33 This option enables building a transitional driver, supporting
34 both devices conforming to Virtio 1 specification, and legacy devices.
35 If disabled, you get a slightly smaller, non-transitional driver,
36 with no legacy compatibility.
38 So look out into your driveway. Do you have a flying car? If
39 so, you can happily disable this option and virtio will not
40 break. Otherwise, leave it set. Unless you're testing what
41 life will be like in The Future.
46 tristate "Virtio balloon driver"
50 This driver supports increasing and decreasing the amount
51 of memory within a KVM guest.
56 tristate "Virtio input driver"
60 This driver supports virtio input devices such as
61 keyboards, mice and tablets.
66 tristate "Platform bus driver for memory mapped virtio devices"
67 depends on HAS_IOMEM && HAS_DMA
70 This drivers provides support for memory mapped virtio
71 platform device driver.
75 config VIRTIO_MMIO_CMDLINE_DEVICES
76 bool "Memory mapped virtio devices parameter parsing"
77 depends on VIRTIO_MMIO
79 Allow virtio-mmio devices instantiation via the kernel command line
80 or module parameters. Be aware that using incorrect parameters (base
81 address in particular) can crash your system - you have been warned.
82 See Documentation/admin-guide/kernel-parameters.rst for details.