blob: cabfa97f4674ef12c1fcd13d1a55c4affd47f635 [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"
Arnd Bergmannf880b672012-10-09 10:33:52 +00006 depends on !ARM
Jeremy Fitzhardinge17758262008-04-02 10:54:13 -07007 default y
8 help
9 The balloon driver allows the Xen domain to request more memory from
10 the system to expand the domain's memory allocation, or alternatively
11 return unneeded memory to the system.
12
Dan Magenheimera50777c2011-07-08 12:26:21 -060013config XEN_SELFBALLOONING
14 bool "Dynamically self-balloon kernel memory to target"
Konrad Rzeszutek Wilk65d4b242011-07-30 11:21:09 -040015 depends on XEN && XEN_BALLOON && CLEANCACHE && SWAP && XEN_TMEM
Dan Magenheimera50777c2011-07-08 12:26:21 -060016 default n
17 help
18 Self-ballooning dynamically balloons available kernel memory driven
19 by the current usage of anonymous memory ("committed AS") and
20 controlled by various sysfs-settable parameters. Configuring
21 FRONTSWAP is highly recommended; if it is not configured, self-
22 ballooning is disabled by default but can be enabled with the
23 'selfballooning' kernel boot parameter. If FRONTSWAP is configured,
24 frontswap-selfshrinking is enabled by default but can be disabled
25 with the 'noselfshrink' kernel boot parameter; and self-ballooning
26 is enabled by default but can be disabled with the 'noselfballooning'
27 kernel boot parameter. Note that systems without a sufficiently
28 large swap device should not enable self-ballooning.
29
Daniel Kiper080e2be2011-07-25 17:12:06 -070030config XEN_BALLOON_MEMORY_HOTPLUG
31 bool "Memory hotplug support for Xen balloon driver"
32 default n
33 depends on XEN_BALLOON && MEMORY_HOTPLUG
34 help
35 Memory hotplug support for Xen balloon driver allows expanding memory
36 available for the system above limit declared at system startup.
37 It is very useful on critical systems which require long
38 run without rebooting.
39
40 Memory could be hotplugged in following steps:
41
42 1) dom0: xl mem-max <domU> <maxmem>
43 where <maxmem> is >= requested memory size,
44
45 2) dom0: xl mem-set <domU> <memory>
46 where <memory> is requested memory size; alternatively memory
47 could be added by writing proper value to
48 /sys/devices/system/xen_memory/xen_memory0/target or
49 /sys/devices/system/xen_memory/xen_memory0/target_kb on dumU,
50
51 3) domU: for i in /sys/devices/system/memory/memory*/state; do \
52 [ "`cat "$i"`" = offline ] && echo online > "$i"; done
53
54 Memory could be onlined automatically on domU by adding following line to udev rules:
55
56 SUBSYSTEM=="memory", ACTION=="add", RUN+="/bin/sh -c '[ -f /sys$devpath/state ] && echo online > /sys$devpath/state'"
57
58 In that case step 3 should be omitted.
59
Jeremy Fitzhardinge17758262008-04-02 10:54:13 -070060config XEN_SCRUB_PAGES
61 bool "Scrub pages before returning them to system"
62 depends on XEN_BALLOON
63 default y
64 help
65 Scrub pages before returning them to the system for reuse by
66 other domains. This makes sure that any confidential data
67 is not accidentally visible to other domains. Is it more
68 secure, but slightly less efficient.
69 If in doubt, say yes.
Alex Zeffertt1107ba82009-01-07 18:07:11 -080070
Ian Campbellf7116282009-02-06 19:21:19 -080071config XEN_DEV_EVTCHN
72 tristate "Xen /dev/xen/evtchn device"
Ian Campbellf7116282009-02-06 19:21:19 -080073 default y
74 help
Masanari Iida6b2aac42012-04-14 00:14:11 +090075 The evtchn driver allows a userspace process to trigger event
Ian Campbellf7116282009-02-06 19:21:19 -080076 channels and to receive notification of an event channel
77 firing.
78 If in doubt, say yes.
79
Ian Campbelldf660252009-02-09 12:05:51 -080080config XEN_BACKEND
Jeremy Fitzhardinge329620a2009-03-21 23:29:34 -070081 bool "Backend driver support"
Ian Campbelldf660252009-02-09 12:05:51 -080082 depends on XEN_DOM0
83 default y
84 help
85 Support for backend device drivers that provide I/O services
86 to other virtual machines.
87
Alex Zeffertt1107ba82009-01-07 18:07:11 -080088config XENFS
89 tristate "Xen filesystem"
Bastian Blankd8414d32011-12-16 11:34:33 -050090 select XEN_PRIVCMD
Alex Zeffertt1107ba82009-01-07 18:07:11 -080091 default y
92 help
93 The xen filesystem provides a way for domains to share
94 information with each other and with the hypervisor.
95 For example, by reading and writing the "xenbus" file, guests
96 may pass arbitrary information to the initial domain.
97 If in doubt, say yes.
98
99config XEN_COMPAT_XENFS
100 bool "Create compatibility mount point /proc/xen"
101 depends on XENFS
102 default y
103 help
104 The old xenstore userspace tools expect to find "xenbus"
105 under /proc/xen, but "xenbus" is now found at the root of the
106 xenfs filesystem. Selecting this causes the kernel to create
Matt LaPlante692105b2009-01-26 11:12:25 +0100107 the compatibility mount point /proc/xen if it is running on
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800108 a xen platform.
109 If in doubt, say yes.
110
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700111config XEN_SYS_HYPERVISOR
112 bool "Create xen entries under /sys/hypervisor"
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800113 depends on SYSFS
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700114 select SYS_HYPERVISOR
115 default y
116 help
117 Create entries under /sys/hypervisor describing the Xen
118 hypervisor environment. When running native or in another
119 virtual environment, /sys/hypervisor will still be present,
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800120 but will have no xen contents.
121
Ian Campbell2de06cc2009-02-09 12:05:51 -0800122config XEN_XENBUS_FRONTEND
Linus Torvalds9c4bc1c2011-01-13 18:46:48 -0800123 tristate
124
Gerd Hoffmannab315232010-12-14 18:40:46 +0000125config XEN_GNTDEV
126 tristate "userspace grant access device driver"
127 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000128 default m
Gerd Hoffmannab315232010-12-14 18:40:46 +0000129 select MMU_NOTIFIER
130 help
131 Allows userspace processes to use grants.
Ian Campbell6bac7f92010-12-10 14:39:15 +0000132
Daniel De Graafdd314052011-02-07 17:23:05 -0500133config XEN_GRANT_DEV_ALLOC
134 tristate "User-space grant reference allocator driver"
135 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000136 default m
Daniel De Graafdd314052011-02-07 17:23:05 -0500137 help
138 Allows userspace processes to create pages with access granted
139 to other domains. This can be used to implement frontend drivers
140 or as part of an inter-domain shared memory channel.
141
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400142config SWIOTLB_XEN
143 def_bool y
Konrad Rzeszutek Wilk27756092010-10-08 11:06:20 -0400144 depends on PCI
145 select SWIOTLB
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400146
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600147config XEN_TMEM
148 bool
Arnd Bergmannf880b672012-10-09 10:33:52 +0000149 depends on !ARM
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600150 default y if (CLEANCACHE || FRONTSWAP)
151 help
152 Shim to interface in-kernel Transcendent Memory hooks
153 (e.g. cleancache and frontswap) to Xen tmem hypercalls.
154
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400155config XEN_PCIDEV_BACKEND
156 tristate "Xen PCI-device backend driver"
157 depends on PCI && X86 && XEN
158 depends on XEN_BACKEND
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400159 default m
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400160 help
161 The PCI device backend driver allows the kernel to export arbitrary
162 PCI devices to other guests. If you select this to be a module, you
163 will need to make sure no other driver has bound to the device(s)
164 you want to make visible to other guests.
165
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400166 The parameter "passthrough" allows you specify how you want the PCI
167 devices to appear in the guest. You can choose the default (0) where
168 PCI topology starts at 00.00.0, or (1) for passthrough if you want
169 the PCI devices topology appear the same as in the host.
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400170
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400171 The "hide" parameter (only applicable if backend driver is compiled
172 into the kernel) allows you to bind the PCI devices to this module
173 from the default device drivers. The argument is the list of PCI BDFs:
174 xen-pciback.hide=(03:00.0)(04:00.0)
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400175
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400176 If in doubt, say m.
Bastian Blankd8414d32011-12-16 11:34:33 -0500177
178config XEN_PRIVCMD
179 tristate
180 depends on XEN
181 default m
182
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500183config XEN_ACPI_PROCESSOR
184 tristate "Xen ACPI processor"
Konrad Rzeszutek Wilkdf7a3ee2012-03-24 09:18:57 -0400185 depends on XEN && X86 && ACPI_PROCESSOR && CPU_FREQ
Konrad Rzeszutek Wilk102b2082012-03-13 13:28:12 -0400186 default m
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500187 help
Andrew Morton1fd14432012-05-04 14:04:12 -0700188 This ACPI processor uploads Power Management information to the Xen
189 hypervisor.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500190
Andrew Morton1fd14432012-05-04 14:04:12 -0700191 To do that the driver parses the Power Management data and uploads
192 said information to the Xen hypervisor. Then the Xen hypervisor can
193 select the proper Cx and Pxx states. It also registers itslef as the
194 SMM so that other drivers (such as ACPI cpufreq scaling driver) will
195 not load.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500196
Andrew Morton1fd14432012-05-04 14:04:12 -0700197 To compile this driver as a module, choose M here: the module will be
198 called xen_acpi_processor If you do not know what to choose, select
199 M here. If the CPUFREQ drivers are built in, select Y here.
Konrad Rzeszutek Wilk59a56802012-02-03 16:03:20 -0500200
Liu, Jinsongcef12ee2012-06-07 19:56:51 +0800201config XEN_MCE_LOG
202 bool "Xen platform mcelog"
203 depends on XEN_DOM0 && X86_64 && X86_MCE
204 default n
205 help
206 Allow kernel fetching MCE error from Xen platform and
207 converting it into Linux mcelog format for mcelog tools
208
Ian Campbellc2374bf2012-10-03 12:17:50 +0100209config XEN_HAVE_PVMMU
210 bool
211
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800212endmenu