]>
Commit | Line | Data |
---|---|---|
27fb7f00 RD |
1 | menu "Xen driver support" |
2 | depends on XEN | |
3 | ||
1775826c JF |
4 | config XEN_BALLOON |
5 | bool "Xen memory balloon driver" | |
1775826c JF |
6 | 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 | ||
a50777c7 DM |
12 | config 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. | |
1775826c JF |
28 | |
29 | config XEN_SCRUB_PAGES | |
30 | bool "Scrub pages before returning them to system" | |
31 | depends on XEN_BALLOON | |
32 | default y | |
33 | help | |
34 | Scrub pages before returning them to the system for reuse by | |
35 | other domains. This makes sure that any confidential data | |
36 | is not accidentally visible to other domains. Is it more | |
37 | secure, but slightly less efficient. | |
38 | If in doubt, say yes. | |
1107ba88 | 39 | |
f7116284 IC |
40 | config XEN_DEV_EVTCHN |
41 | tristate "Xen /dev/xen/evtchn device" | |
f7116284 IC |
42 | default y |
43 | help | |
44 | The evtchn driver allows a userspace process to triger event | |
45 | channels and to receive notification of an event channel | |
46 | firing. | |
47 | If in doubt, say yes. | |
48 | ||
df660251 | 49 | config XEN_BACKEND |
329620a8 | 50 | bool "Backend driver support" |
df660251 IC |
51 | depends on XEN_DOM0 |
52 | default y | |
53 | help | |
54 | Support for backend device drivers that provide I/O services | |
55 | to other virtual machines. | |
56 | ||
1107ba88 AZ |
57 | config XENFS |
58 | tristate "Xen filesystem" | |
1107ba88 AZ |
59 | default y |
60 | help | |
61 | The xen filesystem provides a way for domains to share | |
62 | information with each other and with the hypervisor. | |
63 | For example, by reading and writing the "xenbus" file, guests | |
64 | may pass arbitrary information to the initial domain. | |
65 | If in doubt, say yes. | |
66 | ||
67 | config XEN_COMPAT_XENFS | |
68 | bool "Create compatibility mount point /proc/xen" | |
69 | depends on XENFS | |
70 | default y | |
71 | help | |
72 | The old xenstore userspace tools expect to find "xenbus" | |
73 | under /proc/xen, but "xenbus" is now found at the root of the | |
74 | xenfs filesystem. Selecting this causes the kernel to create | |
692105b8 | 75 | the compatibility mount point /proc/xen if it is running on |
1107ba88 AZ |
76 | a xen platform. |
77 | If in doubt, say yes. | |
78 | ||
cff7e81b JF |
79 | config XEN_SYS_HYPERVISOR |
80 | bool "Create xen entries under /sys/hypervisor" | |
27fb7f00 | 81 | depends on SYSFS |
cff7e81b JF |
82 | select SYS_HYPERVISOR |
83 | default y | |
84 | help | |
85 | Create entries under /sys/hypervisor describing the Xen | |
86 | hypervisor environment. When running native or in another | |
87 | virtual environment, /sys/hypervisor will still be present, | |
27fb7f00 RD |
88 | but will have no xen contents. |
89 | ||
2de06cc1 | 90 | config XEN_XENBUS_FRONTEND |
9c4bc1c2 LT |
91 | tristate |
92 | ||
ab31523c GH |
93 | config XEN_GNTDEV |
94 | tristate "userspace grant access device driver" | |
95 | depends on XEN | |
1f169f66 | 96 | default m |
ab31523c GH |
97 | select MMU_NOTIFIER |
98 | help | |
99 | Allows userspace processes to use grants. | |
6bac7f9f | 100 | |
dd314058 DDG |
101 | config XEN_GRANT_DEV_ALLOC |
102 | tristate "User-space grant reference allocator driver" | |
103 | depends on XEN | |
1f169f66 | 104 | default m |
dd314058 DDG |
105 | help |
106 | Allows userspace processes to create pages with access granted | |
107 | to other domains. This can be used to implement frontend drivers | |
108 | or as part of an inter-domain shared memory channel. | |
109 | ||
183d03cc SS |
110 | config XEN_PLATFORM_PCI |
111 | tristate "xen platform pci device driver" | |
e528db5b | 112 | depends on XEN_PVHVM && PCI |
183d03cc SS |
113 | default m |
114 | help | |
115 | Driver for the Xen PCI Platform device: it is responsible for | |
116 | initializing xenbus and grant_table when running in a Xen HVM | |
117 | domain. As a consequence this driver is required to run any Xen PV | |
118 | frontend on Xen HVM. | |
26f0cf91 | 119 | |
b097186f KRW |
120 | config SWIOTLB_XEN |
121 | def_bool y | |
2775609c KRW |
122 | depends on PCI |
123 | select SWIOTLB | |
b097186f | 124 | |
afec6e04 DM |
125 | config XEN_TMEM |
126 | bool | |
127 | default y if (CLEANCACHE || FRONTSWAP) | |
128 | help | |
129 | Shim to interface in-kernel Transcendent Memory hooks | |
130 | (e.g. cleancache and frontswap) to Xen tmem hypercalls. | |
131 | ||
30edc14b KRW |
132 | config XEN_PCIDEV_BACKEND |
133 | tristate "Xen PCI-device backend driver" | |
134 | depends on PCI && X86 && XEN | |
135 | depends on XEN_BACKEND | |
2ebdc426 | 136 | default m |
30edc14b KRW |
137 | help |
138 | The PCI device backend driver allows the kernel to export arbitrary | |
139 | PCI devices to other guests. If you select this to be a module, you | |
140 | will need to make sure no other driver has bound to the device(s) | |
141 | you want to make visible to other guests. | |
142 | ||
2ebdc426 KRW |
143 | The parameter "passthrough" allows you specify how you want the PCI |
144 | devices to appear in the guest. You can choose the default (0) where | |
145 | PCI topology starts at 00.00.0, or (1) for passthrough if you want | |
146 | the PCI devices topology appear the same as in the host. | |
30edc14b | 147 | |
2ebdc426 KRW |
148 | The "hide" parameter (only applicable if backend driver is compiled |
149 | into the kernel) allows you to bind the PCI devices to this module | |
150 | from the default device drivers. The argument is the list of PCI BDFs: | |
151 | xen-pciback.hide=(03:00.0)(04:00.0) | |
30edc14b | 152 | |
2ebdc426 | 153 | If in doubt, say m. |
27fb7f00 | 154 | endmenu |