Kconfig 11.6 KB
Newer Older
Randy Dunlap's avatar
Randy Dunlap committed
1 2 3
menu "Xen driver support"
	depends on XEN

4 5 6 7 8 9 10 11
config XEN_BALLOON
	bool "Xen memory balloon driver"
	default y
	help
	  The balloon driver allows the Xen domain to request more memory from
	  the system to expand the domain's memory allocation, or alternatively
	  return unneeded memory to the system.

12 13
config XEN_SELFBALLOONING
	bool "Dynamically self-balloon kernel memory to target"
14
	depends on XEN && XEN_BALLOON && CLEANCACHE && SWAP && XEN_TMEM
15 16 17 18 19
	help
	  Self-ballooning dynamically balloons available kernel memory driven
	  by the current usage of anonymous memory ("committed AS") and
	  controlled by various sysfs-settable parameters.  Configuring
	  FRONTSWAP is highly recommended; if it is not configured, self-
20
	  ballooning is disabled by default. If FRONTSWAP is configured,
21
	  frontswap-selfshrinking is enabled by default but can be disabled
22
	  with the 'tmem.selfshrink=0' kernel boot parameter; and self-ballooning
23
	  is enabled by default but can be disabled with the 'tmem.selfballooning=0'
24 25
	  kernel boot parameter.  Note that systems without a sufficiently
	  large swap device should not enable self-ballooning.
26

27 28 29 30 31 32 33 34 35 36 37
config XEN_BALLOON_MEMORY_HOTPLUG
	bool "Memory hotplug support for Xen balloon driver"
	depends on XEN_BALLOON && MEMORY_HOTPLUG
	help
	  Memory hotplug support for Xen balloon driver allows expanding memory
	  available for the system above limit declared at system startup.
	  It is very useful on critical systems which require long
	  run without rebooting.

	  Memory could be hotplugged in following steps:

38 39 40 41 42
	    1) target domain: ensure that memory auto online policy is in
	       effect by checking /sys/devices/system/memory/auto_online_blocks
	       file (should be 'online').

	    2) control domain: xl mem-max <target-domain> <maxmem>
43 44
	       where <maxmem> is >= requested memory size,

45
	    3) control domain: xl mem-set <target-domain> <memory>
46 47 48
	       where <memory> is requested memory size; alternatively memory
	       could be added by writing proper value to
	       /sys/devices/system/xen_memory/xen_memory0/target or
49 50
	       /sys/devices/system/xen_memory/xen_memory0/target_kb on the
	       target domain.
51

52 53 54
	  Alternatively, if memory auto onlining was not requested at step 1
	  the newly added memory can be manually onlined in the target domain
	  by doing the following:
55

56 57
		for i in /sys/devices/system/memory/memory*/state; do \
		  [ "`cat "$i"`" = offline ] && echo online > "$i"; done
58

59
	  or by adding the following line to udev rules:
60

61
	  SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /sys$devpath/state'"
62

63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
config XEN_BALLOON_MEMORY_HOTPLUG_LIMIT
	int "Hotplugged memory limit (in GiB) for a PV guest"
	default 512 if X86_64
	default 4 if X86_32
	range 0 64 if X86_32
	depends on XEN_HAVE_PVMMU
	depends on XEN_BALLOON_MEMORY_HOTPLUG
	help
	  Maxmium amount of memory (in GiB) that a PV guest can be
	  expanded to when using memory hotplug.

	  A PV guest can have more memory than this limit if is
	  started with a larger maximum.

	  This value is used to allocate enough space in internal
	  tables needed for physical memory administration.

80 81
config XEN_SCRUB_PAGES_DEFAULT
	bool "Scrub pages before returning them to system by default"
82 83 84 85 86
	depends on XEN_BALLOON
	default y
	help
	  Scrub pages before returning them to the system for reuse by
	  other domains.  This makes sure that any confidential data
87
	  is not accidentally visible to other domains.  It is more
88 89 90 91 92
	  secure, but slightly less efficient. This can be controlled with
	  xen_scrub_pages=0 parameter and
	  /sys/devices/system/xen_memory/xen_memory0/scrub_pages.
	  This option only sets the default value.

93
	  If in doubt, say yes.
94

95 96 97 98
config XEN_DEV_EVTCHN
	tristate "Xen /dev/xen/evtchn device"
	default y
	help
99
	  The evtchn driver allows a userspace process to trigger event
100 101 102 103
	  channels and to receive notification of an event channel
	  firing.
	  If in doubt, say yes.

104
config XEN_BACKEND
105
	bool "Backend driver support"
106
	default XEN_DOM0
107 108 109 110
	help
	  Support for backend device drivers that provide I/O services
	  to other virtual machines.

111 112
config XENFS
	tristate "Xen filesystem"
113
	select XEN_PRIVCMD
114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129
	default y
	help
	  The xen filesystem provides a way for domains to share
	  information with each other and with the hypervisor.
	  For example, by reading and writing the "xenbus" file, guests
	  may pass arbitrary information to the initial domain.
	  If in doubt, say yes.

config XEN_COMPAT_XENFS
       bool "Create compatibility mount point /proc/xen"
       depends on XENFS
       default y
       help
         The old xenstore userspace tools expect to find "xenbus"
         under /proc/xen, but "xenbus" is now found at the root of the
         xenfs filesystem.  Selecting this causes the kernel to create
130
         the compatibility mount point /proc/xen if it is running on
131 132 133
         a xen platform.
         If in doubt, say yes.

134 135
config XEN_SYS_HYPERVISOR
       bool "Create xen entries under /sys/hypervisor"
Randy Dunlap's avatar
Randy Dunlap committed
136
       depends on SYSFS
137 138 139 140 141 142
       select SYS_HYPERVISOR
       default y
       help
         Create entries under /sys/hypervisor describing the Xen
	 hypervisor environment.  When running native or in another
	 virtual environment, /sys/hypervisor will still be present,
Randy Dunlap's avatar
Randy Dunlap committed
143 144
	 but will have no xen contents.

145
config XEN_XENBUS_FRONTEND
146 147
	tristate

148 149 150
config XEN_GNTDEV
	tristate "userspace grant access device driver"
	depends on XEN
151
	default m
152 153 154
	select MMU_NOTIFIER
	help
	  Allows userspace processes to use grants.
155

156 157 158 159 160 161 162 163 164 165
config XEN_GNTDEV_DMABUF
	bool "Add support for dma-buf grant access device driver extension"
	depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC && DMA_SHARED_BUFFER
	help
	  Allows userspace processes and kernel modules to use Xen backed
	  dma-buf implementation. With this extension grant references to
	  the pages of an imported dma-buf can be exported for other domain
	  use and grant references coming from a foreign domain can be
	  converted into a local dma-buf for local export.

166 167 168
config XEN_GRANT_DEV_ALLOC
	tristate "User-space grant reference allocator driver"
	depends on XEN
169
	default m
170 171 172 173 174
	help
	  Allows userspace processes to create pages with access granted
	  to other domains. This can be used to implement frontend drivers
	  or as part of an inter-domain shared memory channel.

175 176 177 178 179 180 181 182 183 184 185 186 187 188
config XEN_GRANT_DMA_ALLOC
	bool "Allow allocating DMA capable buffers with grant reference module"
	depends on XEN && HAS_DMA
	help
	  Extends grant table module API to allow allocating DMA capable
	  buffers and mapping foreign grant references on top of it.
	  The resulting buffer is similar to one allocated by the balloon
	  driver in that proper memory reservation is made by
	  ({increase|decrease}_reservation and VA mappings are updated if
	  needed).
	  This is useful for sharing foreign buffers with HW drivers which
	  cannot work with scattered buffers provided by the balloon driver,
	  but require DMAable memory instead.

189 190
config SWIOTLB_XEN
	def_bool y
191
	select SWIOTLB
192

193
config XEN_TMEM
194
	tristate
195
	depends on !ARM && !ARM64
196
	default m if (CLEANCACHE || FRONTSWAP)
197 198 199 200
	help
	  Shim to interface in-kernel Transcendent Memory hooks
	  (e.g. cleancache and frontswap) to Xen tmem hypercalls.

201 202 203 204
config XEN_PCIDEV_BACKEND
	tristate "Xen PCI-device backend driver"
	depends on PCI && X86 && XEN
	depends on XEN_BACKEND
205
	default m
206 207 208 209 210 211
	help
	  The PCI device backend driver allows the kernel to export arbitrary
	  PCI devices to other guests. If you select this to be a module, you
	  will need to make sure no other driver has bound to the device(s)
	  you want to make visible to other guests.

212 213 214 215
	  The parameter "passthrough" allows you specify how you want the PCI
	  devices to appear in the guest. You can choose the default (0) where
	  PCI topology starts at 00.00.0, or (1) for passthrough if you want
	  the PCI devices topology appear the same as in the host.
216

217 218 219 220
	  The "hide" parameter (only applicable if backend driver is compiled
	  into the kernel) allows you to bind the PCI devices to this module
	  from the default device drivers. The argument is the list of PCI BDFs:
	  xen-pciback.hide=(03:00.0)(04:00.0)
221

222
	  If in doubt, say m.
223

224 225 226 227 228 229 230 231 232 233
config XEN_PVCALLS_FRONTEND
	tristate "XEN PV Calls frontend driver"
	depends on INET && XEN
	select XEN_XENBUS_FRONTEND
	help
	  Experimental frontend for the Xen PV Calls protocol
	  (https://xenbits.xen.org/docs/unstable/misc/pvcalls.html). It
	  sends a small set of POSIX calls to the backend, which
	  implements them.

234 235 236 237 238 239 240 241 242 243 244
config XEN_PVCALLS_BACKEND
	bool "XEN PV Calls backend driver"
	depends on INET && XEN && XEN_BACKEND
	help
	  Experimental backend for the Xen PV Calls protocol
	  (https://xenbits.xen.org/docs/unstable/misc/pvcalls.html). It
	  allows PV Calls frontends to send POSIX calls to the backend,
	  which implements them.

	  If in doubt, say n.

245 246 247 248 249 250 251 252 253
config XEN_SCSI_BACKEND
	tristate "XEN SCSI backend driver"
	depends on XEN && XEN_BACKEND && TARGET_CORE
	help
	  The SCSI backend driver allows the kernel to export its SCSI Devices
	  to other guests via a high-performance shared-memory interface.
	  Only needed for systems running as XEN driver domains (e.g. Dom0) and
	  if guests need generic access to SCSI devices.

254 255 256 257 258
config XEN_PRIVCMD
	tristate
	depends on XEN
	default m

259 260
config XEN_STUB
	bool "Xen stub drivers"
261
	depends on XEN && X86_64 && BROKEN
262 263 264 265 266 267 268
	help
	  Allow kernel to install stub drivers, to reserve space for Xen drivers,
	  i.e. memory hotplug and cpu hotplug, and to block native drivers loaded,
	  so that real Xen drivers can be modular.

	  To enable Xen features like cpu and memory hotplug, select Y here.

269 270 271 272 273 274 275 276 277 278
config XEN_ACPI_HOTPLUG_MEMORY
	tristate "Xen ACPI memory hotplug"
	depends on XEN_DOM0 && XEN_STUB && ACPI
	help
	  This is Xen ACPI memory hotplug.

	  Currently Xen only support ACPI memory hot-add. If you want
	  to hot-add memory at runtime (the hot-added memory cannot be
	  removed until machine stop), select Y/M here, otherwise select N.

Liu Jinsong's avatar
Liu Jinsong committed
279 280 281 282 283 284 285 286 287 288 289
config XEN_ACPI_HOTPLUG_CPU
	tristate "Xen ACPI cpu hotplug"
	depends on XEN_DOM0 && XEN_STUB && ACPI
	select ACPI_CONTAINER
	help
	  Xen ACPI cpu enumerating and hotplugging

	  For hotplugging, currently Xen only support ACPI cpu hotadd.
	  If you want to hotadd cpu at runtime (the hotadded cpu cannot
	  be removed until machine stop), select Y/M here.

290 291
config XEN_ACPI_PROCESSOR
	tristate "Xen ACPI processor"
292
	depends on XEN && XEN_DOM0 && X86 && ACPI_PROCESSOR && CPU_FREQ
293
	default m
294
	help
295 296 297 298 299
          This ACPI processor uploads Power Management information to the Xen
	  hypervisor.

	  To do that the driver parses the Power Management data and uploads
	  said information to the Xen hypervisor. Then the Xen hypervisor can
300
	  select the proper Cx and Pxx states. It also registers itself as the
301 302 303 304 305 306
	  SMM so that other drivers (such as ACPI cpufreq scaling driver) will
	  not load.

          To compile this driver as a module, choose M here: the module will be
	  called xen_acpi_processor  If you do not know what to choose, select
	  M here. If the CPUFREQ drivers are built in, select Y here.
307

308 309 310 311 312 313 314
config XEN_MCE_LOG
	bool "Xen platform mcelog"
	depends on XEN_DOM0 && X86_64 && X86_MCE
	help
	  Allow kernel fetching MCE error from Xen platform and
	  converting it into Linux mcelog format for mcelog tools

315 316 317
config XEN_HAVE_PVMMU
       bool

318 319
config XEN_EFI
	def_bool y
320
	depends on (ARM || ARM64 || X86_64) && EFI
321

322 323 324 325 326 327
config XEN_AUTO_XLATE
	def_bool y
	depends on ARM || ARM64 || XEN_PVHVM
	help
	  Support for auto-translated physmap guests.

328 329 330 331
config XEN_ACPI
	def_bool y
	depends on X86 && ACPI

Boris Ostrovsky's avatar
Boris Ostrovsky committed
332 333 334 335 336 337 338 339
config XEN_SYMS
       bool "Xen symbols"
       depends on X86 && XEN_DOM0 && XENFS
       default y if KALLSYMS
       help
          Exports hypervisor symbols (along with their types and addresses) via
          /proc/xen/xensyms file, similar to /proc/kallsyms

340 341 342
config XEN_HAVE_VPMU
       bool

Randy Dunlap's avatar
Randy Dunlap committed
343
endmenu