1# Virtio always gets selected by whoever wants it. 2config VIRTIO 3 tristate 4 5# Similarly the virtio ring implementation. 6config VIRTIO_RING 7 tristate 8 depends on VIRTIO 9 10menu "Virtio drivers" 11 12config VIRTIO_PCI 13 tristate "PCI driver for virtio devices (EXPERIMENTAL)" 14 depends on PCI && EXPERIMENTAL 15 select VIRTIO 16 select VIRTIO_RING 17 ---help--- 18 This drivers provides support for virtio based paravirtual device 19 drivers over PCI. This requires that your VMM has appropriate PCI 20 virtio backends. Most QEMU based VMMs should support these devices 21 (like KVM or Xen). 22 23 Currently, the ABI is not considered stable so there is no guarantee 24 that this version of the driver will work with your VMM. 25 26 If unsure, say M. 27 28config VIRTIO_BALLOON 29 tristate "Virtio balloon driver (EXPERIMENTAL)" 30 select VIRTIO 31 select VIRTIO_RING 32 ---help--- 33 This driver supports increasing and decreasing the amount 34 of memory within a KVM guest. 35 36 If unsure, say M. 37 38 config VIRTIO_MMIO 39 tristate "Platform bus driver for memory mapped virtio devices (EXPERIMENTAL)" 40 depends on HAS_IOMEM && EXPERIMENTAL 41 select VIRTIO 42 select VIRTIO_RING 43 ---help--- 44 This drivers provides support for memory mapped virtio 45 platform device driver. 46 47 If unsure, say N. 48 49config VIRTIO_MMIO_CMDLINE_DEVICES 50 bool "Memory mapped virtio devices parameter parsing" 51 depends on VIRTIO_MMIO 52 ---help--- 53 Allow virtio-mmio devices instantiation via the kernel command line 54 or module parameters. Be aware that using incorrect parameters (base 55 address in particular) can crash your system - you have been warned. 56 See Documentation/kernel-parameters.txt for details. 57 58 If unsure, say 'N'. 59 60endmenu 61