Lines Matching +full:system +full:- +full:on +full:- +full:module

1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on XEN
10 the system to expand the domain's memory allocation, or alternatively
11 return unneeded memory to the system.
15 depends on XEN_BALLOON && MEMORY_HOTPLUG
19 available for the system above limit declared at system startup.
20 It is very useful on critical systems which require long
29 effect by checking /sys/devices/system/memory/auto_online_blocks
32 2) control domain: xl mem-max <target-domain> <maxmem>
35 3) control domain: xl mem-set <target-domain> <memory>
38 /sys/devices/system/xen_memory/xen_memory0/target or
39 /sys/devices/system/xen_memory/xen_memory0/target_kb on the
46 for i in /sys/devices/system/memory/memory*/state; do \
51 …SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /…
56 depends on XEN_HAVE_PVMMU
57 depends on MEMORY_HOTPLUG
69 bool "Scrub pages before returning them to system by default"
70 depends on XEN_BALLOON
73 Scrub pages before returning them to the system for reuse by
78 /sys/devices/system/xen_memory/xen_memory0/scrub_pages.
112 depends on XENFS
118 the compatibility mount point /proc/xen if it is running on
124 depends on SYSFS
138 depends on XEN
145 bool "Add support for dma-buf grant access device driver extension"
146 depends on XEN_GNTDEV && XEN_GRANT_DMA_ALLOC
150 dma-buf implementation. With this extension grant references to
151 the pages of an imported dma-buf can be exported for other domain
153 converted into a local dma-buf for local export.
156 tristate "User-space grant reference allocator driver"
157 depends on XEN
162 or as part of an inter-domain shared memory channel.
165 bool "Allow allocating DMA capable buffers with grant reference module"
166 depends on XEN && HAS_DMA
168 Extends grant table module API to allow allocating DMA capable
169 buffers and mapping foreign grant references on top of it.
180 depends on ARCH_HAS_DMA_OPS
181 depends on XEN_PV || ARM || ARM64
188 tristate "Xen PCI-device stub driver"
189 depends on PCI && !X86 && XEN
190 depends on XEN_BACKEND
195 device backend driver without para-virtualized support for guests.
196 If you select this to be a module, you will need to make sure no
201 into the kernel) allows you to bind the PCI devices to this module
203 xen-pciback.hide=(03:00.0)(04:00.0)
208 tristate "Xen PCI-device backend driver"
209 depends on PCI && X86 && XEN
210 depends on XEN_BACKEND
215 PCI devices to other guests. If you select this to be a module, you
225 into the kernel) allows you to bind the PCI devices to this module
227 xen-pciback.hide=(03:00.0)(04:00.0)
233 depends on INET && XEN
243 depends on INET && XEN && XEN_BACKEND
254 depends on XEN && XEN_BACKEND && TARGET_CORE
257 to other guests via a high-performance shared-memory interface.
263 depends on XEN
274 depends on XEN_PRIVCMD && XEN_VIRTIO && EVENTFD
281 depends on XEN && XEN_PV_DOM0 && X86 && ACPI_PROCESSOR && CPU_FREQ
293 To compile this driver as a module, choose M here: the module will be
299 depends on XEN_PV_DOM0 && X86_MCE
309 depends on (ARM || ARM64 || X86_64) && EFI
313 depends on ARM || ARM64 || XEN_PVHVM
315 Support for auto-translated physmap guests.
319 depends on X86 && ACPI
323 depends on X86 && XEN_DOM0 && XENFS
337 depends on ZONE_DEVICE
354 depends on ARCH_HAS_DMA_OPS
355 depends on VIRTIO
359 Enable virtio support for running as Xen guest. Depending on the
360 guest type this will require special support on the backend side
361 (qemu or kernel, depending on the virtio device types used).
367 depends on XEN_VIRTIO
371 of the guest memory. This will need support on the backend side
372 (e.g. qemu or kernel, depending on the virtio device types used).