2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
10 config RWSEM_GENERIC_SPINLOCK
13 config RWSEM_XCHGADD_ALGORITHM
17 config GENERIC_HWEIGHT
21 config GENERIC_CALIBRATE_DELAY
25 config GENERIC_BUST_SPINLOCK
28 mainmenu "Linux Kernel Configuration"
38 comment "Processor type and features"
43 Select this option if you have a 64 bit IBM zSeries machine
44 and want to use the 64 bit addressing mode.
47 bool "Symmetric multi-processing support"
49 This enables support for systems with more than one CPU. If you have
50 a system with only one CPU, like most personal computers, say N. If
51 you have a system with more than one CPU, say Y.
53 If you say N here, the kernel will run on single and multiprocessor
54 machines, but will use only one CPU of a multiprocessor machine. If
55 you say Y here, the kernel will run on many, but not all,
56 singleprocessor machines. On a singleprocessor machine, the kernel
57 will run faster if you say N here.
59 See also the <file:Documentation/smp.txt> and the SMP-HOWTO
60 available at <http://www.tldp.org/docs.html#howto>.
62 Even if you don't know what to do here, say Y.
65 int "Maximum number of CPUs (2-64)"
70 This allows you to specify the maximum number of CPUs which this
71 kernel will support. The maximum supported value is 64 and the
72 minimum value which makes sense is 2.
74 This is purely to save memory - each supported CPU adds
75 approximately sixteen kilobytes to the kernel image.
78 bool "Support for hot-pluggable CPUs"
83 Say Y here to be able to turn CPUs off and on. CPUs
84 can be controlled through /sys/devices/system/cpu/cpu#.
85 Say N if you want to disable CPU hotplug.
87 config DEFAULT_MIGRATION_COST
92 bool "IEEE FPU emulation"
95 This option is required for IEEE compliant floating point arithmetic
96 on older S/390 machines. Say Y unless you know your machine doesn't
100 bool "Kernel support for 31 bit emulation"
103 Select this option if you want to enable your system kernel to
104 handle system-calls from ELF binaries for 31 bit ESA. This option
105 (and some other stuff like libraries and such) is needed for
106 executing 31 bit applications. It is safe to say "Y".
108 config SYSVIPC_COMPAT
110 depends on COMPAT && SYSVIPC
114 tristate "Kernel support for 31 bit ELF binaries"
117 This allows you to run 32-bit Linux/ELF binaries on your zSeries
118 in 64 bit mode. Everybody wants this; say Y.
120 comment "Code generation options"
123 prompt "Processor type"
127 bool "S/390 model G5 and G6"
130 Select this to build a 31 bit kernel that works
131 on all S/390 and zSeries machines.
134 bool "IBM eServer zSeries model z800 and z900"
136 Select this to optimize for zSeries machines. This
137 will enable some optimizations that are not available
138 on older 31 bit only CPUs.
141 bool "IBM eServer zSeries model z890 and z990"
143 Select this enable optimizations for model z890/z990.
144 This will be slightly faster but does not work on
145 older machines such as the z900.
150 bool "Pack kernel stack"
152 This option enables the compiler option -mkernel-backchain if it
153 is available. If the option is available the compiler supports
154 the new stack layout which dramatically reduces the minimum stack
155 frame size. With an old compiler a non-leaf function needs a
156 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
157 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
158 and 24 byte on 64 bit.
160 Say Y if you are unsure.
163 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
164 depends on PACK_STACK
166 If you say Y here and the compiler supports the -mkernel-backchain
167 option the kernel will use a smaller kernel stack size. For 31 bit
168 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
169 instead of 16kb. This allows to run more thread on a system and
170 reduces the pressure on the memory management for higher order
173 Say N if you are unsure.
177 bool "Detect kernel stack overflow"
179 This option enables the compiler option -mstack-guard and
180 -mstack-size if they are available. If the compiler supports them
181 it will emit additional code to each function prolog to trigger
182 an illegal operation if the kernel stack is about to overflow.
184 Say N if you are unsure.
187 int "Size of the guard area (128-1024)"
189 depends on CHECK_STACK
192 This allows you to specify the size of the guard area at the lower
193 end of the kernel stack. If the kernel stack points into the guard
194 area on function entry an illegal operation is triggered. The size
195 needs to be a power of 2. Please keep in mind that the size of an
196 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
197 The minimum size for the stack guard should be 256 for 31 bit and
201 bool "Emit compiler warnings for function with broken stack usage"
203 This option enables the compiler options -mwarn-framesize and
204 -mwarn-dynamicstack. If the compiler supports these options it
205 will generate warnings for function which either use alloca or
206 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
208 Say N if you are unsure.
210 config WARN_STACK_SIZE
211 int "Maximum frame size considered safe (128-2048)"
213 depends on WARN_STACK
216 This allows you to specify the maximum frame size a function may
217 have without the compiler complaining about it.
221 comment "I/O subsystem configuration"
223 config MACHCHK_WARNING
224 bool "Process warning machine checks"
226 Select this option if you want the machine check handler on IBM S/390 or
227 zSeries to process warning machine checks (e.g. on power failures).
231 tristate "QDIO support"
233 This driver provides the Queued Direct I/O base support for
236 For details please refer to the documentation provided by IBM at
237 <http://www10.software.ibm.com/developerworks/opensource/linux390>
239 To compile this driver as a module, choose M here: the
240 module will be called qdio.
244 config QDIO_PERF_STATS
245 bool "Performance statistics in /proc"
248 Say Y here to get performance statistics in /proc/qdio_perf
253 bool "Extended debugging information"
256 Say Y here to get extended debugging output in
257 /sys/kernel/debug/s390dbf/qdio...
258 Warning: this option reduces the performance of the QDIO module.
265 bool "Preemptible Kernel"
267 This option reduces the latency of the kernel when reacting to
268 real-time or interactive events by allowing a low priority process to
269 be preempted even if it is in kernel mode executing a system call.
270 This allows applications to run more reliably even when the system is
273 Say N if you are unsure.
276 bool "Builtin IPL record support"
278 If you want to use the produced kernel to IPL directly from a
279 device, you have to merge a bootsector specific to the device
280 into the first bytes of the kernel. You will have to select the
284 prompt "IPL method generated into head.S"
288 Select "tape" if you want to IPL the image from a Tape.
290 Select "vm_reader" if you are running under VM/ESA and want
291 to IPL the image from the emulated card reader.
301 source "fs/Kconfig.binfmt"
304 bool "Show crashed user process info"
306 Say Y to print all process fault locations to the console. This is
307 a debugging option; you probably do not want to set it unless you
308 are an S390 port maintainer.
311 bool "Pseudo page fault support"
313 Select this option, if you want to use PFAULT pseudo page fault
314 handling under VM. If running native or in LPAR, this option
315 has no effect. If your VM does not support PFAULT, PAGEEX
316 pseudo page fault handling will be used.
317 Note that VM 4.2 supports PFAULT but has a bug in its
318 implementation that causes some problems.
319 Everybody who wants to run Linux under VM != VM4.2 should select
323 bool "VM shared kernel support"
325 Select this option, if you want to share the text segment of the
326 Linux kernel between different VM guests. This reduces memory
327 usage with lots of guests but greatly increases kernel size.
328 You should only select this option if you know what you are
329 doing and want to exploit this feature.
332 tristate "Cooperative memory management"
334 Select this option, if you want to enable the kernel interface
335 to reduce the memory size of the system. This is accomplished
336 by allocating pages of memory and put them "on hold". This only
337 makes sense for a system running under VM where the unused pages
338 will be reused by VM for other guest systems. The interface
339 allows an external monitor to balance memory of many systems.
340 Everybody who wants to run Linux under VM should select this
344 bool "/proc interface to cooperative memory management"
347 Select this option to enable the /proc interface to the
348 cooperative memory management.
351 bool "IUCV special message interface to cooperative memory management"
352 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
354 Select this option to enable the special message interface to
355 the cooperative memory management.
358 bool "Virtual CPU timer support"
360 This provides a kernel interface for virtual CPU timers.
363 config VIRT_CPU_ACCOUNTING
364 bool "Base user process accounting on virtual cpu timer"
365 depends on VIRT_TIMER
367 Select this option to use CPU timer deltas to do user
371 bool "Linux - VM Monitor Stream, base infrastructure"
372 depends on PROC_FS && VIRT_TIMER=y
374 This provides a kernel interface for creating and updating z/VM APPLDATA
375 monitor records. The monitor records are updated at certain time
376 intervals, once the timer is started.
377 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
378 i.e. enables or disables monitoring on the Linux side.
379 A custom interval value (in seconds) can be written to
380 /proc/appldata/interval.
382 Defaults are 60 seconds interval and timer off.
383 The /proc entries can also be read from, showing the current settings.
386 tristate "Monitor memory management statistics"
387 depends on APPLDATA_BASE
389 This provides memory management related data to the Linux - VM Monitor
390 Stream, like paging/swapping rate, memory utilisation, etc.
391 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
392 APPLDATA monitor record, i.e. enables or disables monitoring this record
396 The /proc entry can also be read from, showing the current settings.
398 This can also be compiled as a module, which will be called
402 tristate "Monitor OS statistics"
403 depends on APPLDATA_BASE
405 This provides OS related data to the Linux - VM Monitor Stream, like
406 CPU utilisation, etc.
407 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
408 APPLDATA monitor record, i.e. enables or disables monitoring this record
412 This can also be compiled as a module, which will be called
415 config APPLDATA_NET_SUM
416 tristate "Monitor overall network statistics"
417 depends on APPLDATA_BASE
419 This provides network related data to the Linux - VM Monitor Stream,
420 currently there is only a total sum of network I/O statistics, no
422 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
423 APPLDATA monitor record, i.e. enables or disables monitoring this record
427 This can also be compiled as a module, which will be called
431 bool "No HZ timer ticks in idle"
433 Switches the regular HZ timer off when the system is going idle.
434 This helps z/VM to detect that the Linux system is idle. VM can
435 then "swap-out" this guest which reduces memory usage. It also
436 reduces the overhead of idle systems.
438 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
439 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
442 config NO_IDLE_HZ_INIT
443 bool "HZ timer in idle off by default"
444 depends on NO_IDLE_HZ
446 The HZ timer is switched off in idle by default. That means the
447 HZ timer is already disabled at boot time.
450 bool "s390 hypervisor file system support"
451 select SYS_HYPERVISOR
454 This is a virtual file system intended to provide accounting
455 information in an s390 hypervisor environment.
458 bool "kexec system call (EXPERIMENTAL)"
459 depends on EXPERIMENTAL
461 kexec is a system call that implements the ability to shutdown your
462 current kernel, and to start another kernel. It is like a reboot
463 but is independent of hardware/microcode support.
473 source "drivers/base/Kconfig"
475 source "drivers/connector/Kconfig"
477 source "drivers/scsi/Kconfig"
479 source "drivers/s390/Kconfig"
481 source "drivers/net/Kconfig"
485 source "arch/s390/oprofile/Kconfig"
487 source "arch/s390/Kconfig.debug"
489 source "security/Kconfig"
491 source "crypto/Kconfig"