debuggers.hg

view linux-2.6.10-xen-sparse/arch/xen/Kconfig @ 3525:c60c0cc29ae0

bitkeeper revision 1.1159.212.26 (41f28aabyam1d9KxJTuTjomL3m7ZlA)

manual merge
author iap10@labyrinth.cl.cam.ac.uk
date Sat Jan 22 17:17:31 2005 +0000 (2005-01-22)
parents 39a7a74fd6f9 834cba8761c6
children bb56e77896e7 2e60786262c4 30ee9c427a5b
line source
1 #
2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
4 #
6 mainmenu "Linux Kernel Configuration"
8 config XEN
9 bool
10 default y
11 help
12 This is the Linux Xen port.
14 config ARCH_XEN
15 bool
16 default y
19 config NO_IDLE_HZ
20 bool
21 default y
24 menu "XEN"
26 config XEN_PRIVILEGED_GUEST
27 bool "Privileged Guest (domain 0)"
28 default n
29 select XEN_PHYSDEV_ACCESS
30 help
31 Support for privileged operation (domain 0)
33 config XEN_PHYSDEV_ACCESS
34 bool "Physical device access"
35 default XEN_PRIVILEGED_GUEST
36 help
37 Assume access is available to physical hardware devices
38 (e.g., hard drives, network cards). This allows you to configure
39 such devices and also includes some low-level support that is
40 otherwise not compiled into the kernel.
42 config XEN_BLKDEV_BACKEND
43 bool "Block-device backend driver"
44 depends on XEN_PHYSDEV_ACCESS
45 default y
46 help
47 The block-device backend driver allows the kernel to export its
48 block devices to other guests via a high-performance shared-memory
49 interface.
51 config XEN_BLKDEV_TAP_BE
52 bool "Block Tap support for backend driver (DANGEROUS)"
53 depends on XEN_BLDEV_BACKEND
54 default n
55 help
56 If you intend to use the block tap driver, the backend domain will
57 not know the domain id of the real frontend, and so will not be able
58 to map its data pages. This modifies the backend to attempt to map
59 from both the tap domain and the real frontend. This presents a
60 security risk, and so should ONLY be used for development
61 with the blktap. This option will be removed as the block drivers are
62 modified to use grant tables.
64 config XEN_NETDEV_BACKEND
65 bool "Network-device backend driver"
66 depends on XEN_PHYSDEV_ACCESS
67 default y
68 help
69 The network-device backend driver allows the kernel to export its
70 network devices to other guests via a high-performance shared-memory
71 interface.
73 config XEN_BLKDEV_FRONTEND
74 bool "Block-device frontend driver"
75 default y
76 help
77 The block-device frontend driver allows the kernel to access block
78 devices mounted within another guest OS. Unless you are building a
79 dedicated device-driver domain, or your master control domain
80 (domain 0), then you almost certainly want to say Y here.
82 config XEN_NETDEV_FRONTEND
83 bool "Network-device frontend driver"
84 default y
85 help
86 The network-device frontend driver allows the kernel to access
87 network interfaces within another guest OS. Unless you are building a
88 dedicated device-driver domain, or your master control domain
89 (domain 0), then you almost certainly want to say Y here.
91 config XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER
92 bool "Pipelined transmitter (DANGEROUS)"
93 depends on XEN_NETDEV_FRONTEND
94 default n
95 help
96 The driver will assume that the backend is pipelining packets for
97 transmission: whenever packets are pending in the remote backend,
98 the driver will not send asynchronous notifications when it queues
99 additional packets for transmission.
100 If the backend is a dumb domain, such as a transparent Ethernet
101 bridge with no local IP interface, it is safe to say Y here to get
102 slightly lower network overhead.
103 If the backend has a local IP interface; or may be doing smart things
104 like reassembling packets to perform firewall filtering; or if you
105 are unsure; or if you experience network hangs when this option is
106 enabled; then you must say N here.
108 config XEN_BLKDEV_TAP
109 bool "Block device tap driver"
110 default n
111 help
112 This driver allows a VM to interact on block device channels
113 to other VMs. Block messages may be passed through or redirected
114 to a character device, allowing device prototyping in application
115 space. Odds are that you want to say N here.
118 config XEN_WRITABLE_PAGETABLES
119 bool
120 default y
122 config XEN_SCRUB_PAGES
123 bool "Scrub memory before freeing it to Xen"
124 default y
125 help
126 Erase memory contents before freeing it back to Xen's global
127 pool. This ensures that any secrets contained within that
128 memory (e.g., private keys) cannot be found by other guests that
129 may be running on the machine. Most people will want to say Y here.
130 If security is not a concern then you may increase performance by
131 saying N.
133 choice
134 prompt "Processor Type"
135 default X86
137 config X86
138 bool "X86"
139 help
140 Choose this option if your computer is a X86 architecture.
142 config X86_64
143 bool "X86_64"
144 help
145 Choose this option if your computer is a X86 architecture.
147 endchoice
149 endmenu
151 config HAVE_ARCH_DEV_ALLOC_SKB
152 bool
153 default y
155 source "init/Kconfig"
157 if X86
158 source "arch/xen/i386/Kconfig"
159 endif
161 menu "Executable file formats"
163 source "fs/Kconfig.binfmt"
165 endmenu
167 source "arch/xen/Kconfig.drivers"
169 source "fs/Kconfig"
171 source "security/Kconfig"
173 source "crypto/Kconfig"
175 source "lib/Kconfig"