2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
10 config LOCKDEP_SUPPORT
14 config STACKTRACE_SUPPORT
18 config RWSEM_GENERIC_SPINLOCK
21 config RWSEM_XCHGADD_ALGORITHM
25 config GENERIC_HWEIGHT
29 config GENERIC_CALIBRATE_DELAY
33 config GENERIC_BUST_SPINLOCK
36 mainmenu "Linux Kernel Configuration"
46 comment "Processor type and features"
51 Select this option if you have a 64 bit IBM zSeries machine
52 and want to use the 64 bit addressing mode.
55 bool "Symmetric multi-processing support"
57 This enables support for systems with more than one CPU. If you have
58 a system with only one CPU, like most personal computers, say N. If
59 you have a system with more than one CPU, say Y.
61 If you say N here, the kernel will run on single and multiprocessor
62 machines, but will use only one CPU of a multiprocessor machine. If
63 you say Y here, the kernel will run on many, but not all,
64 singleprocessor machines. On a singleprocessor machine, the kernel
65 will run faster if you say N here.
67 See also the <file:Documentation/smp.txt> and the SMP-HOWTO
68 available at <http://www.tldp.org/docs.html#howto>.
70 Even if you don't know what to do here, say Y.
73 int "Maximum number of CPUs (2-64)"
78 This allows you to specify the maximum number of CPUs which this
79 kernel will support. The maximum supported value is 64 and the
80 minimum value which makes sense is 2.
82 This is purely to save memory - each supported CPU adds
83 approximately sixteen kilobytes to the kernel image.
86 bool "Support for hot-pluggable CPUs"
91 Say Y here to be able to turn CPUs off and on. CPUs
92 can be controlled through /sys/devices/system/cpu/cpu#.
93 Say N if you want to disable CPU hotplug.
95 config DEFAULT_MIGRATION_COST
100 bool "IEEE FPU emulation"
103 This option is required for IEEE compliant floating point arithmetic
104 on older S/390 machines. Say Y unless you know your machine doesn't
108 bool "Kernel support for 31 bit emulation"
111 Select this option if you want to enable your system kernel to
112 handle system-calls from ELF binaries for 31 bit ESA. This option
113 (and some other stuff like libraries and such) is needed for
114 executing 31 bit applications. It is safe to say "Y".
116 config SYSVIPC_COMPAT
118 depends on COMPAT && SYSVIPC
122 tristate "Kernel support for 31 bit ELF binaries"
125 This allows you to run 32-bit Linux/ELF binaries on your zSeries
126 in 64 bit mode. Everybody wants this; say Y.
128 comment "Code generation options"
131 prompt "Processor type"
135 bool "S/390 model G5 and G6"
138 Select this to build a 31 bit kernel that works
139 on all S/390 and zSeries machines.
142 bool "IBM eServer zSeries model z800 and z900"
144 Select this to optimize for zSeries machines. This
145 will enable some optimizations that are not available
146 on older 31 bit only CPUs.
149 bool "IBM eServer zSeries model z890 and z990"
151 Select this enable optimizations for model z890/z990.
152 This will be slightly faster but does not work on
153 older machines such as the z900.
158 bool "Pack kernel stack"
160 This option enables the compiler option -mkernel-backchain if it
161 is available. If the option is available the compiler supports
162 the new stack layout which dramatically reduces the minimum stack
163 frame size. With an old compiler a non-leaf function needs a
164 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
165 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
166 and 24 byte on 64 bit.
168 Say Y if you are unsure.
171 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
172 depends on PACK_STACK
174 If you say Y here and the compiler supports the -mkernel-backchain
175 option the kernel will use a smaller kernel stack size. For 31 bit
176 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
177 instead of 16kb. This allows to run more thread on a system and
178 reduces the pressure on the memory management for higher order
181 Say N if you are unsure.
185 bool "Detect kernel stack overflow"
187 This option enables the compiler option -mstack-guard and
188 -mstack-size if they are available. If the compiler supports them
189 it will emit additional code to each function prolog to trigger
190 an illegal operation if the kernel stack is about to overflow.
192 Say N if you are unsure.
195 int "Size of the guard area (128-1024)"
197 depends on CHECK_STACK
200 This allows you to specify the size of the guard area at the lower
201 end of the kernel stack. If the kernel stack points into the guard
202 area on function entry an illegal operation is triggered. The size
203 needs to be a power of 2. Please keep in mind that the size of an
204 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
205 The minimum size for the stack guard should be 256 for 31 bit and
209 bool "Emit compiler warnings for function with broken stack usage"
211 This option enables the compiler options -mwarn-framesize and
212 -mwarn-dynamicstack. If the compiler supports these options it
213 will generate warnings for function which either use alloca or
214 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
216 Say N if you are unsure.
218 config WARN_STACK_SIZE
219 int "Maximum frame size considered safe (128-2048)"
221 depends on WARN_STACK
224 This allows you to specify the maximum frame size a function may
225 have without the compiler complaining about it.
229 comment "I/O subsystem configuration"
231 config MACHCHK_WARNING
232 bool "Process warning machine checks"
234 Select this option if you want the machine check handler on IBM S/390 or
235 zSeries to process warning machine checks (e.g. on power failures).
239 tristate "QDIO support"
241 This driver provides the Queued Direct I/O base support for
244 For details please refer to the documentation provided by IBM at
245 <http://www10.software.ibm.com/developerworks/opensource/linux390>
247 To compile this driver as a module, choose M here: the
248 module will be called qdio.
252 config QDIO_PERF_STATS
253 bool "Performance statistics in /proc"
256 Say Y here to get performance statistics in /proc/qdio_perf
261 bool "Extended debugging information"
264 Say Y here to get extended debugging output in
265 /sys/kernel/debug/s390dbf/qdio...
266 Warning: this option reduces the performance of the QDIO module.
273 bool "Preemptible Kernel"
275 This option reduces the latency of the kernel when reacting to
276 real-time or interactive events by allowing a low priority process to
277 be preempted even if it is in kernel mode executing a system call.
278 This allows applications to run more reliably even when the system is
281 Say N if you are unsure.
284 bool "Builtin IPL record support"
286 If you want to use the produced kernel to IPL directly from a
287 device, you have to merge a bootsector specific to the device
288 into the first bytes of the kernel. You will have to select the
292 prompt "IPL method generated into head.S"
296 Select "tape" if you want to IPL the image from a Tape.
298 Select "vm_reader" if you are running under VM/ESA and want
299 to IPL the image from the emulated card reader.
309 source "fs/Kconfig.binfmt"
312 bool "Show crashed user process info"
314 Say Y to print all process fault locations to the console. This is
315 a debugging option; you probably do not want to set it unless you
316 are an S390 port maintainer.
319 bool "Pseudo page fault support"
321 Select this option, if you want to use PFAULT pseudo page fault
322 handling under VM. If running native or in LPAR, this option
323 has no effect. If your VM does not support PFAULT, PAGEEX
324 pseudo page fault handling will be used.
325 Note that VM 4.2 supports PFAULT but has a bug in its
326 implementation that causes some problems.
327 Everybody who wants to run Linux under VM != VM4.2 should select
331 bool "VM shared kernel support"
333 Select this option, if you want to share the text segment of the
334 Linux kernel between different VM guests. This reduces memory
335 usage with lots of guests but greatly increases kernel size.
336 You should only select this option if you know what you are
337 doing and want to exploit this feature.
340 tristate "Cooperative memory management"
342 Select this option, if you want to enable the kernel interface
343 to reduce the memory size of the system. This is accomplished
344 by allocating pages of memory and put them "on hold". This only
345 makes sense for a system running under VM where the unused pages
346 will be reused by VM for other guest systems. The interface
347 allows an external monitor to balance memory of many systems.
348 Everybody who wants to run Linux under VM should select this
352 bool "/proc interface to cooperative memory management"
355 Select this option to enable the /proc interface to the
356 cooperative memory management.
359 bool "IUCV special message interface to cooperative memory management"
360 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
362 Select this option to enable the special message interface to
363 the cooperative memory management.
366 bool "Virtual CPU timer support"
368 This provides a kernel interface for virtual CPU timers.
371 config VIRT_CPU_ACCOUNTING
372 bool "Base user process accounting on virtual cpu timer"
373 depends on VIRT_TIMER
375 Select this option to use CPU timer deltas to do user
379 bool "Linux - VM Monitor Stream, base infrastructure"
380 depends on PROC_FS && VIRT_TIMER=y
382 This provides a kernel interface for creating and updating z/VM APPLDATA
383 monitor records. The monitor records are updated at certain time
384 intervals, once the timer is started.
385 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
386 i.e. enables or disables monitoring on the Linux side.
387 A custom interval value (in seconds) can be written to
388 /proc/appldata/interval.
390 Defaults are 60 seconds interval and timer off.
391 The /proc entries can also be read from, showing the current settings.
394 tristate "Monitor memory management statistics"
395 depends on APPLDATA_BASE
397 This provides memory management related data to the Linux - VM Monitor
398 Stream, like paging/swapping rate, memory utilisation, etc.
399 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
400 APPLDATA monitor record, i.e. enables or disables monitoring this record
404 The /proc entry can also be read from, showing the current settings.
406 This can also be compiled as a module, which will be called
410 tristate "Monitor OS statistics"
411 depends on APPLDATA_BASE
413 This provides OS related data to the Linux - VM Monitor Stream, like
414 CPU utilisation, etc.
415 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
416 APPLDATA monitor record, i.e. enables or disables monitoring this record
420 This can also be compiled as a module, which will be called
423 config APPLDATA_NET_SUM
424 tristate "Monitor overall network statistics"
425 depends on APPLDATA_BASE
427 This provides network related data to the Linux - VM Monitor Stream,
428 currently there is only a total sum of network I/O statistics, no
430 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
431 APPLDATA monitor record, i.e. enables or disables monitoring this record
435 This can also be compiled as a module, which will be called
439 bool "No HZ timer ticks in idle"
441 Switches the regular HZ timer off when the system is going idle.
442 This helps z/VM to detect that the Linux system is idle. VM can
443 then "swap-out" this guest which reduces memory usage. It also
444 reduces the overhead of idle systems.
446 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
447 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
450 config NO_IDLE_HZ_INIT
451 bool "HZ timer in idle off by default"
452 depends on NO_IDLE_HZ
454 The HZ timer is switched off in idle by default. That means the
455 HZ timer is already disabled at boot time.
458 bool "s390 hypervisor file system support"
459 select SYS_HYPERVISOR
462 This is a virtual file system intended to provide accounting
463 information in an s390 hypervisor environment.
466 bool "kexec system call (EXPERIMENTAL)"
467 depends on EXPERIMENTAL
469 kexec is a system call that implements the ability to shutdown your
470 current kernel, and to start another kernel. It is like a reboot
471 but is independent of hardware/microcode support.
481 source "drivers/base/Kconfig"
483 source "drivers/connector/Kconfig"
485 source "drivers/scsi/Kconfig"
487 source "drivers/s390/Kconfig"
489 source "drivers/net/Kconfig"
493 source "arch/s390/oprofile/Kconfig"
495 source "arch/s390/Kconfig.debug"
497 source "security/Kconfig"
499 source "crypto/Kconfig"