]> git.proxmox.com Git - mirror_ubuntu-zesty-kernel.git/blob - drivers/xen/Kconfig
Merge branch 'drm-next' of ../drm-next into drm-linus
[mirror_ubuntu-zesty-kernel.git] / drivers / xen / Kconfig
1 config XEN_BALLOON
2 bool "Xen memory balloon driver"
3 depends on XEN
4 default y
5 help
6 The balloon driver allows the Xen domain to request more memory from
7 the system to expand the domain's memory allocation, or alternatively
8 return unneeded memory to the system.
9
10 config XEN_SCRUB_PAGES
11 bool "Scrub pages before returning them to system"
12 depends on XEN_BALLOON
13 default y
14 help
15 Scrub pages before returning them to the system for reuse by
16 other domains. This makes sure that any confidential data
17 is not accidentally visible to other domains. Is it more
18 secure, but slightly less efficient.
19 If in doubt, say yes.
20
21 config XEN_DEV_EVTCHN
22 tristate "Xen /dev/xen/evtchn device"
23 depends on XEN
24 default y
25 help
26 The evtchn driver allows a userspace process to triger event
27 channels and to receive notification of an event channel
28 firing.
29 If in doubt, say yes.
30
31 config XENFS
32 tristate "Xen filesystem"
33 depends on XEN
34 default y
35 help
36 The xen filesystem provides a way for domains to share
37 information with each other and with the hypervisor.
38 For example, by reading and writing the "xenbus" file, guests
39 may pass arbitrary information to the initial domain.
40 If in doubt, say yes.
41
42 config XEN_COMPAT_XENFS
43 bool "Create compatibility mount point /proc/xen"
44 depends on XENFS
45 default y
46 help
47 The old xenstore userspace tools expect to find "xenbus"
48 under /proc/xen, but "xenbus" is now found at the root of the
49 xenfs filesystem. Selecting this causes the kernel to create
50 the compatibility mount point /proc/xen if it is running on
51 a xen platform.
52 If in doubt, say yes.
53
54 config XEN_SYS_HYPERVISOR
55 bool "Create xen entries under /sys/hypervisor"
56 depends on XEN && SYSFS
57 select SYS_HYPERVISOR
58 default y
59 help
60 Create entries under /sys/hypervisor describing the Xen
61 hypervisor environment. When running native or in another
62 virtual environment, /sys/hypervisor will still be present,
63 but will have no xen contents.