mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-21 11:44:01 +08:00
780bc7903a
virtio_ring currently sends the device (usually a hypervisor) physical addresses of its I/O buffers. This is okay when DMA addresses and physical addresses are the same thing, but this isn't always the case. For example, this never works on Xen guests, and it is likely to fail if a physical "virtio" device ever ends up behind an IOMMU or swiotlb. The immediate use case for me is to enable virtio on Xen guests. For that to work, we need vring to support DMA address translation as well as a corresponding change to virtio_pci or to another driver. Signed-off-by: Andy Lutomirski <luto@kernel.org> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
83 lines
2.4 KiB
Plaintext
83 lines
2.4 KiB
Plaintext
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_LGUEST,
|
|
CONFIG_RPMSG or CONFIG_S390_GUEST.
|
|
|
|
menu "Virtio drivers"
|
|
|
|
config VIRTIO_PCI
|
|
tristate "PCI driver for virtio devices"
|
|
depends on PCI
|
|
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
|
|
---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_BALLOON
|
|
tristate "Virtio balloon driver"
|
|
depends on VIRTIO
|
|
select MEMORY_BALLOON
|
|
---help---
|
|
This driver supports increasing and decreasing the amount
|
|
of memory within a KVM guest.
|
|
|
|
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/kernel-parameters.txt for details.
|
|
|
|
If unsure, say 'N'.
|
|
|
|
endmenu
|