]> bbs.cooldavid.org Git - net-next-2.6.git/blame - arch/s390/Kconfig
[PATCH] bitops: powerpc: use generic bitops
[net-next-2.6.git] / arch / s390 / Kconfig
CommitLineData
1da177e4
LT
1#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5
6config MMU
7 bool
8 default y
9
10config RWSEM_GENERIC_SPINLOCK
11 bool
12
13config RWSEM_XCHGADD_ALGORITHM
14 bool
15 default y
16
17config GENERIC_CALIBRATE_DELAY
18 bool
19 default y
20
21config GENERIC_BUST_SPINLOCK
22 bool
23
24mainmenu "Linux Kernel Configuration"
25
347a8dc3 26config S390
1da177e4
LT
27 bool
28 default y
29
1da177e4
LT
30source "init/Kconfig"
31
32menu "Base setup"
33
34comment "Processor type and features"
35
347a8dc3 36config 64BIT
1da177e4
LT
37 bool "64 bit kernel"
38 help
39 Select this option if you have a 64 bit IBM zSeries machine
40 and want to use the 64 bit addressing mode.
41
1da177e4
LT
42config SMP
43 bool "Symmetric multi-processing support"
44 ---help---
45 This enables support for systems with more than one CPU. If you have
46 a system with only one CPU, like most personal computers, say N. If
47 you have a system with more than one CPU, say Y.
48
49 If you say N here, the kernel will run on single and multiprocessor
50 machines, but will use only one CPU of a multiprocessor machine. If
51 you say Y here, the kernel will run on many, but not all,
52 singleprocessor machines. On a singleprocessor machine, the kernel
53 will run faster if you say N here.
54
55 See also the <file:Documentation/smp.txt> and the SMP-HOWTO
56 available at <http://www.tldp.org/docs.html#howto>.
57
58 Even if you don't know what to do here, say Y.
59
60config NR_CPUS
61 int "Maximum number of CPUs (2-64)"
62 range 2 64
63 depends on SMP
64 default "32"
65 help
66 This allows you to specify the maximum number of CPUs which this
67 kernel will support. The maximum supported value is 64 and the
68 minimum value which makes sense is 2.
69
70 This is purely to save memory - each supported CPU adds
71 approximately sixteen kilobytes to the kernel image.
72
73config HOTPLUG_CPU
74 bool "Support for hot-pluggable CPUs"
75 depends on SMP
76 select HOTPLUG
77 default n
78 help
79 Say Y here to be able to turn CPUs off and on. CPUs
80 can be controlled through /sys/devices/system/cpu/cpu#.
81 Say N if you want to disable CPU hotplug.
82
4bbf39c2
IM
83config DEFAULT_MIGRATION_COST
84 int
85 default "1000000"
86
1da177e4
LT
87config MATHEMU
88 bool "IEEE FPU emulation"
89 depends on MARCH_G5
90 help
91 This option is required for IEEE compliant floating point arithmetic
92 on older S/390 machines. Say Y unless you know your machine doesn't
93 need this.
94
347a8dc3 95config COMPAT
1da177e4 96 bool "Kernel support for 31 bit emulation"
347a8dc3 97 depends on 64BIT
1da177e4
LT
98 help
99 Select this option if you want to enable your system kernel to
100 handle system-calls from ELF binaries for 31 bit ESA. This option
101 (and some other stuff like libraries and such) is needed for
102 executing 31 bit applications. It is safe to say "Y".
103
1da177e4
LT
104config SYSVIPC_COMPAT
105 bool
106 depends on COMPAT && SYSVIPC
107 default y
108
109config BINFMT_ELF32
110 tristate "Kernel support for 31 bit ELF binaries"
347a8dc3 111 depends on COMPAT
1da177e4
LT
112 help
113 This allows you to run 32-bit Linux/ELF binaries on your zSeries
114 in 64 bit mode. Everybody wants this; say Y.
115
116comment "Code generation options"
117
118choice
119 prompt "Processor type"
120 default MARCH_G5
121
122config MARCH_G5
123 bool "S/390 model G5 and G6"
347a8dc3 124 depends on !64BIT
1da177e4
LT
125 help
126 Select this to build a 31 bit kernel that works
127 on all S/390 and zSeries machines.
128
129config MARCH_Z900
130 bool "IBM eServer zSeries model z800 and z900"
131 help
132 Select this to optimize for zSeries machines. This
133 will enable some optimizations that are not available
134 on older 31 bit only CPUs.
135
136config MARCH_Z990
137 bool "IBM eServer zSeries model z890 and z990"
138 help
139 Select this enable optimizations for model z890/z990.
140 This will be slightly faster but does not work on
141 older machines such as the z900.
142
143endchoice
144
145config PACK_STACK
146 bool "Pack kernel stack"
147 help
148 This option enables the compiler option -mkernel-backchain if it
149 is available. If the option is available the compiler supports
150 the new stack layout which dramatically reduces the minimum stack
151 frame size. With an old compiler a non-leaf function needs a
152 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
153 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
154 and 24 byte on 64 bit.
155
156 Say Y if you are unsure.
157
158config SMALL_STACK
159 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
160 depends on PACK_STACK
161 help
162 If you say Y here and the compiler supports the -mkernel-backchain
163 option the kernel will use a smaller kernel stack size. For 31 bit
164 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
165 instead of 16kb. This allows to run more thread on a system and
166 reduces the pressure on the memory management for higher order
167 page allocations.
168
169 Say N if you are unsure.
170
171
172config CHECK_STACK
173 bool "Detect kernel stack overflow"
174 help
175 This option enables the compiler option -mstack-guard and
176 -mstack-size if they are available. If the compiler supports them
177 it will emit additional code to each function prolog to trigger
178 an illegal operation if the kernel stack is about to overflow.
179
180 Say N if you are unsure.
181
182config STACK_GUARD
183 int "Size of the guard area (128-1024)"
184 range 128 1024
185 depends on CHECK_STACK
186 default "256"
187 help
188 This allows you to specify the size of the guard area at the lower
189 end of the kernel stack. If the kernel stack points into the guard
190 area on function entry an illegal operation is triggered. The size
191 needs to be a power of 2. Please keep in mind that the size of an
192 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
193 The minimum size for the stack guard should be 256 for 31 bit and
194 512 for 64 bit.
195
196config WARN_STACK
197 bool "Emit compiler warnings for function with broken stack usage"
198 help
199 This option enables the compiler options -mwarn-framesize and
200 -mwarn-dynamicstack. If the compiler supports these options it
201 will generate warnings for function which either use alloca or
202 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
203
204 Say N if you are unsure.
205
206config WARN_STACK_SIZE
207 int "Maximum frame size considered safe (128-2048)"
208 range 128 2048
209 depends on WARN_STACK
210 default "256"
211 help
212 This allows you to specify the maximum frame size a function may
213 have without the compiler complaining about it.
214
3f22ab27
DH
215source "mm/Kconfig"
216
1da177e4
LT
217comment "I/O subsystem configuration"
218
219config MACHCHK_WARNING
220 bool "Process warning machine checks"
221 help
222 Select this option if you want the machine check handler on IBM S/390 or
223 zSeries to process warning machine checks (e.g. on power failures).
224 If unsure, say "Y".
225
226config QDIO
227 tristate "QDIO support"
228 ---help---
8129ee16
FP
229 This driver provides the Queued Direct I/O base support for
230 IBM mainframes.
1da177e4
LT
231
232 For details please refer to the documentation provided by IBM at
233 <http://www10.software.ibm.com/developerworks/opensource/linux390>
234
235 To compile this driver as a module, choose M here: the
236 module will be called qdio.
237
238 If unsure, say Y.
239
240config QDIO_PERF_STATS
241 bool "Performance statistics in /proc"
242 depends on QDIO
243 help
244 Say Y here to get performance statistics in /proc/qdio_perf
245
246 If unsure, say N.
247
248config QDIO_DEBUG
249 bool "Extended debugging information"
250 depends on QDIO
251 help
8129ee16
FP
252 Say Y here to get extended debugging output in
253 /sys/kernel/debug/s390dbf/qdio...
1da177e4
LT
254 Warning: this option reduces the performance of the QDIO module.
255
256 If unsure, say N.
257
258comment "Misc"
259
260config PREEMPT
261 bool "Preemptible Kernel"
262 help
263 This option reduces the latency of the kernel when reacting to
264 real-time or interactive events by allowing a low priority process to
265 be preempted even if it is in kernel mode executing a system call.
266 This allows applications to run more reliably even when the system is
267 under load.
268
269 Say N if you are unsure.
270
271config IPL
272 bool "Builtin IPL record support"
273 help
274 If you want to use the produced kernel to IPL directly from a
275 device, you have to merge a bootsector specific to the device
276 into the first bytes of the kernel. You will have to select the
277 IPL device.
278
279choice
280 prompt "IPL method generated into head.S"
281 depends on IPL
282 default IPL_TAPE
283 help
284 Select "tape" if you want to IPL the image from a Tape.
285
286 Select "vm_reader" if you are running under VM/ESA and want
287 to IPL the image from the emulated card reader.
288
289config IPL_TAPE
290 bool "tape"
291
292config IPL_VM
293 bool "vm_reader"
294
295endchoice
296
297source "fs/Kconfig.binfmt"
298
299config PROCESS_DEBUG
300 bool "Show crashed user process info"
301 help
302 Say Y to print all process fault locations to the console. This is
303 a debugging option; you probably do not want to set it unless you
304 are an S390 port maintainer.
305
306config PFAULT
307 bool "Pseudo page fault support"
308 help
309 Select this option, if you want to use PFAULT pseudo page fault
310 handling under VM. If running native or in LPAR, this option
311 has no effect. If your VM does not support PFAULT, PAGEEX
312 pseudo page fault handling will be used.
313 Note that VM 4.2 supports PFAULT but has a bug in its
314 implementation that causes some problems.
315 Everybody who wants to run Linux under VM != VM4.2 should select
316 this option.
317
318config SHARED_KERNEL
319 bool "VM shared kernel support"
320 help
321 Select this option, if you want to share the text segment of the
322 Linux kernel between different VM guests. This reduces memory
323 usage with lots of guests but greatly increases kernel size.
324 You should only select this option if you know what you are
325 doing and want to exploit this feature.
326
327config CMM
328 tristate "Cooperative memory management"
329 help
330 Select this option, if you want to enable the kernel interface
331 to reduce the memory size of the system. This is accomplished
332 by allocating pages of memory and put them "on hold". This only
333 makes sense for a system running under VM where the unused pages
334 will be reused by VM for other guest systems. The interface
335 allows an external monitor to balance memory of many systems.
336 Everybody who wants to run Linux under VM should select this
337 option.
338
339config CMM_PROC
340 bool "/proc interface to cooperative memory management"
341 depends on CMM
342 help
343 Select this option to enable the /proc interface to the
344 cooperative memory management.
345
346config CMM_IUCV
347 bool "IUCV special message interface to cooperative memory management"
348 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
349 help
350 Select this option to enable the special message interface to
351 the cooperative memory management.
352
353config VIRT_TIMER
354 bool "Virtual CPU timer support"
355 help
356 This provides a kernel interface for virtual CPU timers.
357 Default is disabled.
358
359config VIRT_CPU_ACCOUNTING
360 bool "Base user process accounting on virtual cpu timer"
361 depends on VIRT_TIMER
362 help
363 Select this option to use CPU timer deltas to do user
364 process accounting.
365
366config APPLDATA_BASE
367 bool "Linux - VM Monitor Stream, base infrastructure"
368 depends on PROC_FS && VIRT_TIMER=y
369 help
370 This provides a kernel interface for creating and updating z/VM APPLDATA
371 monitor records. The monitor records are updated at certain time
372 intervals, once the timer is started.
373 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
374 i.e. enables or disables monitoring on the Linux side.
375 A custom interval value (in seconds) can be written to
376 /proc/appldata/interval.
377
378 Defaults are 60 seconds interval and timer off.
379 The /proc entries can also be read from, showing the current settings.
380
381config APPLDATA_MEM
382 tristate "Monitor memory management statistics"
383 depends on APPLDATA_BASE
384 help
385 This provides memory management related data to the Linux - VM Monitor
386 Stream, like paging/swapping rate, memory utilisation, etc.
387 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
388 APPLDATA monitor record, i.e. enables or disables monitoring this record
389 on the z/VM side.
390
391 Default is disabled.
392 The /proc entry can also be read from, showing the current settings.
393
394 This can also be compiled as a module, which will be called
395 appldata_mem.o.
396
397config APPLDATA_OS
398 tristate "Monitor OS statistics"
399 depends on APPLDATA_BASE
400 help
401 This provides OS related data to the Linux - VM Monitor Stream, like
402 CPU utilisation, etc.
403 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
404 APPLDATA monitor record, i.e. enables or disables monitoring this record
405 on the z/VM side.
406
407 Default is disabled.
408 This can also be compiled as a module, which will be called
409 appldata_os.o.
410
411config APPLDATA_NET_SUM
412 tristate "Monitor overall network statistics"
413 depends on APPLDATA_BASE
414 help
415 This provides network related data to the Linux - VM Monitor Stream,
416 currently there is only a total sum of network I/O statistics, no
417 per-interface data.
418 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
419 APPLDATA monitor record, i.e. enables or disables monitoring this record
420 on the z/VM side.
421
422 Default is disabled.
423 This can also be compiled as a module, which will be called
424 appldata_net_sum.o.
425
426config NO_IDLE_HZ
427 bool "No HZ timer ticks in idle"
428 help
429 Switches the regular HZ timer off when the system is going idle.
430 This helps z/VM to detect that the Linux system is idle. VM can
431 then "swap-out" this guest which reduces memory usage. It also
432 reduces the overhead of idle systems.
433
434 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
435 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
436 timer is active.
437
438config NO_IDLE_HZ_INIT
439 bool "HZ timer in idle off by default"
440 depends on NO_IDLE_HZ
441 help
442 The HZ timer is switched off in idle by default. That means the
443 HZ timer is already disabled at boot time.
444
cf13f0ea
HC
445config KEXEC
446 bool "kexec system call (EXPERIMENTAL)"
447 depends on EXPERIMENTAL
448 help
449 kexec is a system call that implements the ability to shutdown your
450 current kernel, and to start another kernel. It is like a reboot
451 but is independent of hardware/microcode support.
452
1da177e4
LT
453endmenu
454
d5950b43
SR
455source "net/Kconfig"
456
1da177e4
LT
457config PCMCIA
458 bool
459 default n
460
461source "drivers/base/Kconfig"
462
61d3ad0e
MS
463source "drivers/connector/Kconfig"
464
1da177e4
LT
465source "drivers/scsi/Kconfig"
466
467source "drivers/s390/Kconfig"
468
d5950b43 469source "drivers/net/Kconfig"
1da177e4
LT
470
471source "fs/Kconfig"
472
473source "arch/s390/oprofile/Kconfig"
474
475source "arch/s390/Kconfig.debug"
476
477source "security/Kconfig"
478
479source "crypto/Kconfig"
480
481source "lib/Kconfig"