[linux-block.git] / drivers / virtio / Kconfig

# SPDX-License-Identifier: GPL-2.0-only
config VIRTIO
	tristate
	help
	  This option is selected by any driver which implements the virtio
	  bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG
	  or CONFIG_S390_GUEST.

config VIRTIO_PCI_LIB
	tristate
	help
	  Modern PCI device implementation. This module implements the
	  basic probe and control for devices which are based on modern
	  PCI device with possible vendor specific extensions. Any
	  module that selects this module must depend on PCI.

config VIRTIO_PCI_LIB_LEGACY
	tristate
	help
	  Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
	  implementation.
	  This module implements the basic probe and control for devices
	  which are based on legacy PCI device. Any module that selects this
	  module must depend on PCI.

menuconfig VIRTIO_MENU
	bool "Virtio drivers"
	default y

if VIRTIO_MENU

config VIRTIO_PCI
	tristate "PCI driver for virtio devices"
	depends on PCI
	select VIRTIO_PCI_LIB
	select VIRTIO
	help
	  This driver provides support for virtio based paravirtual device
	  drivers over PCI.  This requires that your VMM has appropriate PCI
	  virtio backends.  Most QEMU based VMMs should support these devices
	  (like KVM or Xen).

	  If unsure, say M.

config VIRTIO_PCI_LEGACY
	bool "Support for legacy virtio draft 0.9.X and older devices"
	default y
	depends on VIRTIO_PCI
	select VIRTIO_PCI_LIB_LEGACY
	help
          Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.

	  This option enables building a transitional driver, supporting
	  both devices conforming to Virtio 1 specification, and legacy devices.
	  If disabled, you get a slightly smaller, non-transitional driver,
	  with no legacy compatibility.

          So look out into your driveway.  Do you have a flying car?  If
          so, you can happily disable this option and virtio will not
          break.  Otherwise, leave it set.  Unless you're testing what
          life will be like in The Future.

	  If unsure, say Y.

config VIRTIO_VDPA
	tristate "vDPA driver for virtio devices"
	depends on VDPA
	select VIRTIO
	help
	  This driver provides support for virtio based paravirtual
	  device driver over vDPA bus. For this to be useful, you need
	  an appropriate vDPA device implementation that operates on a
	  physical device to allow the datapath of virtio to be
	  offloaded to hardware.

	  If unsure, say M.

config VIRTIO_PMEM
	tristate "Support for virtio pmem driver"
	depends on VIRTIO
	depends on LIBNVDIMM
	help
	  This driver provides access to virtio-pmem devices, storage devices
	  that are mapped into the physical address space - similar to NVDIMMs
	   - with a virtio-based flushing interface.

	  If unsure, say Y.

config VIRTIO_BALLOON
	tristate "Virtio balloon driver"
	depends on VIRTIO
	select MEMORY_BALLOON
	select PAGE_REPORTING
	help
	 This driver supports increasing and decreasing the amount
	 of memory within a KVM guest.

	 If unsure, say M.

config VIRTIO_MEM
	tristate "Virtio mem driver"
	depends on X86_64 || ARM64
	depends on VIRTIO
	depends on MEMORY_HOTPLUG
	depends on MEMORY_HOTREMOVE
	depends on CONTIG_ALLOC
	depends on EXCLUSIVE_SYSTEM_RAM
	help
	 This driver provides access to virtio-mem paravirtualized memory
	 devices, allowing to hotplug and hotunplug memory.

	 This driver was only tested under x86-64 and arm64, but should
	 theoretically work on all architectures that support memory hotplug
	 and hotremove.

	 If unsure, say M.

config VIRTIO_INPUT
	tristate "Virtio input driver"
	depends on VIRTIO
	depends on INPUT
	help
	 This driver supports virtio input devices such as
	 keyboards, mice and tablets.

	 If unsure, say M.

config VIRTIO_MMIO
	tristate "Platform bus driver for memory mapped virtio devices"
	depends on HAS_IOMEM && HAS_DMA
	select VIRTIO
	help
	 This drivers provides support for memory mapped virtio
	 platform device driver.

 	 If unsure, say N.

config VIRTIO_MMIO_CMDLINE_DEVICES
	bool "Memory mapped virtio devices parameter parsing"
	depends on VIRTIO_MMIO
	help
	 Allow virtio-mmio devices instantiation via the kernel command line
	 or module parameters. Be aware that using incorrect parameters (base
	 address in particular) can crash your system - you have been warned.
	 See Documentation/admin-guide/kernel-parameters.rst for details.

	 If unsure, say 'N'.

config VIRTIO_DMA_SHARED_BUFFER
	tristate
	depends on DMA_SHARED_BUFFER
	help
	 This option adds a flavor of dma buffers that are backed by
	 virtio resources.

endif # VIRTIO_MENU
Commit	Line	Data
ec8f24b7	1	# SPDX-License-Identifier: GPL-2.0-only
ec3d41c4	2	config VIRTIO
c6fd4701	3	tristate
a7f7f624	4	help
387daf17	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
ecda85e7 JG	7	or CONFIG_S390_GUEST.
0a8a69dd	8
fd502729 JW	9	config VIRTIO_PCI_LIB
	10	tristate
	11	help
	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.
	16
d89c8169 WZ	17	config VIRTIO_PCI_LIB_LEGACY
	18	tristate
	19	help
	20	Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
	21	implementation.
	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.
	25
7b95fec6 VL	26	menuconfig VIRTIO_MENU
	27	bool "Virtio drivers"
	28	default y
	29
	30	if VIRTIO_MENU
e7254219	31
3343660d	32	config VIRTIO_PCI
d72c5a8c KC	33	tristate "PCI driver for virtio devices"
d72c5a8c KC	34	depends on PCI
fd502729	35	select VIRTIO_PCI_LIB
3343660d	36	select VIRTIO
a7f7f624	37	help
b2a6d51d	38	This driver provides support for virtio based paravirtual device
3343660d AL	39	drivers over PCI. This requires that your VMM has appropriate PCI
	40	virtio backends. Most QEMU based VMMs should support these devices
	41	(like KVM or Xen).
	42
3343660d AL	43	If unsure, say M.
3343660d AL	44
46506da5 MT	45	config VIRTIO_PCI_LEGACY
	46	bool "Support for legacy virtio draft 0.9.X and older devices"
	47	default y
	48	depends on VIRTIO_PCI
d89c8169	49	select VIRTIO_PCI_LIB_LEGACY
a7f7f624	50	help
46506da5 MT	51	Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
	52
	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.
	57
	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.
	62
	63	If unsure, say Y.
	64
c043b4a8 JW	65	config VIRTIO_VDPA
c043b4a8 JW	66	tristate "vDPA driver for virtio devices"
58ad1372	67	depends on VDPA
c043b4a8 JW	68	select VIRTIO
	69	help
	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.
	75
	76	If unsure, say M.
	77
6e84200c PG	78	config VIRTIO_PMEM
	79	tristate "Support for virtio pmem driver"
	80	depends on VIRTIO
	81	depends on LIBNVDIMM
	82	help
	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.
	86
	87	If unsure, say Y.
	88
6b35e407	89	config VIRTIO_BALLOON
7a23eb28 RR	90	tristate "Virtio balloon driver"
7a23eb28 RR	91	depends on VIRTIO
09316c09	92	select MEMORY_BALLOON
b0c504f1	93	select PAGE_REPORTING
a7f7f624	94	help
6b35e407 RR	95	This driver supports increasing and decreasing the amount
	96	of memory within a KVM guest.
	97
	98	If unsure, say M.
	99
5f1f79bb DH	100	config VIRTIO_MEM
5f1f79bb DH	101	tristate "Virtio mem driver"
6f4abbaa	102	depends on X86_64 \|\| ARM64
5f1f79bb	103	depends on VIRTIO
50f9481e	104	depends on MEMORY_HOTPLUG
5f1f79bb	105	depends on MEMORY_HOTREMOVE
a96b0d06	106	depends on CONTIG_ALLOC
2128f4e2	107	depends on EXCLUSIVE_SYSTEM_RAM
5f1f79bb DH	108	help
	109	This driver provides access to virtio-mem paravirtualized memory
	110	devices, allowing to hotplug and hotunplug memory.
	111
6f4abbaa GS	112	This driver was only tested under x86-64 and arm64, but should
	113	theoretically work on all architectures that support memory hotplug
	114	and hotremove.
5f1f79bb DH	115
	116	If unsure, say M.
	117
271c8651 GH	118	config VIRTIO_INPUT
	119	tristate "Virtio input driver"
	120	depends on VIRTIO
	121	depends on INPUT
a7f7f624	122	help
271c8651 GH	123	This driver supports virtio input devices such as
	124	keyboards, mice and tablets.
	125
	126	If unsure, say M.
	127
6166e533	128	config VIRTIO_MMIO
d72c5a8c	129	tristate "Platform bus driver for memory mapped virtio devices"
780bc790	130	depends on HAS_IOMEM && HAS_DMA
6166e533	131	select VIRTIO
a7f7f624	132	help
6166e533	133	This drivers provides support for memory mapped virtio
edfd52e6 PM	134	platform device driver.
	135
	136	If unsure, say N.
	137
81a054ce PM	138	config VIRTIO_MMIO_CMDLINE_DEVICES
	139	bool "Memory mapped virtio devices parameter parsing"
	140	depends on VIRTIO_MMIO
a7f7f624	141	help
81a054ce PM	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.
8c27ceff	145	See Documentation/admin-guide/kernel-parameters.rst for details.
81a054ce PM	146
	147	If unsure, say 'N'.
	148
9fe2f897 DS	149	config VIRTIO_DMA_SHARED_BUFFER
	150	tristate
	151	depends on DMA_SHARED_BUFFER
	152	help
	153	This option adds a flavor of dma buffers that are backed by
	154	virtio resources.
	155
7b95fec6	156	endif # VIRTIO_MENU