blob: f15bb3b789d52dd2024d3efa3f48aafc643ef3ae [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-
Konrad Rzeszutek Wilked4f3462013-05-08 16:52:38 -040021 ballooning is disabled by default. If FRONTSWAP is configured,
Dan Magenheimera50777c2011-07-08 12:26:21 -060022 frontswap-selfshrinking is enabled by default but can be disabled
Konrad Rzeszutek Wilk54598d12013-05-08 16:44:06 -040023 with the 'tmem.selfshrink=0' kernel boot parameter; and self-ballooning
Konrad Rzeszutek Wilked4f3462013-05-08 16:52:38 -040024 is enabled by default but can be disabled with the 'tmem.selfballooning=0'
Dan Magenheimera50777c2011-07-08 12:26:21 -060025 kernel boot parameter. Note that systems without a sufficiently
26 large swap device should not enable self-ballooning.
27
Daniel Kiper080e2be2011-07-25 17:12:06 -070028config XEN_BALLOON_MEMORY_HOTPLUG
29 bool "Memory hotplug support for Xen balloon driver"
30 default n
31 depends on XEN_BALLOON && MEMORY_HOTPLUG
32 help
33 Memory hotplug support for Xen balloon driver allows expanding memory
34 available for the system above limit declared at system startup.
35 It is very useful on critical systems which require long
36 run without rebooting.
37
38 Memory could be hotplugged in following steps:
39
Vitaly Kuznetsov703fc132016-03-15 14:56:52 -070040 1) target domain: ensure that memory auto online policy is in
41 effect by checking /sys/devices/system/memory/auto_online_blocks
42 file (should be 'online').
43
44 2) control domain: xl mem-max <target-domain> <maxmem>
Daniel Kiper080e2be2011-07-25 17:12:06 -070045 where <maxmem> is >= requested memory size,
46
Vitaly Kuznetsov703fc132016-03-15 14:56:52 -070047 3) control domain: xl mem-set <target-domain> <memory>
Daniel Kiper080e2be2011-07-25 17:12:06 -070048 where <memory> is requested memory size; alternatively memory
49 could be added by writing proper value to
50 /sys/devices/system/xen_memory/xen_memory0/target or
Vitaly Kuznetsov703fc132016-03-15 14:56:52 -070051 /sys/devices/system/xen_memory/xen_memory0/target_kb on the
52 target domain.
Daniel Kiper080e2be2011-07-25 17:12:06 -070053
Vitaly Kuznetsov703fc132016-03-15 14:56:52 -070054 Alternatively, if memory auto onlining was not requested at step 1
55 the newly added memory can be manually onlined in the target domain
56 by doing the following:
Daniel Kiper080e2be2011-07-25 17:12:06 -070057
Vitaly Kuznetsov703fc132016-03-15 14:56:52 -070058 for i in /sys/devices/system/memory/memory*/state; do \
59 [ "`cat "$i"`" = offline ] && echo online > "$i"; done
60
61 or by adding the following line to udev rules:
Daniel Kiper080e2be2011-07-25 17:12:06 -070062
63 SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /sys$devpath/state'"
64
Juergen Gross633d6f12015-03-20 13:55:38 +010065config XEN_BALLOON_MEMORY_HOTPLUG_LIMIT
66 int "Hotplugged memory limit (in GiB) for a PV guest"
67 default 512 if X86_64
68 default 4 if X86_32
69 range 0 64 if X86_32
70 depends on XEN_HAVE_PVMMU
71 depends on XEN_BALLOON_MEMORY_HOTPLUG
72 help
73 Maxmium amount of memory (in GiB) that a PV guest can be
74 expanded to when using memory hotplug.
75
76 A PV guest can have more memory than this limit if is
77 started with a larger maximum.
78
79 This value is used to allocate enough space in internal
80 tables needed for physical memory administration.
81
Jeremy Fitzhardinge17758262008-04-02 10:54:13 -070082config XEN_SCRUB_PAGES
83 bool "Scrub pages before returning them to system"
84 depends on XEN_BALLOON
85 default y
86 help
87 Scrub pages before returning them to the system for reuse by
88 other domains. This makes sure that any confidential data
89 is not accidentally visible to other domains. Is it more
90 secure, but slightly less efficient.
91 If in doubt, say yes.
Alex Zeffertt1107ba82009-01-07 18:07:11 -080092
Ian Campbellf7116282009-02-06 19:21:19 -080093config XEN_DEV_EVTCHN
94 tristate "Xen /dev/xen/evtchn device"
Ian Campbellf7116282009-02-06 19:21:19 -080095 default y
96 help
Masanari Iida6b2aac42012-04-14 00:14:11 +090097 The evtchn driver allows a userspace process to trigger event
Ian Campbellf7116282009-02-06 19:21:19 -080098 channels and to receive notification of an event channel
99 firing.
100 If in doubt, say yes.
101
Ian Campbelldf660252009-02-09 12:05:51 -0800102config XEN_BACKEND
Jeremy Fitzhardinge329620a2009-03-21 23:29:34 -0700103 bool "Backend driver support"
Ian Campbelldf660252009-02-09 12:05:51 -0800104 depends on XEN_DOM0
105 default y
106 help
107 Support for backend device drivers that provide I/O services
108 to other virtual machines.
109
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800110config XENFS
111 tristate "Xen filesystem"
Bastian Blankd8414d32011-12-16 11:34:33 -0500112 select XEN_PRIVCMD
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800113 default y
114 help
115 The xen filesystem provides a way for domains to share
116 information with each other and with the hypervisor.
117 For example, by reading and writing the "xenbus" file, guests
118 may pass arbitrary information to the initial domain.
119 If in doubt, say yes.
120
121config XEN_COMPAT_XENFS
122 bool "Create compatibility mount point /proc/xen"
123 depends on XENFS
124 default y
125 help
126 The old xenstore userspace tools expect to find "xenbus"
127 under /proc/xen, but "xenbus" is now found at the root of the
128 xenfs filesystem. Selecting this causes the kernel to create
Matt LaPlante692105b2009-01-26 11:12:25 +0100129 the compatibility mount point /proc/xen if it is running on
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800130 a xen platform.
131 If in doubt, say yes.
132
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700133config XEN_SYS_HYPERVISOR
134 bool "Create xen entries under /sys/hypervisor"
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800135 depends on SYSFS
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700136 select SYS_HYPERVISOR
137 default y
138 help
139 Create entries under /sys/hypervisor describing the Xen
140 hypervisor environment. When running native or in another
141 virtual environment, /sys/hypervisor will still be present,
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800142 but will have no xen contents.
143
Ian Campbell2de06cc2009-02-09 12:05:51 -0800144config XEN_XENBUS_FRONTEND
Linus Torvalds9c4bc1c2011-01-13 18:46:48 -0800145 tristate
146
Gerd Hoffmannab315232010-12-14 18:40:46 +0000147config XEN_GNTDEV
148 tristate "userspace grant access device driver"
149 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000150 default m
Gerd Hoffmannab315232010-12-14 18:40:46 +0000151 select MMU_NOTIFIER
152 help
153 Allows userspace processes to use grants.
Ian Campbell6bac7f92010-12-10 14:39:15 +0000154
Daniel De Graafdd314052011-02-07 17:23:05 -0500155config XEN_GRANT_DEV_ALLOC
156 tristate "User-space grant reference allocator driver"
157 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000158 default m
Daniel De Graafdd314052011-02-07 17:23:05 -0500159 help
160 Allows userspace processes to create pages with access granted
161 to other domains. This can be used to implement frontend drivers
162 or as part of an inter-domain shared memory channel.
163
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400164config SWIOTLB_XEN
165 def_bool y
Konrad Rzeszutek Wilk27756092010-10-08 11:06:20 -0400166 select SWIOTLB
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400167
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600168config XEN_TMEM
Dan Magenheimer10a7a0772013-04-30 15:27:00 -0700169 tristate
Stefano Stabellini741ddbc2013-07-23 17:46:58 +0100170 depends on !ARM && !ARM64
Dan Magenheimer10a7a0772013-04-30 15:27:00 -0700171 default m if (CLEANCACHE || FRONTSWAP)
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600172 help
173 Shim to interface in-kernel Transcendent Memory hooks
174 (e.g. cleancache and frontswap) to Xen tmem hypercalls.
175
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400176config XEN_PCIDEV_BACKEND
177 tristate "Xen PCI-device backend driver"
178 depends on PCI && X86 && XEN
179 depends on XEN_BACKEND
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400180 default m
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400181 help
182 The PCI device backend driver allows the kernel to export arbitrary
183 PCI devices to other guests. If you select this to be a module, you
184 will need to make sure no other driver has bound to the device(s)
185 you want to make visible to other guests.
186
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400187 The parameter "passthrough" allows you specify how you want the PCI
188 devices to appear in the guest. You can choose the default (0) where
189 PCI topology starts at 00.00.0, or (1) for passthrough if you want
190 the PCI devices topology appear the same as in the host.
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400191
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400192 The "hide" parameter (only applicable if backend driver is compiled
193 into the kernel) allows you to bind the PCI devices to this module
194 from the default device drivers. The argument is the list of PCI BDFs:
195 xen-pciback.hide=(03:00.0)(04:00.0)
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400196
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400197 If in doubt, say m.
Bastian Blankd8414d32011-12-16 11:34:33 -0500198
Juergen Grossd9d660f2014-08-28 06:44:12 +0200199config XEN_SCSI_BACKEND
200 tristate "XEN SCSI backend driver"
201 depends on XEN && XEN_BACKEND && TARGET_CORE
202 help
203 The SCSI backend driver allows the kernel to export its SCSI Devices
204 to other guests via a high-performance shared-memory interface.
205 Only needed for systems running as XEN driver domains (e.g. Dom0) and
206 if guests need generic access to SCSI devices.
207
Bastian Blankd8414d32011-12-16 11:34:33 -0500208config XEN_PRIVCMD
209 tristate
210 depends on XEN
211 default m
212
Liu Jinsongdcb93b92013-01-24 20:16:59 +0800213config XEN_STUB
214 bool "Xen stub drivers"
Konrad Rzeszutek Wilk76fc2532013-03-22 10:15:47 -0400215 depends on XEN && X86_64 && BROKEN
Liu Jinsongdcb93b92013-01-24 20:16:59 +0800216 default n
217 help
218 Allow kernel to install stub drivers, to reserve space for Xen drivers,
219 i.e. memory hotplug and cpu hotplug, and to block native drivers loaded,
220 so that real Xen drivers can be modular.
221
222 To enable Xen features like cpu and memory hotplug, select Y here.
223
Liu Jinsongef92e7c2013-01-24 20:19:47 +0800224config XEN_ACPI_HOTPLUG_MEMORY
225 tristate "Xen ACPI memory hotplug"
226 depends on XEN_DOM0 && XEN_STUB && ACPI
227 default n
228 help
229 This is Xen ACPI memory hotplug.
230
231 Currently Xen only support ACPI memory hot-add. If you want
232 to hot-add memory at runtime (the hot-added memory cannot be
233 removed until machine stop), select Y/M here, otherwise select N.
234
Liu Jinsong39adc482013-01-25 15:43:34 +0800235config XEN_ACPI_HOTPLUG_CPU
236 tristate "Xen ACPI cpu hotplug"
237 depends on XEN_DOM0 && XEN_STUB && ACPI
238 select ACPI_CONTAINER
239 default n
240 help
241 Xen ACPI cpu enumerating and hotplugging
242
243 For hotplugging, currently Xen only support ACPI cpu hotadd.
244 If you want to hotadd cpu at runtime (the hotadded cpu cannot
245 be removed until machine stop), select Y/M here.
246
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500247config XEN_ACPI_PROCESSOR
248 tristate "Xen ACPI processor"
Konrad Rzeszutek Wilkdf7a3ee2012-03-24 09:18:57 -0400249 depends on XEN && X86 && ACPI_PROCESSOR && CPU_FREQ
Konrad Rzeszutek Wilk102b2082012-03-13 13:28:12 -0400250 default m
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500251 help
Andrew Morton1fd14432012-05-04 14:04:12 -0700252 This ACPI processor uploads Power Management information to the Xen
253 hypervisor.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500254
Andrew Morton1fd14432012-05-04 14:04:12 -0700255 To do that the driver parses the Power Management data and uploads
256 said information to the Xen hypervisor. Then the Xen hypervisor can
Masanari Iida5065a702013-11-30 21:38:43 +0900257 select the proper Cx and Pxx states. It also registers itself as the
Andrew Morton1fd14432012-05-04 14:04:12 -0700258 SMM so that other drivers (such as ACPI cpufreq scaling driver) will
259 not load.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500260
Andrew Morton1fd14432012-05-04 14:04:12 -0700261 To compile this driver as a module, choose M here: the module will be
262 called xen_acpi_processor If you do not know what to choose, select
263 M here. If the CPUFREQ drivers are built in, select Y here.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500264
Liu, Jinsongcef12ee2012-06-07 19:56:51 +0800265config XEN_MCE_LOG
266 bool "Xen platform mcelog"
267 depends on XEN_DOM0 && X86_64 && X86_MCE
268 default n
269 help
270 Allow kernel fetching MCE error from Xen platform and
271 converting it into Linux mcelog format for mcelog tools
272
Ian Campbellc2374bf2012-10-03 12:17:50 +0100273config XEN_HAVE_PVMMU
274 bool
275
Daniel Kiperbe81c8a2014-06-30 19:53:02 +0200276config XEN_EFI
277 def_bool y
Shannon Zhaobe1aaf42016-04-07 20:03:32 +0800278 depends on (ARM || ARM64 || X86_64) && EFI
Daniel Kiperbe81c8a2014-06-30 19:53:02 +0200279
David Vrabel628c28e2015-03-11 14:49:56 +0000280config XEN_AUTO_XLATE
281 def_bool y
282 depends on ARM || ARM64 || XEN_PVHVM
283 help
284 Support for auto-translated physmap guests.
285
Hanjun Guo42068cf2015-03-24 14:02:52 +0000286config XEN_ACPI
287 def_bool y
288 depends on X86 && ACPI
289
Boris Ostrovskya11f4f02015-08-10 16:34:32 -0400290config XEN_SYMS
291 bool "Xen symbols"
292 depends on X86 && XEN_DOM0 && XENFS
293 default y if KALLSYMS
294 help
295 Exports hypervisor symbols (along with their types and addresses) via
296 /proc/xen/xensyms file, similar to /proc/kallsyms
297
Boris Ostrovsky5f141542015-08-10 16:34:33 -0400298config XEN_HAVE_VPMU
299 bool
300
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800301endmenu