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 HAVE_LATENCYTOP_SUPPORT
22 config RWSEM_GENERIC_SPINLOCK
25 config RWSEM_XCHGADD_ALGORITHM
28 config ARCH_HAS_ILOG2_U32
32 config ARCH_HAS_ILOG2_U64
36 config GENERIC_HWEIGHT
53 config GENERIC_LOCKBREAK
56 depends on SMP && PREEMPT
58 mainmenu "Linux Kernel Configuration"
64 select HAVE_KRETPROBES
70 comment "Processor type and features"
75 Select this option if you have a 64 bit IBM zSeries machine
76 and want to use the 64 bit addressing mode.
83 bool "Symmetric multi-processing support"
85 This enables support for systems with more than one CPU. If you have
86 a system with only one CPU, like most personal computers, say N. If
87 you have a system with more than one CPU, say Y.
89 If you say N here, the kernel will run on single and multiprocessor
90 machines, but will use only one CPU of a multiprocessor machine. If
91 you say Y here, the kernel will run on many, but not all,
92 singleprocessor machines. On a singleprocessor machine, the kernel
93 will run faster if you say N here.
95 See also the SMP-HOWTO available at
96 <http://www.tldp.org/docs.html#howto>.
98 Even if you don't know what to do here, say Y.
101 int "Maximum number of CPUs (2-64)"
104 default "32" if !64BIT
105 default "64" if 64BIT
107 This allows you to specify the maximum number of CPUs which this
108 kernel will support. The maximum supported value is 64 and the
109 minimum value which makes sense is 2.
111 This is purely to save memory - each supported CPU adds
112 approximately sixteen kilobytes to the kernel image.
115 bool "Support for hot-pluggable CPUs"
120 Say Y here to be able to turn CPUs off and on. CPUs
121 can be controlled through /sys/devices/system/cpu/cpu#.
122 Say N if you want to disable CPU hotplug.
125 bool "IEEE FPU emulation"
128 This option is required for IEEE compliant floating point arithmetic
129 on older S/390 machines. Say Y unless you know your machine doesn't
133 bool "Kernel support for 31 bit emulation"
136 Select this option if you want to enable your system kernel to
137 handle system-calls from ELF binaries for 31 bit ESA. This option
138 (and some other stuff like libraries and such) is needed for
139 executing 31 bit applications. It is safe to say "Y".
141 config SYSVIPC_COMPAT
143 depends on COMPAT && SYSVIPC
150 config S390_SWITCH_AMODE
151 bool "Switch kernel/user addressing modes"
153 This option allows to switch the addressing modes of kernel and user
154 space. The kernel parameter switch_amode=on will enable this feature,
155 default is disabled. Enabling this (via kernel parameter) on machines
156 earlier than IBM System z9-109 EC/BC will reduce system performance.
158 Note that this option will also be selected by selecting the execute
159 protection option below. Enabling the execute protection via the
160 noexec kernel parameter will also switch the addressing modes,
161 independent of the switch_amode kernel parameter.
164 config S390_EXEC_PROTECT
165 bool "Data execute protection"
166 select S390_SWITCH_AMODE
168 This option allows to enable a buffer overflow protection for user
169 space programs and it also selects the addressing mode option above.
170 The kernel parameter noexec=on will enable this feature and also
171 switch the addressing modes, default is disabled. Enabling this (via
172 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
173 will reduce system performance.
175 comment "Code generation options"
178 prompt "Processor type"
182 bool "S/390 model G5 and G6"
185 Select this to build a 31 bit kernel that works
186 on all S/390 and zSeries machines.
189 bool "IBM eServer zSeries model z800 and z900"
191 Select this to optimize for zSeries machines. This
192 will enable some optimizations that are not available
193 on older 31 bit only CPUs.
196 bool "IBM eServer zSeries model z890 and z990"
198 Select this enable optimizations for model z890/z990.
199 This will be slightly faster but does not work on
200 older machines such as the z900.
205 Select this to enable optimizations for IBM System z9-109, IBM
206 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
207 Class (z9 BC). The kernel will be slightly faster but will not
208 work on older machines such as the z990, z890, z900, and z800.
213 bool "Pack kernel stack"
215 This option enables the compiler option -mkernel-backchain if it
216 is available. If the option is available the compiler supports
217 the new stack layout which dramatically reduces the minimum stack
218 frame size. With an old compiler a non-leaf function needs a
219 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
220 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
221 and 24 byte on 64 bit.
223 Say Y if you are unsure.
226 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
227 depends on PACK_STACK && !LOCKDEP
229 If you say Y here and the compiler supports the -mkernel-backchain
230 option the kernel will use a smaller kernel stack size. For 31 bit
231 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
232 instead of 16kb. This allows to run more thread on a system and
233 reduces the pressure on the memory management for higher order
236 Say N if you are unsure.
240 bool "Detect kernel stack overflow"
242 This option enables the compiler option -mstack-guard and
243 -mstack-size if they are available. If the compiler supports them
244 it will emit additional code to each function prolog to trigger
245 an illegal operation if the kernel stack is about to overflow.
247 Say N if you are unsure.
250 int "Size of the guard area (128-1024)"
252 depends on CHECK_STACK
255 This allows you to specify the size of the guard area at the lower
256 end of the kernel stack. If the kernel stack points into the guard
257 area on function entry an illegal operation is triggered. The size
258 needs to be a power of 2. Please keep in mind that the size of an
259 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
260 The minimum size for the stack guard should be 256 for 31 bit and
264 bool "Emit compiler warnings for function with broken stack usage"
266 This option enables the compiler options -mwarn-framesize and
267 -mwarn-dynamicstack. If the compiler supports these options it
268 will generate warnings for function which either use alloca or
269 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
271 Say N if you are unsure.
273 config WARN_STACK_SIZE
274 int "Maximum frame size considered safe (128-2048)"
276 depends on WARN_STACK
279 This allows you to specify the maximum frame size a function may
280 have without the compiler complaining about it.
282 config ARCH_POPULATES_NODE_MAP
285 comment "Kernel preemption"
287 source "kernel/Kconfig.preempt"
291 comment "I/O subsystem configuration"
293 config MACHCHK_WARNING
294 bool "Process warning machine checks"
296 Select this option if you want the machine check handler on IBM S/390 or
297 zSeries to process warning machine checks (e.g. on power failures).
301 tristate "QDIO support"
303 This driver provides the Queued Direct I/O base support for
306 For details please refer to the documentation provided by IBM at
307 <http://www10.software.ibm.com/developerworks/opensource/linux390>
309 To compile this driver as a module, choose M here: the
310 module will be called qdio.
315 bool "Extended debugging information"
318 Say Y here to get extended debugging output in
319 /sys/kernel/debug/s390dbf/qdio...
320 Warning: this option reduces the performance of the QDIO module.
327 bool "Builtin IPL record support"
329 If you want to use the produced kernel to IPL directly from a
330 device, you have to merge a bootsector specific to the device
331 into the first bytes of the kernel. You will have to select the
335 prompt "IPL method generated into head.S"
339 Select "tape" if you want to IPL the image from a Tape.
341 Select "vm_reader" if you are running under VM/ESA and want
342 to IPL the image from the emulated card reader.
352 source "fs/Kconfig.binfmt"
354 config FORCE_MAX_ZONEORDER
359 bool "Show crashed user process info"
361 Say Y to print all process fault locations to the console. This is
362 a debugging option; you probably do not want to set it unless you
363 are an S390 port maintainer.
366 bool "Pseudo page fault support"
368 Select this option, if you want to use PFAULT pseudo page fault
369 handling under VM. If running native or in LPAR, this option
370 has no effect. If your VM does not support PFAULT, PAGEEX
371 pseudo page fault handling will be used.
372 Note that VM 4.2 supports PFAULT but has a bug in its
373 implementation that causes some problems.
374 Everybody who wants to run Linux under VM != VM4.2 should select
378 bool "VM shared kernel support"
380 Select this option, if you want to share the text segment of the
381 Linux kernel between different VM guests. This reduces memory
382 usage with lots of guests but greatly increases kernel size.
383 Also if a kernel was IPL'ed from a shared segment the kexec system
385 You should only select this option if you know what you are
386 doing and want to exploit this feature.
389 tristate "Cooperative memory management"
391 Select this option, if you want to enable the kernel interface
392 to reduce the memory size of the system. This is accomplished
393 by allocating pages of memory and put them "on hold". This only
394 makes sense for a system running under VM where the unused pages
395 will be reused by VM for other guest systems. The interface
396 allows an external monitor to balance memory of many systems.
397 Everybody who wants to run Linux under VM should select this
401 bool "/proc interface to cooperative memory management"
404 Select this option to enable the /proc interface to the
405 cooperative memory management.
408 bool "IUCV special message interface to cooperative memory management"
409 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
411 Select this option to enable the special message interface to
412 the cooperative memory management.
415 bool "Virtual CPU timer support"
417 This provides a kernel interface for virtual CPU timers.
420 config VIRT_CPU_ACCOUNTING
421 bool "Base user process accounting on virtual cpu timer"
422 depends on VIRT_TIMER
424 Select this option to use CPU timer deltas to do user
428 bool "Linux - VM Monitor Stream, base infrastructure"
429 depends on PROC_FS && VIRT_TIMER=y
431 This provides a kernel interface for creating and updating z/VM APPLDATA
432 monitor records. The monitor records are updated at certain time
433 intervals, once the timer is started.
434 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
435 i.e. enables or disables monitoring on the Linux side.
436 A custom interval value (in seconds) can be written to
437 /proc/appldata/interval.
439 Defaults are 60 seconds interval and timer off.
440 The /proc entries can also be read from, showing the current settings.
443 tristate "Monitor memory management statistics"
444 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
446 This provides memory management related data to the Linux - VM Monitor
447 Stream, like paging/swapping rate, memory utilisation, etc.
448 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
449 APPLDATA monitor record, i.e. enables or disables monitoring this record
453 The /proc entry can also be read from, showing the current settings.
455 This can also be compiled as a module, which will be called
459 tristate "Monitor OS statistics"
460 depends on APPLDATA_BASE
462 This provides OS related data to the Linux - VM Monitor Stream, like
463 CPU utilisation, etc.
464 Writing 1 or 0 to /proc/appldata/os 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 config APPLDATA_NET_SUM
473 tristate "Monitor overall network statistics"
474 depends on APPLDATA_BASE
476 This provides network related data to the Linux - VM Monitor Stream,
477 currently there is only a total sum of network I/O statistics, no
479 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
480 APPLDATA monitor record, i.e. enables or disables monitoring this record
484 This can also be compiled as a module, which will be called
487 source kernel/Kconfig.hz
490 bool "No HZ timer ticks in idle"
492 Switches the regular HZ timer off when the system is going idle.
493 This helps z/VM to detect that the Linux system is idle. VM can
494 then "swap-out" this guest which reduces memory usage. It also
495 reduces the overhead of idle systems.
497 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
498 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
501 config NO_IDLE_HZ_INIT
502 bool "HZ timer in idle off by default"
503 depends on NO_IDLE_HZ
505 The HZ timer is switched off in idle by default. That means the
506 HZ timer is already disabled at boot time.
509 bool "s390 hypervisor file system support"
510 select SYS_HYPERVISOR
513 This is a virtual file system intended to provide accounting
514 information in an s390 hypervisor environment.
517 bool "kexec system call"
519 kexec is a system call that implements the ability to shutdown your
520 current kernel, and to start another kernel. It is like a reboot
521 but is independent of hardware/microcode support.
524 tristate "zfcpdump support"
528 Select this option if you want to build an zfcpdump enabled kernel.
529 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
541 source "drivers/Kconfig"
545 source "arch/s390/Kconfig.debug"
547 source "security/Kconfig"
549 source "crypto/Kconfig"