[linux-2.6-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 ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS
	bool
	help
	  This option is selected if the architecture may need to enforce
	  VIRTIO_F_ACCESS_PLATFORM

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"
	default m
	depends on X86_64
	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, 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
0afa15e1 PM	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
	14
fd502729 JW	15	config VIRTIO_PCI_LIB
	16	tristate
	17	help
	18	Modern PCI device implementation. This module implements the
	19	basic probe and control for devices which are based on modern
	20	PCI device with possible vendor specific extensions. Any
	21	module that selects this module must depend on PCI.
	22
d89c8169 WZ	23	config VIRTIO_PCI_LIB_LEGACY
	24	tristate
	25	help
	26	Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
	27	implementation.
	28	This module implements the basic probe and control for devices
	29	which are based on legacy PCI device. Any module that selects this
	30	module must depend on PCI.
	31
7b95fec6 VL	32	menuconfig VIRTIO_MENU
	33	bool "Virtio drivers"
	34	default y
	35
	36	if VIRTIO_MENU
e7254219	37
3343660d	38	config VIRTIO_PCI
d72c5a8c KC	39	tristate "PCI driver for virtio devices"
d72c5a8c KC	40	depends on PCI
fd502729	41	select VIRTIO_PCI_LIB
3343660d	42	select VIRTIO
a7f7f624	43	help
b2a6d51d	44	This driver provides support for virtio based paravirtual device
3343660d AL	45	drivers over PCI. This requires that your VMM has appropriate PCI
	46	virtio backends. Most QEMU based VMMs should support these devices
	47	(like KVM or Xen).
	48
3343660d AL	49	If unsure, say M.
3343660d AL	50
46506da5 MT	51	config VIRTIO_PCI_LEGACY
	52	bool "Support for legacy virtio draft 0.9.X and older devices"
	53	default y
	54	depends on VIRTIO_PCI
d89c8169	55	select VIRTIO_PCI_LIB_LEGACY
a7f7f624	56	help
46506da5 MT	57	Virtio PCI Card 0.9.X Draft (circa 2014) and older device support.
	58
	59	This option enables building a transitional driver, supporting
	60	both devices conforming to Virtio 1 specification, and legacy devices.
	61	If disabled, you get a slightly smaller, non-transitional driver,
	62	with no legacy compatibility.
	63
	64	So look out into your driveway. Do you have a flying car? If
	65	so, you can happily disable this option and virtio will not
	66	break. Otherwise, leave it set. Unless you're testing what
	67	life will be like in The Future.
	68
	69	If unsure, say Y.
	70
c043b4a8 JW	71	config VIRTIO_VDPA
c043b4a8 JW	72	tristate "vDPA driver for virtio devices"
58ad1372	73	depends on VDPA
c043b4a8 JW	74	select VIRTIO
	75	help
	76	This driver provides support for virtio based paravirtual
	77	device driver over vDPA bus. For this to be useful, you need
	78	an appropriate vDPA device implementation that operates on a
	79	physical device to allow the datapath of virtio to be
	80	offloaded to hardware.
	81
	82	If unsure, say M.
	83
6e84200c PG	84	config VIRTIO_PMEM
	85	tristate "Support for virtio pmem driver"
	86	depends on VIRTIO
	87	depends on LIBNVDIMM
	88	help
	89	This driver provides access to virtio-pmem devices, storage devices
	90	that are mapped into the physical address space - similar to NVDIMMs
	91	- with a virtio-based flushing interface.
	92
	93	If unsure, say Y.
	94
6b35e407	95	config VIRTIO_BALLOON
7a23eb28 RR	96	tristate "Virtio balloon driver"
7a23eb28 RR	97	depends on VIRTIO
09316c09	98	select MEMORY_BALLOON
b0c504f1	99	select PAGE_REPORTING
a7f7f624	100	help
6b35e407 RR	101	This driver supports increasing and decreasing the amount
	102	of memory within a KVM guest.
	103
	104	If unsure, say M.
	105
5f1f79bb DH	106	config VIRTIO_MEM
	107	tristate "Virtio mem driver"
	108	default m
	109	depends on X86_64
	110	depends on VIRTIO
50f9481e	111	depends on MEMORY_HOTPLUG
5f1f79bb	112	depends on MEMORY_HOTREMOVE
a96b0d06	113	depends on CONTIG_ALLOC
2128f4e2	114	depends on EXCLUSIVE_SYSTEM_RAM
5f1f79bb DH	115	help
	116	This driver provides access to virtio-mem paravirtualized memory
	117	devices, allowing to hotplug and hotunplug memory.
	118
	119	This driver was only tested under x86-64, but should theoretically
	120	work on all architectures that support memory hotplug and hotremove.
	121
	122	If unsure, say M.
	123
271c8651 GH	124	config VIRTIO_INPUT
	125	tristate "Virtio input driver"
	126	depends on VIRTIO
	127	depends on INPUT
a7f7f624	128	help
271c8651 GH	129	This driver supports virtio input devices such as
	130	keyboards, mice and tablets.
	131
	132	If unsure, say M.
	133
6166e533	134	config VIRTIO_MMIO
d72c5a8c	135	tristate "Platform bus driver for memory mapped virtio devices"
780bc790	136	depends on HAS_IOMEM && HAS_DMA
6166e533	137	select VIRTIO
a7f7f624	138	help
6166e533	139	This drivers provides support for memory mapped virtio
edfd52e6 PM	140	platform device driver.
	141
	142	If unsure, say N.
	143
81a054ce PM	144	config VIRTIO_MMIO_CMDLINE_DEVICES
	145	bool "Memory mapped virtio devices parameter parsing"
	146	depends on VIRTIO_MMIO
a7f7f624	147	help
81a054ce PM	148	Allow virtio-mmio devices instantiation via the kernel command line
	149	or module parameters. Be aware that using incorrect parameters (base
	150	address in particular) can crash your system - you have been warned.
8c27ceff	151	See Documentation/admin-guide/kernel-parameters.rst for details.
81a054ce PM	152
	153	If unsure, say 'N'.
	154
9fe2f897 DS	155	config VIRTIO_DMA_SHARED_BUFFER
	156	tristate
	157	depends on DMA_SHARED_BUFFER
	158	help
	159	This option adds a flavor of dma buffers that are backed by
	160	virtio resources.
	161
7b95fec6	162	endif # VIRTIO_MENU