]> git.proxmox.com Git - mirror_ubuntu-hirsute-kernel.git/blame - drivers/virtio/Kconfig
Merge tag 'char-misc-5.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh...
[mirror_ubuntu-hirsute-kernel.git] / drivers / virtio / Kconfig
CommitLineData
ec8f24b7 1# SPDX-License-Identifier: GPL-2.0-only
ec3d41c4 2config VIRTIO
c6fd4701 3 tristate
387daf17
RR
4 ---help---
5 This option is selected by any driver which implements the virtio
ecda85e7
JG
6 bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG
7 or CONFIG_S390_GUEST.
0a8a69dd 8
7b95fec6
VL
9menuconfig VIRTIO_MENU
10 bool "Virtio drivers"
11 default y
12
13if VIRTIO_MENU
e7254219 14
3343660d 15config VIRTIO_PCI
d72c5a8c
KC
16 tristate "PCI driver for virtio devices"
17 depends on PCI
3343660d 18 select VIRTIO
3343660d 19 ---help---
b2a6d51d 20 This driver provides support for virtio based paravirtual device
3343660d
AL
21 drivers over PCI. This requires that your VMM has appropriate PCI
22 virtio backends. Most QEMU based VMMs should support these devices
23 (like KVM or Xen).
24
3343660d
AL
25 If unsure, say M.
26
46506da5
MT
27config VIRTIO_PCI_LEGACY
28 bool "Support for legacy virtio draft 0.9.X and older devices"
29 default y
30 depends on VIRTIO_PCI
31 ---help---
32 Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
33
34 This option enables building a transitional driver, supporting
35 both devices conforming to Virtio 1 specification, and legacy devices.
36 If disabled, you get a slightly smaller, non-transitional driver,
37 with no legacy compatibility.
38
39 So look out into your driveway. Do you have a flying car? If
40 so, you can happily disable this option and virtio will not
41 break. Otherwise, leave it set. Unless you're testing what
42 life will be like in The Future.
43
44 If unsure, say Y.
45
6e84200c
PG
46config VIRTIO_PMEM
47 tristate "Support for virtio pmem driver"
48 depends on VIRTIO
49 depends on LIBNVDIMM
50 help
51 This driver provides access to virtio-pmem devices, storage devices
52 that are mapped into the physical address space - similar to NVDIMMs
53 - with a virtio-based flushing interface.
54
55 If unsure, say Y.
56
6b35e407 57config VIRTIO_BALLOON
7a23eb28
RR
58 tristate "Virtio balloon driver"
59 depends on VIRTIO
09316c09 60 select MEMORY_BALLOON
6b35e407
RR
61 ---help---
62 This driver supports increasing and decreasing the amount
63 of memory within a KVM guest.
64
65 If unsure, say M.
66
271c8651
GH
67config VIRTIO_INPUT
68 tristate "Virtio input driver"
69 depends on VIRTIO
70 depends on INPUT
71 ---help---
72 This driver supports virtio input devices such as
73 keyboards, mice and tablets.
74
75 If unsure, say M.
76
6166e533 77config VIRTIO_MMIO
d72c5a8c 78 tristate "Platform bus driver for memory mapped virtio devices"
780bc790 79 depends on HAS_IOMEM && HAS_DMA
6166e533
FC
80 select VIRTIO
81 ---help---
82 This drivers provides support for memory mapped virtio
edfd52e6
PM
83 platform device driver.
84
85 If unsure, say N.
86
81a054ce
PM
87config VIRTIO_MMIO_CMDLINE_DEVICES
88 bool "Memory mapped virtio devices parameter parsing"
89 depends on VIRTIO_MMIO
90 ---help---
91 Allow virtio-mmio devices instantiation via the kernel command line
92 or module parameters. Be aware that using incorrect parameters (base
93 address in particular) can crash your system - you have been warned.
8c27ceff 94 See Documentation/admin-guide/kernel-parameters.rst for details.
81a054ce
PM
95
96 If unsure, say 'N'.
97
7b95fec6 98endif # VIRTIO_MENU