direct-io.hg

view linux-2.6-xen-sparse/drivers/xen/Kconfig @ 10691:c3597f7bd8e2

Fix typo in description of XEN_BLKDEV_TAP
Signed-off-by: Horms <horms@verge.net.au>
author kfraser@localhost.localdomain
date Fri Jul 14 11:43:57 2006 +0100 (2006-07-14)
parents 2937703f0ed0
children 4e2eb1947728
line source
1 #
2 # This Kconfig describe xen options
3 #
5 mainmenu "Xen Configuration"
7 config XEN
8 bool
9 default y if X86_XEN || X86_64_XEN
10 help
11 This is the Linux Xen port.
13 if XEN
14 config XEN_INTERFACE_VERSION
15 hex
16 default 0x00030202
18 menu "XEN"
20 config XEN_PRIVILEGED_GUEST
21 bool "Privileged Guest (domain 0)"
22 depends XEN
23 default n
24 help
25 Support for privileged operation (domain 0)
27 config XEN_UNPRIVILEGED_GUEST
28 bool
29 default !XEN_PRIVILEGED_GUEST
31 config XEN_PRIVCMD
32 bool
33 depends on PROC_FS
34 default y
36 config XEN_BACKEND
37 tristate "Backend driver support"
38 default y
39 help
40 Support for backend device drivers that provide I/O services
41 to other virtual machines.
43 config XEN_PCIDEV_BACKEND
44 tristate "PCI device backend driver"
45 depends on PCI && XEN_BACKEND
46 default XEN_PRIVILEGED_GUEST
47 help
48 The PCI device backend driver allows the kernel to export arbitrary
49 PCI devices to other guests. If you select this to be a module, you
50 will need to make sure no other driver has bound to the device(s)
51 you want to make visible to other guests.
53 choice
54 prompt "PCI Backend Mode"
55 depends on XEN_PCIDEV_BACKEND
56 default XEN_PCIDEV_BACKEND_VPCI
58 config XEN_PCIDEV_BACKEND_VPCI
59 bool "Virtual PCI"
60 ---help---
61 This PCI Backend hides the true PCI topology and makes the frontend
62 think there is a single PCI bus with only the exported devices on it.
63 For example, a device at 03:05.0 will be re-assigned to 00:00.0. A
64 second device at 02:1a.0 will be re-assigned to 00:01.0.
66 config XEN_PCIDEV_BACKEND_PASS
67 bool "Passthrough"
68 ---help---
69 This PCI Backend provides a real view of the PCI topology to the
70 frontend (for example, a device at 06:01.b will still appear at
71 06:01.b to the frontend). This is similar to how Xen 2.0.x exposed
72 PCI devices to its driver domains. This may be required for drivers
73 which depend on finding their hardward in certain bus/slot
74 locations.
76 endchoice
78 config XEN_PCIDEV_BE_DEBUG
79 bool "PCI Backend Debugging"
80 depends on XEN_PCIDEV_BACKEND
81 default n
83 config XEN_BLKDEV_BACKEND
84 tristate "Block-device backend driver"
85 depends on XEN_BACKEND
86 default y
87 help
88 The block-device backend driver allows the kernel to export its
89 block devices to other guests via a high-performance shared-memory
90 interface.
92 config XEN_XENBUS_DEV
93 bool
94 depends on PROC_FS
95 default y
97 config XEN_BLKDEV_TAP
98 tristate "Block device tap backend"
99 depends on XEN_BACKEND
100 default XEN_PRIVILEGED_GUEST
101 help
102 The block tap driver is an alternative to the block back driver
103 and allows VM block requests to be redirected to userspace through
104 a device interface. The tap allows user-space development of
105 high-performance block backends, where disk images may be implemented
106 as files, in memory, or on other hosts across the network. This
107 driver can safely coexist with the existing blockback driver.
109 config XEN_NETDEV_BACKEND
110 tristate "Network-device backend driver"
111 depends on XEN_BACKEND && NET
112 default y
113 help
114 The network-device backend driver allows the kernel to export its
115 network devices to other guests via a high-performance shared-memory
116 interface.
118 config XEN_NETDEV_PIPELINED_TRANSMITTER
119 bool "Pipelined transmitter (DANGEROUS)"
120 depends on XEN_NETDEV_BACKEND
121 default n
122 help
123 If the net backend is a dumb domain, such as a transparent Ethernet
124 bridge with no local IP interface, it is safe to say Y here to get
125 slightly lower network overhead.
126 If the backend has a local IP interface; or may be doing smart things
127 like reassembling packets to perform firewall filtering; or if you
128 are unsure; or if you experience network hangs when this option is
129 enabled; then you must say N here.
131 config XEN_NETDEV_LOOPBACK
132 tristate "Network-device loopback driver"
133 depends on XEN_NETDEV_BACKEND
134 default y
135 help
136 A two-interface loopback device to emulate a local netfront-netback
137 connection.
139 config XEN_TPMDEV_BACKEND
140 tristate "TPM-device backend driver"
141 depends on XEN_BACKEND
142 default n
143 help
144 The TPM-device backend driver
146 config XEN_TPMDEV_CLOSE_IF_VTPM_FAILS
147 bool "TPM backend closes upon vTPM failure"
148 depends on XEN_TPMDEV_BACKEND
149 default n
150 help
151 The TPM backend closes the channel if the vTPM in userspace indicates
152 a failure. The corresponding domain's channel will be closed.
153 Say Y if you want this feature.
155 config XEN_BLKDEV_FRONTEND
156 tristate "Block-device frontend driver"
157 depends on XEN
158 default y
159 help
160 The block-device frontend driver allows the kernel to access block
161 devices mounted within another guest OS. Unless you are building a
162 dedicated device-driver domain, or your master control domain
163 (domain 0), then you almost certainly want to say Y here.
165 config XEN_NETDEV_FRONTEND
166 tristate "Network-device frontend driver"
167 depends on XEN && NET
168 default y
169 help
170 The network-device frontend driver allows the kernel to access
171 network interfaces within another guest OS. Unless you are building a
172 dedicated device-driver domain, or your master control domain
173 (domain 0), then you almost certainly want to say Y here.
175 config XEN_SCRUB_PAGES
176 bool "Scrub memory before freeing it to Xen"
177 default y
178 help
179 Erase memory contents before freeing it back to Xen's global
180 pool. This ensures that any secrets contained within that
181 memory (e.g., private keys) cannot be found by other guests that
182 may be running on the machine. Most people will want to say Y here.
183 If security is not a concern then you may increase performance by
184 saying N.
186 config XEN_DISABLE_SERIAL
187 bool "Disable serial port drivers"
188 default y
189 help
190 Disable serial port drivers, allowing the Xen console driver
191 to provide a serial console at ttyS0.
193 config XEN_SYSFS
194 tristate "Export Xen attributes in sysfs"
195 depends on SYSFS
196 default y
197 help
198 Xen hypervisor attributes will show up under /sys/hypervisor/.
200 choice
201 prompt "Xen version compatibility"
202 default XEN_COMPAT_030002_AND_LATER
204 config XEN_COMPAT_030002_AND_LATER
205 bool "3.0.2 and later"
207 config XEN_COMPAT_LATEST_ONLY
208 bool "no compatibility code"
210 endchoice
212 config XEN_COMPAT_030002
213 bool
214 default XEN_COMPAT_030002_AND_LATER
216 endmenu
218 config HAVE_ARCH_ALLOC_SKB
219 bool
220 default y
222 config HAVE_ARCH_DEV_ALLOC_SKB
223 bool
224 default y
226 config HAVE_IRQ_IGNORE_UNHANDLED
227 bool
228 default y
230 config NO_IDLE_HZ
231 bool
232 default y
234 config XEN_UTIL
235 bool
236 default y
238 config XEN_BALLOON
239 bool
240 default y
242 config XEN_DEVMEM
243 bool
244 default y
246 config XEN_SKBUFF
247 bool
248 default y
249 depends on NET
251 config XEN_REBOOT
252 bool
253 default y
255 config XEN_SMPBOOT
256 bool
257 default y
258 depends on SMP
260 endif