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