blob: 8d2501e604dde22dd2bf1103454c4a1824f93793 [file] [log] [blame]
Randy Dunlap27fb7f02010-03-05 13:44:18 -08001menu "Xen driver support"
2 depends on XEN
3
Jeremy Fitzhardinge17758262008-04-02 10:54:13 -07004config XEN_BALLOON
5 bool "Xen memory balloon driver"
Jeremy Fitzhardinge17758262008-04-02 10:54:13 -07006 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
Dan Magenheimera50777c2011-07-08 12:26:21 -060012config XEN_SELFBALLOONING
13 bool "Dynamically self-balloon kernel memory to target"
Konrad Rzeszutek Wilk65d4b242011-07-30 11:21:09 -040014 depends on XEN && XEN_BALLOON && CLEANCACHE && SWAP && XEN_TMEM
Dan Magenheimera50777c2011-07-08 12:26:21 -060015 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
Daniel Kiper080e2be2011-07-25 17:12:06 -070029config XEN_BALLOON_MEMORY_HOTPLUG
30 bool "Memory hotplug support for Xen balloon driver"
31 default n
32 depends on XEN_BALLOON && MEMORY_HOTPLUG
33 help
34 Memory hotplug support for Xen balloon driver allows expanding memory
35 available for the system above limit declared at system startup.
36 It is very useful on critical systems which require long
37 run without rebooting.
38
39 Memory could be hotplugged in following steps:
40
41 1) dom0: xl mem-max <domU> <maxmem>
42 where <maxmem> is >= requested memory size,
43
44 2) dom0: xl mem-set <domU> <memory>
45 where <memory> is requested memory size; alternatively memory
46 could be added by writing proper value to
47 /sys/devices/system/xen_memory/xen_memory0/target or
48 /sys/devices/system/xen_memory/xen_memory0/target_kb on dumU,
49
50 3) domU: for i in /sys/devices/system/memory/memory*/state; do \
51 [ "`cat "$i"`" = offline ] && echo online > "$i"; done
52
53 Memory could be onlined automatically on domU by adding following line to udev rules:
54
55 SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /sys$devpath/state'"
56
57 In that case step 3 should be omitted.
58
Jeremy Fitzhardinge17758262008-04-02 10:54:13 -070059config XEN_SCRUB_PAGES
60 bool "Scrub pages before returning them to system"
61 depends on XEN_BALLOON
62 default y
63 help
64 Scrub pages before returning them to the system for reuse by
65 other domains. This makes sure that any confidential data
66 is not accidentally visible to other domains. Is it more
67 secure, but slightly less efficient.
68 If in doubt, say yes.
Alex Zeffertt1107ba82009-01-07 18:07:11 -080069
Ian Campbellf7116282009-02-06 19:21:19 -080070config XEN_DEV_EVTCHN
71 tristate "Xen /dev/xen/evtchn device"
Ian Campbellf7116282009-02-06 19:21:19 -080072 default y
73 help
Masanari Iida6b2aac42012-04-14 00:14:11 +090074 The evtchn driver allows a userspace process to trigger event
Ian Campbellf7116282009-02-06 19:21:19 -080075 channels and to receive notification of an event channel
76 firing.
77 If in doubt, say yes.
78
Ian Campbelldf660252009-02-09 12:05:51 -080079config XEN_BACKEND
Jeremy Fitzhardinge329620a2009-03-21 23:29:34 -070080 bool "Backend driver support"
Ian Campbelldf660252009-02-09 12:05:51 -080081 depends on XEN_DOM0
82 default y
83 help
84 Support for backend device drivers that provide I/O services
85 to other virtual machines.
86
Alex Zeffertt1107ba82009-01-07 18:07:11 -080087config XENFS
88 tristate "Xen filesystem"
Bastian Blankd8414d32011-12-16 11:34:33 -050089 select XEN_PRIVCMD
Alex Zeffertt1107ba82009-01-07 18:07:11 -080090 default y
91 help
92 The xen filesystem provides a way for domains to share
93 information with each other and with the hypervisor.
94 For example, by reading and writing the "xenbus" file, guests
95 may pass arbitrary information to the initial domain.
96 If in doubt, say yes.
97
98config XEN_COMPAT_XENFS
99 bool "Create compatibility mount point /proc/xen"
100 depends on XENFS
101 default y
102 help
103 The old xenstore userspace tools expect to find "xenbus"
104 under /proc/xen, but "xenbus" is now found at the root of the
105 xenfs filesystem. Selecting this causes the kernel to create
Matt LaPlante692105b2009-01-26 11:12:25 +0100106 the compatibility mount point /proc/xen if it is running on
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800107 a xen platform.
108 If in doubt, say yes.
109
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700110config XEN_SYS_HYPERVISOR
111 bool "Create xen entries under /sys/hypervisor"
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800112 depends on SYSFS
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700113 select SYS_HYPERVISOR
114 default y
115 help
116 Create entries under /sys/hypervisor describing the Xen
117 hypervisor environment. When running native or in another
118 virtual environment, /sys/hypervisor will still be present,
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800119 but will have no xen contents.
120
Ian Campbell2de06cc2009-02-09 12:05:51 -0800121config XEN_XENBUS_FRONTEND
Linus Torvalds9c4bc1c2011-01-13 18:46:48 -0800122 tristate
123
Gerd Hoffmannab315232010-12-14 18:40:46 +0000124config XEN_GNTDEV
125 tristate "userspace grant access device driver"
126 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000127 default m
Gerd Hoffmannab315232010-12-14 18:40:46 +0000128 select MMU_NOTIFIER
129 help
130 Allows userspace processes to use grants.
Ian Campbell6bac7f92010-12-10 14:39:15 +0000131
Daniel De Graafdd314052011-02-07 17:23:05 -0500132config XEN_GRANT_DEV_ALLOC
133 tristate "User-space grant reference allocator driver"
134 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000135 default m
Daniel De Graafdd314052011-02-07 17:23:05 -0500136 help
137 Allows userspace processes to create pages with access granted
138 to other domains. This can be used to implement frontend drivers
139 or as part of an inter-domain shared memory channel.
140
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400141config SWIOTLB_XEN
142 def_bool y
Konrad Rzeszutek Wilk27756092010-10-08 11:06:20 -0400143 depends on PCI
144 select SWIOTLB
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400145
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600146config XEN_TMEM
147 bool
148 default y if (CLEANCACHE || FRONTSWAP)
149 help
150 Shim to interface in-kernel Transcendent Memory hooks
151 (e.g. cleancache and frontswap) to Xen tmem hypercalls.
152
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400153config XEN_PCIDEV_BACKEND
154 tristate "Xen PCI-device backend driver"
155 depends on PCI && X86 && XEN
156 depends on XEN_BACKEND
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400157 default m
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400158 help
159 The PCI device backend driver allows the kernel to export arbitrary
160 PCI devices to other guests. If you select this to be a module, you
161 will need to make sure no other driver has bound to the device(s)
162 you want to make visible to other guests.
163
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400164 The parameter "passthrough" allows you specify how you want the PCI
165 devices to appear in the guest. You can choose the default (0) where
166 PCI topology starts at 00.00.0, or (1) for passthrough if you want
167 the PCI devices topology appear the same as in the host.
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400168
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400169 The "hide" parameter (only applicable if backend driver is compiled
170 into the kernel) allows you to bind the PCI devices to this module
171 from the default device drivers. The argument is the list of PCI BDFs:
172 xen-pciback.hide=(03:00.0)(04:00.0)
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400173
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400174 If in doubt, say m.
Bastian Blankd8414d32011-12-16 11:34:33 -0500175
176config XEN_PRIVCMD
177 tristate
178 depends on XEN
179 default m
180
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500181config XEN_ACPI_PROCESSOR
182 tristate "Xen ACPI processor"
Konrad Rzeszutek Wilkdf7a3ee2012-03-24 09:18:57 -0400183 depends on XEN && X86 && ACPI_PROCESSOR && CPU_FREQ
Konrad Rzeszutek Wilk102b2082012-03-13 13:28:12 -0400184 default m
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500185 help
Andrew Morton1fd14432012-05-04 14:04:12 -0700186 This ACPI processor uploads Power Management information to the Xen
187 hypervisor.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500188
Andrew Morton1fd14432012-05-04 14:04:12 -0700189 To do that the driver parses the Power Management data and uploads
190 said information to the Xen hypervisor. Then the Xen hypervisor can
191 select the proper Cx and Pxx states. It also registers itslef as the
192 SMM so that other drivers (such as ACPI cpufreq scaling driver) will
193 not load.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500194
Andrew Morton1fd14432012-05-04 14:04:12 -0700195 To compile this driver as a module, choose M here: the module will be
196 called xen_acpi_processor If you do not know what to choose, select
197 M here. If the CPUFREQ drivers are built in, select Y here.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500198
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800199endmenu