| 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859 |
- # Virtio always gets selected by whoever wants it.
- config VIRTIO
- tristate
- # Similarly the virtio ring implementation.
- config VIRTIO_RING
- tristate
- depends on VIRTIO
- menu "Virtio drivers"
- config VIRTIO_PCI
- tristate "PCI driver for virtio devices (EXPERIMENTAL)"
- depends on PCI && EXPERIMENTAL
- select VIRTIO
- select VIRTIO_RING
- ---help---
- This drivers 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).
- Currently, the ABI is not considered stable so there is no guarantee
- that this version of the driver will work with your VMM.
- If unsure, say M.
- config VIRTIO_BALLOON
- tristate "Virtio balloon driver (EXPERIMENTAL)"
- depends on EXPERIMENTAL && VIRTIO
- ---help---
- This driver supports increasing and decreasing the amount
- of memory within a KVM guest.
- If unsure, say M.
- config VIRTIO_MMIO
- tristate "Platform bus driver for memory mapped virtio devices (EXPERIMENTAL)"
- depends on HAS_IOMEM && EXPERIMENTAL
- select VIRTIO
- select VIRTIO_RING
- ---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
|
