2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
13 config LOCKDEP_SUPPORT
16 config STACKTRACE_SUPPORT
19 config RWSEM_GENERIC_SPINLOCK
22 config RWSEM_XCHGADD_ALGORITHM
25 config ARCH_HAS_ILOG2_U32
29 config ARCH_HAS_ILOG2_U64
33 config GENERIC_HWEIGHT
50 mainmenu "Linux Kernel Configuration"
60 comment "Processor type and features"
65 Select this option if you have a 64 bit IBM zSeries machine
66 and want to use the 64 bit addressing mode.
73 bool "Symmetric multi-processing support"
75 This enables support for systems with more than one CPU. If you have
76 a system with only one CPU, like most personal computers, say N. If
77 you have a system with more than one CPU, say Y.
79 If you say N here, the kernel will run on single and multiprocessor
80 machines, but will use only one CPU of a multiprocessor machine. If
81 you say Y here, the kernel will run on many, but not all,
82 singleprocessor machines. On a singleprocessor machine, the kernel
83 will run faster if you say N here.
85 See also the <file:Documentation/smp.txt> and the SMP-HOWTO
86 available at <http://www.tldp.org/docs.html#howto>.
88 Even if you don't know what to do here, say Y.
91 int "Maximum number of CPUs (2-64)"
96 This allows you to specify the maximum number of CPUs which this
97 kernel will support. The maximum supported value is 64 and the
98 minimum value which makes sense is 2.
100 This is purely to save memory - each supported CPU adds
101 approximately sixteen kilobytes to the kernel image.
104 bool "Support for hot-pluggable CPUs"
109 Say Y here to be able to turn CPUs off and on. CPUs
110 can be controlled through /sys/devices/system/cpu/cpu#.
111 Say N if you want to disable CPU hotplug.
114 bool "IEEE FPU emulation"
117 This option is required for IEEE compliant floating point arithmetic
118 on older S/390 machines. Say Y unless you know your machine doesn't
122 bool "Kernel support for 31 bit emulation"
125 Select this option if you want to enable your system kernel to
126 handle system-calls from ELF binaries for 31 bit ESA. This option
127 (and some other stuff like libraries and such) is needed for
128 executing 31 bit applications. It is safe to say "Y".
130 config SYSVIPC_COMPAT
132 depends on COMPAT && SYSVIPC
139 config S390_SWITCH_AMODE
140 bool "Switch kernel/user addressing modes"
142 This option allows to switch the addressing modes of kernel and user
143 space. The kernel parameter switch_amode=on will enable this feature,
144 default is disabled. Enabling this (via kernel parameter) on machines
145 earlier than IBM System z9-109 EC/BC will reduce system performance.
147 Note that this option will also be selected by selecting the execute
148 protection option below. Enabling the execute protection via the
149 noexec kernel parameter will also switch the addressing modes,
150 independent of the switch_amode kernel parameter.
153 config S390_EXEC_PROTECT
154 bool "Data execute protection"
155 select S390_SWITCH_AMODE
157 This option allows to enable a buffer overflow protection for user
158 space programs and it also selects the addressing mode option above.
159 The kernel parameter noexec=on will enable this feature and also
160 switch the addressing modes, default is disabled. Enabling this (via
161 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
162 will reduce system performance.
164 comment "Code generation options"
167 prompt "Processor type"
171 bool "S/390 model G5 and G6"
174 Select this to build a 31 bit kernel that works
175 on all S/390 and zSeries machines.
178 bool "IBM eServer zSeries model z800 and z900"
180 Select this to optimize for zSeries machines. This
181 will enable some optimizations that are not available
182 on older 31 bit only CPUs.
185 bool "IBM eServer zSeries model z890 and z990"
187 Select this enable optimizations for model z890/z990.
188 This will be slightly faster but does not work on
189 older machines such as the z900.
194 Select this to enable optimizations for IBM System z9-109, IBM
195 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
196 Class (z9 BC). The kernel will be slightly faster but will not
197 work on older machines such as the z990, z890, z900, and z800.
202 bool "Pack kernel stack"
204 This option enables the compiler option -mkernel-backchain if it
205 is available. If the option is available the compiler supports
206 the new stack layout which dramatically reduces the minimum stack
207 frame size. With an old compiler a non-leaf function needs a
208 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
209 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
210 and 24 byte on 64 bit.
212 Say Y if you are unsure.
215 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
216 depends on PACK_STACK && !LOCKDEP
218 If you say Y here and the compiler supports the -mkernel-backchain
219 option the kernel will use a smaller kernel stack size. For 31 bit
220 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
221 instead of 16kb. This allows to run more thread on a system and
222 reduces the pressure on the memory management for higher order
225 Say N if you are unsure.
229 bool "Detect kernel stack overflow"
231 This option enables the compiler option -mstack-guard and
232 -mstack-size if they are available. If the compiler supports them
233 it will emit additional code to each function prolog to trigger
234 an illegal operation if the kernel stack is about to overflow.
236 Say N if you are unsure.
239 int "Size of the guard area (128-1024)"
241 depends on CHECK_STACK
244 This allows you to specify the size of the guard area at the lower
245 end of the kernel stack. If the kernel stack points into the guard
246 area on function entry an illegal operation is triggered. The size
247 needs to be a power of 2. Please keep in mind that the size of an
248 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
249 The minimum size for the stack guard should be 256 for 31 bit and
253 bool "Emit compiler warnings for function with broken stack usage"
255 This option enables the compiler options -mwarn-framesize and
256 -mwarn-dynamicstack. If the compiler supports these options it
257 will generate warnings for function which either use alloca or
258 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
260 Say N if you are unsure.
262 config WARN_STACK_SIZE
263 int "Maximum frame size considered safe (128-2048)"
265 depends on WARN_STACK
268 This allows you to specify the maximum frame size a function may
269 have without the compiler complaining about it.
271 config ARCH_POPULATES_NODE_MAP
274 comment "Kernel preemption"
276 source "kernel/Kconfig.preempt"
280 comment "I/O subsystem configuration"
282 config MACHCHK_WARNING
283 bool "Process warning machine checks"
285 Select this option if you want the machine check handler on IBM S/390 or
286 zSeries to process warning machine checks (e.g. on power failures).
290 tristate "QDIO support"
292 This driver provides the Queued Direct I/O base support for
295 For details please refer to the documentation provided by IBM at
296 <http://www10.software.ibm.com/developerworks/opensource/linux390>
298 To compile this driver as a module, choose M here: the
299 module will be called qdio.
304 bool "Extended debugging information"
307 Say Y here to get extended debugging output in
308 /sys/kernel/debug/s390dbf/qdio...
309 Warning: this option reduces the performance of the QDIO module.
316 bool "Builtin IPL record support"
318 If you want to use the produced kernel to IPL directly from a
319 device, you have to merge a bootsector specific to the device
320 into the first bytes of the kernel. You will have to select the
324 prompt "IPL method generated into head.S"
328 Select "tape" if you want to IPL the image from a Tape.
330 Select "vm_reader" if you are running under VM/ESA and want
331 to IPL the image from the emulated card reader.
341 source "fs/Kconfig.binfmt"
344 bool "Show crashed user process info"
346 Say Y to print all process fault locations to the console. This is
347 a debugging option; you probably do not want to set it unless you
348 are an S390 port maintainer.
351 bool "Pseudo page fault support"
353 Select this option, if you want to use PFAULT pseudo page fault
354 handling under VM. If running native or in LPAR, this option
355 has no effect. If your VM does not support PFAULT, PAGEEX
356 pseudo page fault handling will be used.
357 Note that VM 4.2 supports PFAULT but has a bug in its
358 implementation that causes some problems.
359 Everybody who wants to run Linux under VM != VM4.2 should select
363 bool "VM shared kernel support"
365 Select this option, if you want to share the text segment of the
366 Linux kernel between different VM guests. This reduces memory
367 usage with lots of guests but greatly increases kernel size.
368 Also if a kernel was IPL'ed from a shared segment the kexec system
370 You should only select this option if you know what you are
371 doing and want to exploit this feature.
374 tristate "Cooperative memory management"
376 Select this option, if you want to enable the kernel interface
377 to reduce the memory size of the system. This is accomplished
378 by allocating pages of memory and put them "on hold". This only
379 makes sense for a system running under VM where the unused pages
380 will be reused by VM for other guest systems. The interface
381 allows an external monitor to balance memory of many systems.
382 Everybody who wants to run Linux under VM should select this
386 bool "/proc interface to cooperative memory management"
389 Select this option to enable the /proc interface to the
390 cooperative memory management.
393 bool "IUCV special message interface to cooperative memory management"
394 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
396 Select this option to enable the special message interface to
397 the cooperative memory management.
400 bool "Virtual CPU timer support"
402 This provides a kernel interface for virtual CPU timers.
405 config VIRT_CPU_ACCOUNTING
406 bool "Base user process accounting on virtual cpu timer"
407 depends on VIRT_TIMER
409 Select this option to use CPU timer deltas to do user
413 bool "Linux - VM Monitor Stream, base infrastructure"
414 depends on PROC_FS && VIRT_TIMER=y
416 This provides a kernel interface for creating and updating z/VM APPLDATA
417 monitor records. The monitor records are updated at certain time
418 intervals, once the timer is started.
419 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
420 i.e. enables or disables monitoring on the Linux side.
421 A custom interval value (in seconds) can be written to
422 /proc/appldata/interval.
424 Defaults are 60 seconds interval and timer off.
425 The /proc entries can also be read from, showing the current settings.
428 tristate "Monitor memory management statistics"
429 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
431 This provides memory management related data to the Linux - VM Monitor
432 Stream, like paging/swapping rate, memory utilisation, etc.
433 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
434 APPLDATA monitor record, i.e. enables or disables monitoring this record
438 The /proc entry can also be read from, showing the current settings.
440 This can also be compiled as a module, which will be called
444 tristate "Monitor OS statistics"
445 depends on APPLDATA_BASE
447 This provides OS related data to the Linux - VM Monitor Stream, like
448 CPU utilisation, etc.
449 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
450 APPLDATA monitor record, i.e. enables or disables monitoring this record
454 This can also be compiled as a module, which will be called
457 config APPLDATA_NET_SUM
458 tristate "Monitor overall network statistics"
459 depends on APPLDATA_BASE
461 This provides network related data to the Linux - VM Monitor Stream,
462 currently there is only a total sum of network I/O statistics, no
464 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
465 APPLDATA monitor record, i.e. enables or disables monitoring this record
469 This can also be compiled as a module, which will be called
472 source kernel/Kconfig.hz
475 bool "No HZ timer ticks in idle"
477 Switches the regular HZ timer off when the system is going idle.
478 This helps z/VM to detect that the Linux system is idle. VM can
479 then "swap-out" this guest which reduces memory usage. It also
480 reduces the overhead of idle systems.
482 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
483 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
486 config NO_IDLE_HZ_INIT
487 bool "HZ timer in idle off by default"
488 depends on NO_IDLE_HZ
490 The HZ timer is switched off in idle by default. That means the
491 HZ timer is already disabled at boot time.
494 bool "s390 hypervisor file system support"
495 select SYS_HYPERVISOR
498 This is a virtual file system intended to provide accounting
499 information in an s390 hypervisor environment.
502 bool "kexec system call"
504 kexec is a system call that implements the ability to shutdown your
505 current kernel, and to start another kernel. It is like a reboot
506 but is independent of hardware/microcode support.
509 tristate "zfcpdump support"
513 Select this option if you want to build an zfcpdump enabled kernel.
514 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
526 source "drivers/Kconfig"
530 source "kernel/Kconfig.instrumentation"
532 source "arch/s390/Kconfig.debug"
534 source "security/Kconfig"
536 source "crypto/Kconfig"