| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | config VIRTIO |
|---|
| 2 | 3 | tristate |
|---|
| 3 | | - ---help--- |
|---|
| 4 | + help |
|---|
| 4 | 5 | This option is selected by any driver which implements the virtio |
|---|
| 5 | 6 | bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG |
|---|
| 6 | 7 | or CONFIG_S390_GUEST. |
|---|
| 8 | + |
|---|
| 9 | +config ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS |
|---|
| 10 | + bool |
|---|
| 11 | + help |
|---|
| 12 | + This option is selected if the architecture may need to enforce |
|---|
| 13 | + VIRTIO_F_ACCESS_PLATFORM |
|---|
| 7 | 14 | |
|---|
| 8 | 15 | menuconfig VIRTIO_MENU |
|---|
| 9 | 16 | bool "Virtio drivers" |
|---|
| .. | .. |
|---|
| 15 | 22 | tristate "PCI driver for virtio devices" |
|---|
| 16 | 23 | depends on PCI |
|---|
| 17 | 24 | select VIRTIO |
|---|
| 18 | | - ---help--- |
|---|
| 25 | + help |
|---|
| 19 | 26 | This driver provides support for virtio based paravirtual device |
|---|
| 20 | 27 | drivers over PCI. This requires that your VMM has appropriate PCI |
|---|
| 21 | 28 | virtio backends. Most QEMU based VMMs should support these devices |
|---|
| .. | .. |
|---|
| 27 | 34 | bool "Support for legacy virtio draft 0.9.X and older devices" |
|---|
| 28 | 35 | default y |
|---|
| 29 | 36 | depends on VIRTIO_PCI |
|---|
| 30 | | - ---help--- |
|---|
| 37 | + help |
|---|
| 31 | 38 | Virtio PCI Card 0.9.X Draft (circa 2014) and older device support. |
|---|
| 32 | 39 | |
|---|
| 33 | 40 | This option enables building a transitional driver, supporting |
|---|
| .. | .. |
|---|
| 41 | 48 | life will be like in The Future. |
|---|
| 42 | 49 | |
|---|
| 43 | 50 | If unsure, say Y. |
|---|
| 51 | + |
|---|
| 52 | +config VIRTIO_VDPA |
|---|
| 53 | + tristate "vDPA driver for virtio devices" |
|---|
| 54 | + depends on VDPA |
|---|
| 55 | + select VIRTIO |
|---|
| 56 | + help |
|---|
| 57 | + This driver provides support for virtio based paravirtual |
|---|
| 58 | + device driver over vDPA bus. For this to be useful, you need |
|---|
| 59 | + an appropriate vDPA device implementation that operates on a |
|---|
| 60 | + physical device to allow the datapath of virtio to be |
|---|
| 61 | + offloaded to hardware. |
|---|
| 62 | + |
|---|
| 63 | + If unsure, say M. |
|---|
| 44 | 64 | |
|---|
| 45 | 65 | config VIRTIO_PMEM |
|---|
| 46 | 66 | tristate "Support for virtio pmem driver" |
|---|
| .. | .. |
|---|
| 57 | 77 | tristate "Virtio balloon driver" |
|---|
| 58 | 78 | depends on VIRTIO |
|---|
| 59 | 79 | select MEMORY_BALLOON |
|---|
| 60 | | - ---help--- |
|---|
| 80 | + select PAGE_REPORTING |
|---|
| 81 | + help |
|---|
| 61 | 82 | This driver supports increasing and decreasing the amount |
|---|
| 62 | 83 | of memory within a KVM guest. |
|---|
| 84 | + |
|---|
| 85 | + If unsure, say M. |
|---|
| 86 | + |
|---|
| 87 | +config VIRTIO_MEM |
|---|
| 88 | + tristate "Virtio mem driver" |
|---|
| 89 | + default m |
|---|
| 90 | + depends on X86_64 |
|---|
| 91 | + depends on VIRTIO |
|---|
| 92 | + depends on MEMORY_HOTPLUG_SPARSE |
|---|
| 93 | + depends on MEMORY_HOTREMOVE |
|---|
| 94 | + depends on CONTIG_ALLOC |
|---|
| 95 | + help |
|---|
| 96 | + This driver provides access to virtio-mem paravirtualized memory |
|---|
| 97 | + devices, allowing to hotplug and hotunplug memory. |
|---|
| 98 | + |
|---|
| 99 | + This driver was only tested under x86-64, but should theoretically |
|---|
| 100 | + work on all architectures that support memory hotplug and hotremove. |
|---|
| 63 | 101 | |
|---|
| 64 | 102 | If unsure, say M. |
|---|
| 65 | 103 | |
|---|
| .. | .. |
|---|
| 67 | 105 | tristate "Virtio input driver" |
|---|
| 68 | 106 | depends on VIRTIO |
|---|
| 69 | 107 | depends on INPUT |
|---|
| 70 | | - ---help--- |
|---|
| 108 | + help |
|---|
| 71 | 109 | This driver supports virtio input devices such as |
|---|
| 72 | 110 | keyboards, mice and tablets. |
|---|
| 73 | 111 | |
|---|
| 74 | 112 | If unsure, say M. |
|---|
| 75 | 113 | |
|---|
| 76 | | - config VIRTIO_MMIO |
|---|
| 114 | +config VIRTIO_MMIO |
|---|
| 77 | 115 | tristate "Platform bus driver for memory mapped virtio devices" |
|---|
| 78 | 116 | depends on HAS_IOMEM && HAS_DMA |
|---|
| 79 | | - select VIRTIO |
|---|
| 80 | | - ---help--- |
|---|
| 81 | | - This drivers provides support for memory mapped virtio |
|---|
| 117 | + select VIRTIO |
|---|
| 118 | + help |
|---|
| 119 | + This drivers provides support for memory mapped virtio |
|---|
| 82 | 120 | platform device driver. |
|---|
| 83 | 121 | |
|---|
| 84 | 122 | If unsure, say N. |
|---|
| .. | .. |
|---|
| 86 | 124 | config VIRTIO_MMIO_CMDLINE_DEVICES |
|---|
| 87 | 125 | bool "Memory mapped virtio devices parameter parsing" |
|---|
| 88 | 126 | depends on VIRTIO_MMIO |
|---|
| 89 | | - ---help--- |
|---|
| 127 | + help |
|---|
| 90 | 128 | Allow virtio-mmio devices instantiation via the kernel command line |
|---|
| 91 | 129 | or module parameters. Be aware that using incorrect parameters (base |
|---|
| 92 | 130 | address in particular) can crash your system - you have been warned. |
|---|
| .. | .. |
|---|
| 94 | 132 | |
|---|
| 95 | 133 | If unsure, say 'N'. |
|---|
| 96 | 134 | |
|---|
| 135 | +config VIRTIO_DMA_SHARED_BUFFER |
|---|
| 136 | + tristate "Virtio DMA shared buffer support" |
|---|
| 137 | + depends on DMA_SHARED_BUFFER |
|---|
| 138 | + help |
|---|
| 139 | + This option adds a flavor of dma buffers that are backed by |
|---|
| 140 | + virtio resources. |
|---|
| 141 | + |
|---|
| 97 | 142 | endif # VIRTIO_MENU |
|---|