ia64/linux-2.6.18-xen.hg

view drivers/xen/Kconfig @ 562:66faefe721eb

pvSCSI backend driver

Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
author Keir Fraser <keir.fraser@citrix.com>
date Mon Jun 02 09:58:27 2008 +0100 (2008-06-02)
parents fc44fda2c68a
children 3b3701ad4eec
line source
1 #
2 # This Kconfig describe xen options
3 #
5 mainmenu "Xen Configuration"
7 config XEN
8 bool
10 if XEN
11 config XEN_INTERFACE_VERSION
12 hex
13 default 0x00030207
15 menu "XEN"
17 config XEN_PRIVILEGED_GUEST
18 bool "Privileged Guest (domain 0)"
19 help
20 Support for privileged operation (domain 0)
22 config XEN_UNPRIVILEGED_GUEST
23 def_bool !XEN_PRIVILEGED_GUEST
25 config XEN_PRIVCMD
26 def_bool y
27 depends on PROC_FS
29 config XEN_XENBUS_DEV
30 def_bool y
31 depends on PROC_FS
33 config XEN_NETDEV_ACCEL_SFC_UTIL
34 depends on X86
35 tristate
37 config XEN_BACKEND
38 tristate "Backend driver support"
39 default XEN_PRIVILEGED_GUEST
40 help
41 Support for backend device drivers that provide I/O services
42 to other virtual machines.
44 config XEN_BLKDEV_BACKEND
45 tristate "Block-device backend driver"
46 depends on XEN_BACKEND
47 default XEN_BACKEND
48 help
49 The block-device backend driver allows the kernel to export its
50 block devices to other guests via a high-performance shared-memory
51 interface.
53 config XEN_BLKDEV_TAP
54 tristate "Block-device tap backend driver"
55 depends on XEN_BACKEND
56 default XEN_BACKEND
57 help
58 The block tap driver is an alternative to the block back driver
59 and allows VM block requests to be redirected to userspace through
60 a device interface. The tap allows user-space development of
61 high-performance block backends, where disk images may be implemented
62 as files, in memory, or on other hosts across the network. This
63 driver can safely coexist with the existing blockback driver.
65 config XEN_NETDEV_BACKEND
66 tristate "Network-device backend driver"
67 depends on XEN_BACKEND && NET
68 default XEN_BACKEND
69 help
70 The network-device backend driver allows the kernel to export its
71 network devices to other guests via a high-performance shared-memory
72 interface.
74 config XEN_NETDEV_PIPELINED_TRANSMITTER
75 bool "Pipelined transmitter (DANGEROUS)"
76 depends on XEN_NETDEV_BACKEND
77 help
78 If the net backend is a dumb domain, such as a transparent Ethernet
79 bridge with no local IP interface, it is safe to say Y here to get
80 slightly lower network overhead.
81 If the backend has a local IP interface; or may be doing smart things
82 like reassembling packets to perform firewall filtering; or if you
83 are unsure; or if you experience network hangs when this option is
84 enabled; then you must say N here.
86 config XEN_NETDEV_ACCEL_SFC_BACKEND
87 tristate "Network-device backend driver acceleration for Solarflare NICs"
88 depends on XEN_NETDEV_BACKEND && SFC && SFC_RESOURCE && X86
89 select XEN_NETDEV_ACCEL_SFC_UTIL
90 default m
92 config XEN_NETDEV_LOOPBACK
93 tristate "Network-device loopback driver"
94 depends on XEN_NETDEV_BACKEND
95 help
96 A two-interface loopback device to emulate a local netfront-netback
97 connection. If unsure, it is probably safe to say N here.
99 config XEN_PCIDEV_BACKEND
100 tristate "PCI-device backend driver"
101 depends on PCI && XEN_BACKEND
102 default XEN_BACKEND
103 help
104 The PCI device backend driver allows the kernel to export arbitrary
105 PCI devices to other guests. If you select this to be a module, you
106 will need to make sure no other driver has bound to the device(s)
107 you want to make visible to other guests.
109 choice
110 prompt "PCI Backend Mode"
111 depends on XEN_PCIDEV_BACKEND
112 default XEN_PCIDEV_BACKEND_VPCI if !IA64
113 default XEN_PCIDEV_BACKEND_CONTROLLER if IA64
115 config XEN_PCIDEV_BACKEND_VPCI
116 bool "Virtual PCI"
117 ---help---
118 This PCI Backend hides the true PCI topology and makes the frontend
119 think there is a single PCI bus with only the exported devices on it.
120 For example, a device at 03:05.0 will be re-assigned to 00:00.0. A
121 second device at 02:1a.1 will be re-assigned to 00:01.1.
123 config XEN_PCIDEV_BACKEND_PASS
124 bool "Passthrough"
125 ---help---
126 This PCI Backend provides a real view of the PCI topology to the
127 frontend (for example, a device at 06:01.b will still appear at
128 06:01.b to the frontend). This is similar to how Xen 2.0.x exposed
129 PCI devices to its driver domains. This may be required for drivers
130 which depend on finding their hardward in certain bus/slot
131 locations.
133 config XEN_PCIDEV_BACKEND_SLOT
134 bool "Slot"
135 ---help---
136 This PCI Backend hides the true PCI topology and makes the frontend
137 think there is a single PCI bus with only the exported devices on it.
138 Contrary to the virtual PCI backend, a function becomes a new slot.
139 For example, a device at 03:05.2 will be re-assigned to 00:00.0. A
140 second device at 02:1a.1 will be re-assigned to 00:01.0.
142 config XEN_PCIDEV_BACKEND_CONTROLLER
143 bool "Controller"
144 depends on IA64
145 ---help---
146 This PCI backend virtualizes the PCI bus topology by providing a
147 virtual bus per PCI root device. Devices which are physically under
148 the same root bus will appear on the same virtual bus. For systems
149 with complex I/O addressing, this is the only backend which supports
150 extended I/O port spaces and MMIO translation offsets. This backend
151 also supports slot virtualization. For example, a device at
152 0000:01:02.1 will be re-assigned to 0000:00:00.0. A second device
153 at 0000:02:05.0 (behind a P2P bridge on bus 0000:01) will be
154 re-assigned to 0000:00:01.0. A third device at 0000:16:05.0 (under
155 a different PCI root bus) will be re-assigned to 0000:01:00.0.
157 endchoice
159 config XEN_PCIDEV_BE_DEBUG
160 bool "PCI Backend Debugging"
161 depends on XEN_PCIDEV_BACKEND
163 config XEN_TPMDEV_BACKEND
164 tristate "TPM-device backend driver"
165 depends on XEN_BACKEND
166 help
167 The TPM-device backend driver
169 config XEN_SCSI_BACKEND
170 tristate "SCSI backend driver"
171 depends on XEN_BACKEND
172 default n
173 help
174 The SCSI backend driver allows the kernel to export its SCSI Devices
175 to other guests via a high-performance shared-memory interface.
177 config XEN_BLKDEV_FRONTEND
178 tristate "Block-device frontend driver"
179 default m
180 help
181 The block-device frontend driver allows the kernel to access block
182 devices mounted within another guest OS. Unless you are building a
183 dedicated device-driver domain, or your master control domain
184 (domain 0), then you almost certainly want to say Y here.
186 config XEN_NETDEV_FRONTEND
187 tristate "Network-device frontend driver"
188 depends on NET
189 default y
190 help
191 The network-device frontend driver allows the kernel to access
192 network interfaces within another guest OS. Unless you are building a
193 dedicated device-driver domain, or your master control domain
194 (domain 0), then you almost certainly want to say Y here.
196 config XEN_NETDEV_ACCEL_SFC_FRONTEND
197 tristate "Network-device frontend driver acceleration for Solarflare NICs"
198 depends on XEN_NETDEV_FRONTEND && X86
199 select XEN_NETDEV_ACCEL_SFC_UTIL
200 default m
202 config XEN_GRANT_DEV
203 tristate "User-space granted page access driver"
204 default XEN_PRIVILEGED_GUEST
205 help
206 Device for accessing (in user-space) pages that have been granted
207 by other domains.
209 config XEN_FRAMEBUFFER
210 tristate "Framebuffer-device frontend driver"
211 depends on FB
212 select FB_CFB_FILLRECT
213 select FB_CFB_COPYAREA
214 select FB_CFB_IMAGEBLIT
215 default y
216 help
217 The framebuffer-device frontend drivers allows the kernel to create a
218 virtual framebuffer. This framebuffer can be viewed in another
219 domain. Unless this domain has access to a real video card, you
220 probably want to say Y here.
222 config XEN_KEYBOARD
223 tristate "Keyboard-device frontend driver"
224 depends on XEN_FRAMEBUFFER && INPUT
225 default y
226 help
227 The keyboard-device frontend driver allows the kernel to create a
228 virtual keyboard. This keyboard can then be driven by another
229 domain. If you've said Y to CONFIG_XEN_FRAMEBUFFER, you probably
230 want to say Y here.
232 config XEN_SCRUB_PAGES
233 bool "Scrub memory before freeing it to Xen"
234 default y
235 help
236 Erase memory contents before freeing it back to Xen's global
237 pool. This ensures that any secrets contained within that
238 memory (e.g., private keys) cannot be found by other guests that
239 may be running on the machine. Most people will want to say Y here.
240 If security is not a concern then you may increase performance by
241 saying N.
243 config XEN_DISABLE_SERIAL
244 bool "Disable serial port drivers"
245 default y
246 help
247 Disable serial port drivers, allowing the Xen console driver
248 to provide a serial console at ttyS0.
250 config XEN_SYSFS
251 tristate "Export Xen attributes in sysfs"
252 depends on SYSFS
253 select SYS_HYPERVISOR
254 default y
255 help
256 Xen hypervisor attributes will show up under /sys/hypervisor/.
258 choice
259 prompt "Xen version compatibility"
260 default XEN_COMPAT_030002_AND_LATER
262 config XEN_COMPAT_030002_AND_LATER
263 bool "3.0.2 and later"
265 config XEN_COMPAT_030004_AND_LATER
266 bool "3.0.4 and later"
268 config XEN_COMPAT_030100_AND_LATER
269 bool "3.1.0 and later"
271 config XEN_COMPAT_LATEST_ONLY
272 bool "no compatibility code"
274 endchoice
276 config XEN_COMPAT
277 hex
278 default 0xffffff if XEN_COMPAT_LATEST_ONLY
279 default 0x030100 if XEN_COMPAT_030100_AND_LATER
280 default 0x030004 if XEN_COMPAT_030004_AND_LATER
281 default 0x030002 if XEN_COMPAT_030002_AND_LATER
282 default 0
284 endmenu
286 config HAVE_IRQ_IGNORE_UNHANDLED
287 def_bool y
289 config NO_IDLE_HZ
290 def_bool y
292 config XEN_SMPBOOT
293 def_bool y
294 depends on SMP && !PPC_XEN
296 config XEN_BALLOON
297 def_bool y
298 depends on !PPC_XEN
300 config XEN_XENCOMM
301 bool
303 config XEN_DEVMEM
304 def_bool y
306 endif