blob: 73708acce3ca78dfeb2da5fa78d6655e8f6554d4 [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
40 1) dom0: xl mem-max <domU> <maxmem>
41 where <maxmem> is >= requested memory size,
42
43 2) dom0: xl mem-set <domU> <memory>
44 where <memory> is requested memory size; alternatively memory
45 could be added by writing proper value to
46 /sys/devices/system/xen_memory/xen_memory0/target or
47 /sys/devices/system/xen_memory/xen_memory0/target_kb on dumU,
48
49 3) domU: for i in /sys/devices/system/memory/memory*/state; do \
50 [ "`cat "$i"`" = offline ] && echo online > "$i"; done
51
52 Memory could be onlined automatically on domU by adding following line to udev rules:
53
54 SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /sys$devpath/state'"
55
56 In that case step 3 should be omitted.
57
Juergen Gross633d6f12015-03-20 13:55:38 +010058config XEN_BALLOON_MEMORY_HOTPLUG_LIMIT
59 int "Hotplugged memory limit (in GiB) for a PV guest"
60 default 512 if X86_64
61 default 4 if X86_32
62 range 0 64 if X86_32
63 depends on XEN_HAVE_PVMMU
64 depends on XEN_BALLOON_MEMORY_HOTPLUG
65 help
66 Maxmium amount of memory (in GiB) that a PV guest can be
67 expanded to when using memory hotplug.
68
69 A PV guest can have more memory than this limit if is
70 started with a larger maximum.
71
72 This value is used to allocate enough space in internal
73 tables needed for physical memory administration.
74
Jeremy Fitzhardinge17758262008-04-02 10:54:13 -070075config XEN_SCRUB_PAGES
76 bool "Scrub pages before returning them to system"
77 depends on XEN_BALLOON
78 default y
79 help
80 Scrub pages before returning them to the system for reuse by
81 other domains. This makes sure that any confidential data
82 is not accidentally visible to other domains. Is it more
83 secure, but slightly less efficient.
84 If in doubt, say yes.
Alex Zeffertt1107ba82009-01-07 18:07:11 -080085
Ian Campbellf7116282009-02-06 19:21:19 -080086config XEN_DEV_EVTCHN
87 tristate "Xen /dev/xen/evtchn device"
Ian Campbellf7116282009-02-06 19:21:19 -080088 default y
89 help
Masanari Iida6b2aac42012-04-14 00:14:11 +090090 The evtchn driver allows a userspace process to trigger event
Ian Campbellf7116282009-02-06 19:21:19 -080091 channels and to receive notification of an event channel
92 firing.
93 If in doubt, say yes.
94
Ian Campbelldf660252009-02-09 12:05:51 -080095config XEN_BACKEND
Jeremy Fitzhardinge329620a2009-03-21 23:29:34 -070096 bool "Backend driver support"
Ian Campbelldf660252009-02-09 12:05:51 -080097 depends on XEN_DOM0
98 default y
99 help
100 Support for backend device drivers that provide I/O services
101 to other virtual machines.
102
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800103config XENFS
104 tristate "Xen filesystem"
Bastian Blankd8414d32011-12-16 11:34:33 -0500105 select XEN_PRIVCMD
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800106 default y
107 help
108 The xen filesystem provides a way for domains to share
109 information with each other and with the hypervisor.
110 For example, by reading and writing the "xenbus" file, guests
111 may pass arbitrary information to the initial domain.
112 If in doubt, say yes.
113
114config XEN_COMPAT_XENFS
115 bool "Create compatibility mount point /proc/xen"
116 depends on XENFS
117 default y
118 help
119 The old xenstore userspace tools expect to find "xenbus"
120 under /proc/xen, but "xenbus" is now found at the root of the
121 xenfs filesystem. Selecting this causes the kernel to create
Matt LaPlante692105b2009-01-26 11:12:25 +0100122 the compatibility mount point /proc/xen if it is running on
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800123 a xen platform.
124 If in doubt, say yes.
125
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700126config XEN_SYS_HYPERVISOR
127 bool "Create xen entries under /sys/hypervisor"
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800128 depends on SYSFS
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700129 select SYS_HYPERVISOR
130 default y
131 help
132 Create entries under /sys/hypervisor describing the Xen
133 hypervisor environment. When running native or in another
134 virtual environment, /sys/hypervisor will still be present,
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800135 but will have no xen contents.
136
Ian Campbell2de06cc2009-02-09 12:05:51 -0800137config XEN_XENBUS_FRONTEND
Linus Torvalds9c4bc1c2011-01-13 18:46:48 -0800138 tristate
139
Gerd Hoffmannab315232010-12-14 18:40:46 +0000140config XEN_GNTDEV
141 tristate "userspace grant access device driver"
142 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000143 default m
Gerd Hoffmannab315232010-12-14 18:40:46 +0000144 select MMU_NOTIFIER
145 help
146 Allows userspace processes to use grants.
Ian Campbell6bac7f92010-12-10 14:39:15 +0000147
Daniel De Graafdd314052011-02-07 17:23:05 -0500148config XEN_GRANT_DEV_ALLOC
149 tristate "User-space grant reference allocator driver"
150 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000151 default m
Daniel De Graafdd314052011-02-07 17:23:05 -0500152 help
153 Allows userspace processes to create pages with access granted
154 to other domains. This can be used to implement frontend drivers
155 or as part of an inter-domain shared memory channel.
156
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400157config SWIOTLB_XEN
158 def_bool y
Konrad Rzeszutek Wilk27756092010-10-08 11:06:20 -0400159 select SWIOTLB
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400160
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600161config XEN_TMEM
Dan Magenheimer10a7a0772013-04-30 15:27:00 -0700162 tristate
Stefano Stabellini741ddbc2013-07-23 17:46:58 +0100163 depends on !ARM && !ARM64
Dan Magenheimer10a7a0772013-04-30 15:27:00 -0700164 default m if (CLEANCACHE || FRONTSWAP)
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600165 help
166 Shim to interface in-kernel Transcendent Memory hooks
167 (e.g. cleancache and frontswap) to Xen tmem hypercalls.
168
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400169config XEN_PCIDEV_BACKEND
170 tristate "Xen PCI-device backend driver"
171 depends on PCI && X86 && XEN
172 depends on XEN_BACKEND
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400173 default m
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400174 help
175 The PCI device backend driver allows the kernel to export arbitrary
176 PCI devices to other guests. If you select this to be a module, you
177 will need to make sure no other driver has bound to the device(s)
178 you want to make visible to other guests.
179
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400180 The parameter "passthrough" allows you specify how you want the PCI
181 devices to appear in the guest. You can choose the default (0) where
182 PCI topology starts at 00.00.0, or (1) for passthrough if you want
183 the PCI devices topology appear the same as in the host.
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400184
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400185 The "hide" parameter (only applicable if backend driver is compiled
186 into the kernel) allows you to bind the PCI devices to this module
187 from the default device drivers. The argument is the list of PCI BDFs:
188 xen-pciback.hide=(03:00.0)(04:00.0)
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400189
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400190 If in doubt, say m.
Bastian Blankd8414d32011-12-16 11:34:33 -0500191
Juergen Grossd9d660f2014-08-28 06:44:12 +0200192config XEN_SCSI_BACKEND
193 tristate "XEN SCSI backend driver"
194 depends on XEN && XEN_BACKEND && TARGET_CORE
195 help
196 The SCSI backend driver allows the kernel to export its SCSI Devices
197 to other guests via a high-performance shared-memory interface.
198 Only needed for systems running as XEN driver domains (e.g. Dom0) and
199 if guests need generic access to SCSI devices.
200
Bastian Blankd8414d32011-12-16 11:34:33 -0500201config XEN_PRIVCMD
202 tristate
203 depends on XEN
204 default m
205
Liu Jinsongdcb93b92013-01-24 20:16:59 +0800206config XEN_STUB
207 bool "Xen stub drivers"
Konrad Rzeszutek Wilk76fc2532013-03-22 10:15:47 -0400208 depends on XEN && X86_64 && BROKEN
Liu Jinsongdcb93b92013-01-24 20:16:59 +0800209 default n
210 help
211 Allow kernel to install stub drivers, to reserve space for Xen drivers,
212 i.e. memory hotplug and cpu hotplug, and to block native drivers loaded,
213 so that real Xen drivers can be modular.
214
215 To enable Xen features like cpu and memory hotplug, select Y here.
216
Liu Jinsongef92e7c2013-01-24 20:19:47 +0800217config XEN_ACPI_HOTPLUG_MEMORY
218 tristate "Xen ACPI memory hotplug"
219 depends on XEN_DOM0 && XEN_STUB && ACPI
220 default n
221 help
222 This is Xen ACPI memory hotplug.
223
224 Currently Xen only support ACPI memory hot-add. If you want
225 to hot-add memory at runtime (the hot-added memory cannot be
226 removed until machine stop), select Y/M here, otherwise select N.
227
Liu Jinsong39adc482013-01-25 15:43:34 +0800228config XEN_ACPI_HOTPLUG_CPU
229 tristate "Xen ACPI cpu hotplug"
230 depends on XEN_DOM0 && XEN_STUB && ACPI
231 select ACPI_CONTAINER
232 default n
233 help
234 Xen ACPI cpu enumerating and hotplugging
235
236 For hotplugging, currently Xen only support ACPI cpu hotadd.
237 If you want to hotadd cpu at runtime (the hotadded cpu cannot
238 be removed until machine stop), select Y/M here.
239
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500240config XEN_ACPI_PROCESSOR
241 tristate "Xen ACPI processor"
Konrad Rzeszutek Wilkdf7a3ee2012-03-24 09:18:57 -0400242 depends on XEN && X86 && ACPI_PROCESSOR && CPU_FREQ
Konrad Rzeszutek Wilk102b2082012-03-13 13:28:12 -0400243 default m
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500244 help
Andrew Morton1fd14432012-05-04 14:04:12 -0700245 This ACPI processor uploads Power Management information to the Xen
246 hypervisor.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500247
Andrew Morton1fd14432012-05-04 14:04:12 -0700248 To do that the driver parses the Power Management data and uploads
249 said information to the Xen hypervisor. Then the Xen hypervisor can
Masanari Iida5065a702013-11-30 21:38:43 +0900250 select the proper Cx and Pxx states. It also registers itself as the
Andrew Morton1fd14432012-05-04 14:04:12 -0700251 SMM so that other drivers (such as ACPI cpufreq scaling driver) will
252 not load.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500253
Andrew Morton1fd14432012-05-04 14:04:12 -0700254 To compile this driver as a module, choose M here: the module will be
255 called xen_acpi_processor If you do not know what to choose, select
256 M here. If the CPUFREQ drivers are built in, select Y here.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500257
Liu, Jinsongcef12ee2012-06-07 19:56:51 +0800258config XEN_MCE_LOG
259 bool "Xen platform mcelog"
260 depends on XEN_DOM0 && X86_64 && X86_MCE
261 default n
262 help
263 Allow kernel fetching MCE error from Xen platform and
264 converting it into Linux mcelog format for mcelog tools
265
Ian Campbellc2374bf2012-10-03 12:17:50 +0100266config XEN_HAVE_PVMMU
267 bool
268
Daniel Kiperbe81c8a2014-06-30 19:53:02 +0200269config XEN_EFI
270 def_bool y
271 depends on X86_64 && EFI
272
David Vrabel628c28e2015-03-11 14:49:56 +0000273config XEN_AUTO_XLATE
274 def_bool y
275 depends on ARM || ARM64 || XEN_PVHVM
276 help
277 Support for auto-translated physmap guests.
278
Hanjun Guo42068cf2015-03-24 14:02:52 +0000279config XEN_ACPI
280 def_bool y
281 depends on X86 && ACPI
282
Boris Ostrovskya11f4f02015-08-10 16:34:32 -0400283config XEN_SYMS
284 bool "Xen symbols"
285 depends on X86 && XEN_DOM0 && XENFS
286 default y if KALLSYMS
287 help
288 Exports hypervisor symbols (along with their types and addresses) via
289 /proc/xen/xensyms file, similar to /proc/kallsyms
290
Boris Ostrovsky5f141542015-08-10 16:34:33 -0400291config XEN_HAVE_VPMU
292 bool
293
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800294endmenu