2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
17 config LOCKDEP_SUPPORT
20 config STACKTRACE_SUPPORT
23 config HAVE_LATENCYTOP_SUPPORT
26 config RWSEM_GENERIC_SPINLOCK
29 config RWSEM_XCHGADD_ALGORITHM
32 config ARCH_HAS_ILOG2_U32
36 config ARCH_HAS_ILOG2_U64
40 config GENERIC_HWEIGHT
57 config GENERIC_LOCKBREAK
60 depends on SMP && PREEMPT
62 mainmenu "Linux Kernel Configuration"
68 select HAVE_KRETPROBES
74 comment "Processor type and features"
79 Select this option if you have a 64 bit IBM zSeries machine
80 and want to use the 64 bit addressing mode.
87 bool "Symmetric multi-processing support"
89 This enables support for systems with more than one CPU. If you have
90 a system with only one CPU, like most personal computers, say N. If
91 you have a system with more than one CPU, say Y.
93 If you say N here, the kernel will run on single and multiprocessor
94 machines, but will use only one CPU of a multiprocessor machine. If
95 you say Y here, the kernel will run on many, but not all,
96 singleprocessor machines. On a singleprocessor machine, the kernel
97 will run faster if you say N here.
99 See also the SMP-HOWTO available at
100 <http://www.tldp.org/docs.html#howto>.
102 Even if you don't know what to do here, say Y.
105 int "Maximum number of CPUs (2-64)"
108 default "32" if !64BIT
109 default "64" if 64BIT
111 This allows you to specify the maximum number of CPUs which this
112 kernel will support. The maximum supported value is 64 and the
113 minimum value which makes sense is 2.
115 This is purely to save memory - each supported CPU adds
116 approximately sixteen kilobytes to the kernel image.
119 bool "Support for hot-pluggable CPUs"
124 Say Y here to be able to turn CPUs off and on. CPUs
125 can be controlled through /sys/devices/system/cpu/cpu#.
126 Say N if you want to disable CPU hotplug.
129 bool "IEEE FPU emulation"
132 This option is required for IEEE compliant floating point arithmetic
133 on older S/390 machines. Say Y unless you know your machine doesn't
137 bool "Kernel support for 31 bit emulation"
140 Select this option if you want to enable your system kernel to
141 handle system-calls from ELF binaries for 31 bit ESA. This option
142 (and some other stuff like libraries and such) is needed for
143 executing 31 bit applications. It is safe to say "Y".
145 config SYSVIPC_COMPAT
147 depends on COMPAT && SYSVIPC
154 config S390_SWITCH_AMODE
155 bool "Switch kernel/user addressing modes"
157 This option allows to switch the addressing modes of kernel and user
158 space. The kernel parameter switch_amode=on will enable this feature,
159 default is disabled. Enabling this (via kernel parameter) on machines
160 earlier than IBM System z9-109 EC/BC will reduce system performance.
162 Note that this option will also be selected by selecting the execute
163 protection option below. Enabling the execute protection via the
164 noexec kernel parameter will also switch the addressing modes,
165 independent of the switch_amode kernel parameter.
168 config S390_EXEC_PROTECT
169 bool "Data execute protection"
170 select S390_SWITCH_AMODE
172 This option allows to enable a buffer overflow protection for user
173 space programs and it also selects the addressing mode option above.
174 The kernel parameter noexec=on will enable this feature and also
175 switch the addressing modes, default is disabled. Enabling this (via
176 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
177 will reduce system performance.
179 comment "Code generation options"
182 prompt "Processor type"
186 bool "S/390 model G5 and G6"
189 Select this to build a 31 bit kernel that works
190 on all S/390 and zSeries machines.
193 bool "IBM eServer zSeries model z800 and z900"
195 Select this to optimize for zSeries machines. This
196 will enable some optimizations that are not available
197 on older 31 bit only CPUs.
200 bool "IBM eServer zSeries model z890 and z990"
202 Select this enable optimizations for model z890/z990.
203 This will be slightly faster but does not work on
204 older machines such as the z900.
209 Select this to enable optimizations for IBM System z9-109, IBM
210 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
211 Class (z9 BC). The kernel will be slightly faster but will not
212 work on older machines such as the z990, z890, z900, and z800.
217 bool "Pack kernel stack"
219 This option enables the compiler option -mkernel-backchain if it
220 is available. If the option is available the compiler supports
221 the new stack layout which dramatically reduces the minimum stack
222 frame size. With an old compiler a non-leaf function needs a
223 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
224 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
225 and 24 byte on 64 bit.
227 Say Y if you are unsure.
230 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
231 depends on PACK_STACK && !LOCKDEP
233 If you say Y here and the compiler supports the -mkernel-backchain
234 option the kernel will use a smaller kernel stack size. For 31 bit
235 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
236 instead of 16kb. This allows to run more thread on a system and
237 reduces the pressure on the memory management for higher order
240 Say N if you are unsure.
244 bool "Detect kernel stack overflow"
246 This option enables the compiler option -mstack-guard and
247 -mstack-size if they are available. If the compiler supports them
248 it will emit additional code to each function prolog to trigger
249 an illegal operation if the kernel stack is about to overflow.
251 Say N if you are unsure.
254 int "Size of the guard area (128-1024)"
256 depends on CHECK_STACK
259 This allows you to specify the size of the guard area at the lower
260 end of the kernel stack. If the kernel stack points into the guard
261 area on function entry an illegal operation is triggered. The size
262 needs to be a power of 2. Please keep in mind that the size of an
263 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
264 The minimum size for the stack guard should be 256 for 31 bit and
268 bool "Emit compiler warnings for function with broken stack usage"
270 This option enables the compiler options -mwarn-framesize and
271 -mwarn-dynamicstack. If the compiler supports these options it
272 will generate warnings for function which either use alloca or
273 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
275 Say N if you are unsure.
277 config WARN_STACK_SIZE
278 int "Maximum frame size considered safe (128-2048)"
280 depends on WARN_STACK
283 This allows you to specify the maximum frame size a function may
284 have without the compiler complaining about it.
286 config ARCH_POPULATES_NODE_MAP
289 comment "Kernel preemption"
291 source "kernel/Kconfig.preempt"
295 comment "I/O subsystem configuration"
297 config MACHCHK_WARNING
298 bool "Process warning machine checks"
300 Select this option if you want the machine check handler on IBM S/390 or
301 zSeries to process warning machine checks (e.g. on power failures).
305 tristate "QDIO support"
307 This driver provides the Queued Direct I/O base support for
310 For details please refer to the documentation provided by IBM at
311 <http://www10.software.ibm.com/developerworks/opensource/linux390>
313 To compile this driver as a module, choose M here: the
314 module will be called qdio.
319 bool "Extended debugging information"
322 Say Y here to get extended debugging output in
323 /sys/kernel/debug/s390dbf/qdio...
324 Warning: this option reduces the performance of the QDIO module.
331 bool "Builtin IPL record support"
333 If you want to use the produced kernel to IPL directly from a
334 device, you have to merge a bootsector specific to the device
335 into the first bytes of the kernel. You will have to select the
339 prompt "IPL method generated into head.S"
343 Select "tape" if you want to IPL the image from a Tape.
345 Select "vm_reader" if you are running under VM/ESA and want
346 to IPL the image from the emulated card reader.
356 source "fs/Kconfig.binfmt"
358 config FORCE_MAX_ZONEORDER
363 bool "Show crashed user process info"
365 Say Y to print all process fault locations to the console. This is
366 a debugging option; you probably do not want to set it unless you
367 are an S390 port maintainer.
370 bool "Pseudo page fault support"
372 Select this option, if you want to use PFAULT pseudo page fault
373 handling under VM. If running native or in LPAR, this option
374 has no effect. If your VM does not support PFAULT, PAGEEX
375 pseudo page fault handling will be used.
376 Note that VM 4.2 supports PFAULT but has a bug in its
377 implementation that causes some problems.
378 Everybody who wants to run Linux under VM != VM4.2 should select
382 bool "VM shared kernel support"
384 Select this option, if you want to share the text segment of the
385 Linux kernel between different VM guests. This reduces memory
386 usage with lots of guests but greatly increases kernel size.
387 Also if a kernel was IPL'ed from a shared segment the kexec system
389 You should only select this option if you know what you are
390 doing and want to exploit this feature.
393 tristate "Cooperative memory management"
395 Select this option, if you want to enable the kernel interface
396 to reduce the memory size of the system. This is accomplished
397 by allocating pages of memory and put them "on hold". This only
398 makes sense for a system running under VM where the unused pages
399 will be reused by VM for other guest systems. The interface
400 allows an external monitor to balance memory of many systems.
401 Everybody who wants to run Linux under VM should select this
405 bool "/proc interface to cooperative memory management"
408 Select this option to enable the /proc interface to the
409 cooperative memory management.
412 bool "IUCV special message interface to cooperative memory management"
413 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
415 Select this option to enable the special message interface to
416 the cooperative memory management.
419 bool "Virtual CPU timer support"
421 This provides a kernel interface for virtual CPU timers.
424 config VIRT_CPU_ACCOUNTING
425 bool "Base user process accounting on virtual cpu timer"
426 depends on VIRT_TIMER
428 Select this option to use CPU timer deltas to do user
432 bool "Linux - VM Monitor Stream, base infrastructure"
433 depends on PROC_FS && VIRT_TIMER=y
435 This provides a kernel interface for creating and updating z/VM APPLDATA
436 monitor records. The monitor records are updated at certain time
437 intervals, once the timer is started.
438 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
439 i.e. enables or disables monitoring on the Linux side.
440 A custom interval value (in seconds) can be written to
441 /proc/appldata/interval.
443 Defaults are 60 seconds interval and timer off.
444 The /proc entries can also be read from, showing the current settings.
447 tristate "Monitor memory management statistics"
448 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
450 This provides memory management related data to the Linux - VM Monitor
451 Stream, like paging/swapping rate, memory utilisation, etc.
452 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
453 APPLDATA monitor record, i.e. enables or disables monitoring this record
457 The /proc entry can also be read from, showing the current settings.
459 This can also be compiled as a module, which will be called
463 tristate "Monitor OS statistics"
464 depends on APPLDATA_BASE
466 This provides OS related data to the Linux - VM Monitor Stream, like
467 CPU utilisation, etc.
468 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
469 APPLDATA monitor record, i.e. enables or disables monitoring this record
473 This can also be compiled as a module, which will be called
476 config APPLDATA_NET_SUM
477 tristate "Monitor overall network statistics"
478 depends on APPLDATA_BASE
480 This provides network related data to the Linux - VM Monitor Stream,
481 currently there is only a total sum of network I/O statistics, no
483 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
484 APPLDATA monitor record, i.e. enables or disables monitoring this record
488 This can also be compiled as a module, which will be called
491 source kernel/Kconfig.hz
494 bool "No HZ timer ticks in idle"
496 Switches the regular HZ timer off when the system is going idle.
497 This helps z/VM to detect that the Linux system is idle. VM can
498 then "swap-out" this guest which reduces memory usage. It also
499 reduces the overhead of idle systems.
501 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
502 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
505 config NO_IDLE_HZ_INIT
506 bool "HZ timer in idle off by default"
507 depends on NO_IDLE_HZ
509 The HZ timer is switched off in idle by default. That means the
510 HZ timer is already disabled at boot time.
513 bool "s390 hypervisor file system support"
514 select SYS_HYPERVISOR
517 This is a virtual file system intended to provide accounting
518 information in an s390 hypervisor environment.
521 bool "kexec system call"
523 kexec is a system call that implements the ability to shutdown your
524 current kernel, and to start another kernel. It is like a reboot
525 but is independent of hardware/microcode support.
528 tristate "zfcpdump support"
532 Select this option if you want to build an zfcpdump enabled kernel.
533 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
545 source "drivers/Kconfig"
549 source "arch/s390/Kconfig.debug"
551 source "security/Kconfig"
553 source "crypto/Kconfig"