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
121 comment "Code generation options"
124 prompt "Processor type"
128 bool "S/390 model G5 and G6"
131 Select this to build a 31 bit kernel that works
132 on all S/390 and zSeries machines.
135 bool "IBM eServer zSeries model z800 and z900"
137 Select this to optimize for zSeries machines. This
138 will enable some optimizations that are not available
139 on older 31 bit only CPUs.
142 bool "IBM eServer zSeries model z890 and z990"
144 Select this enable optimizations for model z890/z990.
145 This will be slightly faster but does not work on
146 older machines such as the z900.
151 bool "Pack kernel stack"
153 This option enables the compiler option -mkernel-backchain if it
154 is available. If the option is available the compiler supports
155 the new stack layout which dramatically reduces the minimum stack
156 frame size. With an old compiler a non-leaf function needs a
157 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
158 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
159 and 24 byte on 64 bit.
161 Say Y if you are unsure.
164 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
165 depends on PACK_STACK
167 If you say Y here and the compiler supports the -mkernel-backchain
168 option the kernel will use a smaller kernel stack size. For 31 bit
169 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
170 instead of 16kb. This allows to run more thread on a system and
171 reduces the pressure on the memory management for higher order
174 Say N if you are unsure.
178 bool "Detect kernel stack overflow"
180 This option enables the compiler option -mstack-guard and
181 -mstack-size if they are available. If the compiler supports them
182 it will emit additional code to each function prolog to trigger
183 an illegal operation if the kernel stack is about to overflow.
185 Say N if you are unsure.
188 int "Size of the guard area (128-1024)"
190 depends on CHECK_STACK
193 This allows you to specify the size of the guard area at the lower
194 end of the kernel stack. If the kernel stack points into the guard
195 area on function entry an illegal operation is triggered. The size
196 needs to be a power of 2. Please keep in mind that the size of an
197 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
198 The minimum size for the stack guard should be 256 for 31 bit and
202 bool "Emit compiler warnings for function with broken stack usage"
204 This option enables the compiler options -mwarn-framesize and
205 -mwarn-dynamicstack. If the compiler supports these options it
206 will generate warnings for function which either use alloca or
207 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
209 Say N if you are unsure.
211 config WARN_STACK_SIZE
212 int "Maximum frame size considered safe (128-2048)"
214 depends on WARN_STACK
217 This allows you to specify the maximum frame size a function may
218 have without the compiler complaining about it.
222 comment "I/O subsystem configuration"
224 config MACHCHK_WARNING
225 bool "Process warning machine checks"
227 Select this option if you want the machine check handler on IBM S/390 or
228 zSeries to process warning machine checks (e.g. on power failures).
232 tristate "QDIO support"
234 This driver provides the Queued Direct I/O base support for
237 For details please refer to the documentation provided by IBM at
238 <http://www10.software.ibm.com/developerworks/opensource/linux390>
240 To compile this driver as a module, choose M here: the
241 module will be called qdio.
245 config QDIO_PERF_STATS
246 bool "Performance statistics in /proc"
249 Say Y here to get performance statistics in /proc/qdio_perf
254 bool "Extended debugging information"
257 Say Y here to get extended debugging output in
258 /sys/kernel/debug/s390dbf/qdio...
259 Warning: this option reduces the performance of the QDIO module.
266 bool "Preemptible Kernel"
268 This option reduces the latency of the kernel when reacting to
269 real-time or interactive events by allowing a low priority process to
270 be preempted even if it is in kernel mode executing a system call.
271 This allows applications to run more reliably even when the system is
274 Say N if you are unsure.
277 bool "Builtin IPL record support"
279 If you want to use the produced kernel to IPL directly from a
280 device, you have to merge a bootsector specific to the device
281 into the first bytes of the kernel. You will have to select the
285 prompt "IPL method generated into head.S"
289 Select "tape" if you want to IPL the image from a Tape.
291 Select "vm_reader" if you are running under VM/ESA and want
292 to IPL the image from the emulated card reader.
302 source "fs/Kconfig.binfmt"
305 bool "Show crashed user process info"
307 Say Y to print all process fault locations to the console. This is
308 a debugging option; you probably do not want to set it unless you
309 are an S390 port maintainer.
312 bool "Pseudo page fault support"
314 Select this option, if you want to use PFAULT pseudo page fault
315 handling under VM. If running native or in LPAR, this option
316 has no effect. If your VM does not support PFAULT, PAGEEX
317 pseudo page fault handling will be used.
318 Note that VM 4.2 supports PFAULT but has a bug in its
319 implementation that causes some problems.
320 Everybody who wants to run Linux under VM != VM4.2 should select
324 bool "VM shared kernel support"
326 Select this option, if you want to share the text segment of the
327 Linux kernel between different VM guests. This reduces memory
328 usage with lots of guests but greatly increases kernel size.
329 You should only select this option if you know what you are
330 doing and want to exploit this feature.
333 tristate "Cooperative memory management"
335 Select this option, if you want to enable the kernel interface
336 to reduce the memory size of the system. This is accomplished
337 by allocating pages of memory and put them "on hold". This only
338 makes sense for a system running under VM where the unused pages
339 will be reused by VM for other guest systems. The interface
340 allows an external monitor to balance memory of many systems.
341 Everybody who wants to run Linux under VM should select this
345 bool "/proc interface to cooperative memory management"
348 Select this option to enable the /proc interface to the
349 cooperative memory management.
352 bool "IUCV special message interface to cooperative memory management"
353 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
355 Select this option to enable the special message interface to
356 the cooperative memory management.
359 bool "Virtual CPU timer support"
361 This provides a kernel interface for virtual CPU timers.
364 config VIRT_CPU_ACCOUNTING
365 bool "Base user process accounting on virtual cpu timer"
366 depends on VIRT_TIMER
368 Select this option to use CPU timer deltas to do user
372 bool "Linux - VM Monitor Stream, base infrastructure"
373 depends on PROC_FS && VIRT_TIMER=y
375 This provides a kernel interface for creating and updating z/VM APPLDATA
376 monitor records. The monitor records are updated at certain time
377 intervals, once the timer is started.
378 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
379 i.e. enables or disables monitoring on the Linux side.
380 A custom interval value (in seconds) can be written to
381 /proc/appldata/interval.
383 Defaults are 60 seconds interval and timer off.
384 The /proc entries can also be read from, showing the current settings.
387 tristate "Monitor memory management statistics"
388 depends on APPLDATA_BASE
390 This provides memory management related data to the Linux - VM Monitor
391 Stream, like paging/swapping rate, memory utilisation, etc.
392 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
393 APPLDATA monitor record, i.e. enables or disables monitoring this record
397 The /proc entry can also be read from, showing the current settings.
399 This can also be compiled as a module, which will be called
403 tristate "Monitor OS statistics"
404 depends on APPLDATA_BASE
406 This provides OS related data to the Linux - VM Monitor Stream, like
407 CPU utilisation, etc.
408 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
409 APPLDATA monitor record, i.e. enables or disables monitoring this record
413 This can also be compiled as a module, which will be called
416 config APPLDATA_NET_SUM
417 tristate "Monitor overall network statistics"
418 depends on APPLDATA_BASE
420 This provides network related data to the Linux - VM Monitor Stream,
421 currently there is only a total sum of network I/O statistics, no
423 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
424 APPLDATA monitor record, i.e. enables or disables monitoring this record
428 This can also be compiled as a module, which will be called
432 bool "No HZ timer ticks in idle"
434 Switches the regular HZ timer off when the system is going idle.
435 This helps z/VM to detect that the Linux system is idle. VM can
436 then "swap-out" this guest which reduces memory usage. It also
437 reduces the overhead of idle systems.
439 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
440 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
443 config NO_IDLE_HZ_INIT
444 bool "HZ timer in idle off by default"
445 depends on NO_IDLE_HZ
447 The HZ timer is switched off in idle by default. That means the
448 HZ timer is already disabled at boot time.
451 bool "s390 hypervisor file system support"
452 select SYS_HYPERVISOR
455 This is a virtual file system intended to provide accounting
456 information in an s390 hypervisor environment.
459 bool "kexec system call (EXPERIMENTAL)"
460 depends on EXPERIMENTAL
462 kexec is a system call that implements the ability to shutdown your
463 current kernel, and to start another kernel. It is like a reboot
464 but is independent of hardware/microcode support.
474 source "drivers/base/Kconfig"
476 source "drivers/connector/Kconfig"
478 source "drivers/scsi/Kconfig"
480 source "drivers/s390/Kconfig"
482 source "drivers/net/Kconfig"
486 source "arch/s390/oprofile/Kconfig"
488 source "arch/s390/Kconfig.debug"
490 source "security/Kconfig"
492 source "crypto/Kconfig"