| Kconfig (136d9ebff300044865693a57d68fe5905635992a) | Kconfig (30edc14bf39afde24ef7db2de66c91805db80828) |
|---|---|
| 1menu "Xen driver support" 2 depends on XEN 3 4config XEN_BALLOON 5 bool "Xen memory balloon driver" 6 default y 7 help 8 The balloon driver allows the Xen domain to request more memory from 9 the system to expand the domain's memory allocation, or alternatively 10 return unneeded memory to the system. 11 | 1menu "Xen driver support" 2 depends on XEN 3 4config XEN_BALLOON 5 bool "Xen memory balloon driver" 6 default y 7 help 8 The balloon driver allows the Xen domain to request more memory from 9 the system to expand the domain's memory allocation, or alternatively 10 return unneeded memory to the system. 11 |
| 12config XEN_SELFBALLOONING 13 bool "Dynamically self-balloon kernel memory to target" 14 depends on XEN && XEN_BALLOON && CLEANCACHE && SWAP 15 default n 16 help 17 Self-ballooning dynamically balloons available kernel memory driven 18 by the current usage of anonymous memory ("committed AS") and 19 controlled by various sysfs-settable parameters. Configuring 20 FRONTSWAP is highly recommended; if it is not configured, self- 21 ballooning is disabled by default but can be enabled with the 22 'selfballooning' kernel boot parameter. If FRONTSWAP is configured, 23 frontswap-selfshrinking is enabled by default but can be disabled 24 with the 'noselfshrink' kernel boot parameter; and self-ballooning 25 is enabled by default but can be disabled with the 'noselfballooning' 26 kernel boot parameter. Note that systems without a sufficiently 27 large swap device should not enable self-ballooning. 28 | |
| 29config XEN_SCRUB_PAGES 30 bool "Scrub pages before returning them to system" 31 depends on XEN_BALLOON 32 default y 33 help 34 Scrub pages before returning them to the system for reuse by 35 other domains. This makes sure that any confidential data 36 is not accidentally visible to other domains. Is it more --- 80 unchanged lines hidden (view full) --- 117 domain. As a consequence this driver is required to run any Xen PV 118 frontend on Xen HVM. 119 120config SWIOTLB_XEN 121 def_bool y 122 depends on PCI 123 select SWIOTLB 124 | 12config XEN_SCRUB_PAGES 13 bool "Scrub pages before returning them to system" 14 depends on XEN_BALLOON 15 default y 16 help 17 Scrub pages before returning them to the system for reuse by 18 other domains. This makes sure that any confidential data 19 is not accidentally visible to other domains. Is it more --- 80 unchanged lines hidden (view full) --- 100 domain. As a consequence this driver is required to run any Xen PV 101 frontend on Xen HVM. 102 103config SWIOTLB_XEN 104 def_bool y 105 depends on PCI 106 select SWIOTLB 107 |
| 125config XEN_TMEM 126 bool 127 default y if (CLEANCACHE || FRONTSWAP) | 108config XEN_PCIDEV_BACKEND 109 tristate "Xen PCI-device backend driver" 110 depends on PCI && X86 && XEN 111 depends on XEN_BACKEND |
| 128 help | 112 help |
| 129 Shim to interface in-kernel Transcendent Memory hooks 130 (e.g. cleancache and frontswap) to Xen tmem hypercalls. | 113 The PCI device backend driver allows the kernel to export arbitrary 114 PCI devices to other guests. If you select this to be a module, you 115 will need to make sure no other driver has bound to the device(s) 116 you want to make visible to other guests. |
| 131 | 117 |
| 118choice 119 prompt "PCI Backend Mode" 120 depends on XEN_PCIDEV_BACKEND 121 122config XEN_PCIDEV_BACKEND_VPCI 123 bool "Virtual PCI" 124 help 125 This PCI Backend hides the true PCI topology and makes the frontend 126 think there is a single PCI bus with only the exported devices on it. 127 For example, a device at 03:05.0 will be re-assigned to 00:00.0. A 128 second device at 02:1a.1 will be re-assigned to 00:01.1. 129 130config XEN_PCIDEV_BACKEND_PASS 131 bool "Passthrough" 132 help 133 This PCI Backend provides a real view of the PCI topology to the 134 frontend (for example, a device at 06:01.b will still appear at 135 06:01.b to the frontend). This is similar to how Xen 2.0.x exposed 136 PCI devices to its driver domains. This may be required for drivers 137 which depend on finding their hardward in certain bus/slot 138 locations. 139 140endchoice 141 142config XEN_PCIDEV_BE_DEBUG 143 bool "Xen PCI Backend Debugging" 144 depends on XEN_PCIDEV_BACKEND 145 default n 146 help 147 Allows to observe all of the traffic from the frontend/backend 148 when reading and writting to the configuration registers. 149 If in doubt, say no. 150 |
|
| 132endmenu | 151endmenu |