blob: f815283667affd00f568fd16e8452d11ede21f89 [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"
14 depends on XEN && XEN_BALLOON && CLEANCACHE && SWAP
15 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
74 The evtchn driver allows a userspace process to triger event
75 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"
Alex Zeffertt1107ba82009-01-07 18:07:11 -080089 default y
90 help
91 The xen filesystem provides a way for domains to share
92 information with each other and with the hypervisor.
93 For example, by reading and writing the "xenbus" file, guests
94 may pass arbitrary information to the initial domain.
95 If in doubt, say yes.
96
97config XEN_COMPAT_XENFS
98 bool "Create compatibility mount point /proc/xen"
99 depends on XENFS
100 default y
101 help
102 The old xenstore userspace tools expect to find "xenbus"
103 under /proc/xen, but "xenbus" is now found at the root of the
104 xenfs filesystem. Selecting this causes the kernel to create
Matt LaPlante692105b2009-01-26 11:12:25 +0100105 the compatibility mount point /proc/xen if it is running on
Alex Zeffertt1107ba82009-01-07 18:07:11 -0800106 a xen platform.
107 If in doubt, say yes.
108
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700109config XEN_SYS_HYPERVISOR
110 bool "Create xen entries under /sys/hypervisor"
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800111 depends on SYSFS
Jeremy Fitzhardingecff7e812009-03-10 14:39:59 -0700112 select SYS_HYPERVISOR
113 default y
114 help
115 Create entries under /sys/hypervisor describing the Xen
116 hypervisor environment. When running native or in another
117 virtual environment, /sys/hypervisor will still be present,
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800118 but will have no xen contents.
119
Ian Campbell2de06cc2009-02-09 12:05:51 -0800120config XEN_XENBUS_FRONTEND
Linus Torvalds9c4bc1c2011-01-13 18:46:48 -0800121 tristate
122
Gerd Hoffmannab315232010-12-14 18:40:46 +0000123config XEN_GNTDEV
124 tristate "userspace grant access device driver"
125 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000126 default m
Gerd Hoffmannab315232010-12-14 18:40:46 +0000127 select MMU_NOTIFIER
128 help
129 Allows userspace processes to use grants.
Ian Campbell6bac7f92010-12-10 14:39:15 +0000130
Daniel De Graafdd314052011-02-07 17:23:05 -0500131config XEN_GRANT_DEV_ALLOC
132 tristate "User-space grant reference allocator driver"
133 depends on XEN
Stefano Stabellini1f169f62011-02-10 12:08:21 +0000134 default m
Daniel De Graafdd314052011-02-07 17:23:05 -0500135 help
136 Allows userspace processes to create pages with access granted
137 to other domains. This can be used to implement frontend drivers
138 or as part of an inter-domain shared memory channel.
139
Stefano Stabellini183d03c2010-05-17 17:08:21 +0100140config XEN_PLATFORM_PCI
141 tristate "xen platform pci device driver"
Konrad Rzeszutek Wilke528db52011-01-12 12:58:06 -0500142 depends on XEN_PVHVM && PCI
Stefano Stabellini183d03c2010-05-17 17:08:21 +0100143 default m
144 help
145 Driver for the Xen PCI Platform device: it is responsible for
146 initializing xenbus and grant_table when running in a Xen HVM
147 domain. As a consequence this driver is required to run any Xen PV
148 frontend on Xen HVM.
Linus Torvalds26f0cf92010-08-12 09:09:41 -0700149
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400150config SWIOTLB_XEN
151 def_bool y
Konrad Rzeszutek Wilk27756092010-10-08 11:06:20 -0400152 depends on PCI
153 select SWIOTLB
Konrad Rzeszutek Wilkb0971862010-05-11 10:05:49 -0400154
Dan Magenheimerafec6e02011-06-17 15:06:20 -0600155config XEN_TMEM
156 bool
157 default y if (CLEANCACHE || FRONTSWAP)
158 help
159 Shim to interface in-kernel Transcendent Memory hooks
160 (e.g. cleancache and frontswap) to Xen tmem hypercalls.
161
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400162config XEN_PCIDEV_BACKEND
163 tristate "Xen PCI-device backend driver"
164 depends on PCI && X86 && XEN
165 depends on XEN_BACKEND
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400166 default m
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400167 help
168 The PCI device backend driver allows the kernel to export arbitrary
169 PCI devices to other guests. If you select this to be a module, you
170 will need to make sure no other driver has bound to the device(s)
171 you want to make visible to other guests.
172
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400173 The parameter "passthrough" allows you specify how you want the PCI
174 devices to appear in the guest. You can choose the default (0) where
175 PCI topology starts at 00.00.0, or (1) for passthrough if you want
176 the PCI devices topology appear the same as in the host.
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400177
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400178 The "hide" parameter (only applicable if backend driver is compiled
179 into the kernel) allows you to bind the PCI devices to this module
180 from the default device drivers. The argument is the list of PCI BDFs:
181 xen-pciback.hide=(03:00.0)(04:00.0)
Konrad Rzeszutek Wilk30edc142009-10-13 17:22:20 -0400182
Konrad Rzeszutek Wilk2ebdc422011-07-11 16:49:41 -0400183 If in doubt, say m.
Randy Dunlap27fb7f02010-03-05 13:44:18 -0800184endmenu