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
46 config GENERIC_TIME_VSYSCALL
49 config GENERIC_CLOCKEVENTS
63 config GENERIC_LOCKBREAK
66 depends on SMP && PREEMPT
72 config VIRT_CPU_ACCOUNTING
75 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
78 mainmenu "Linux Kernel Configuration"
82 select USE_GENERIC_SMP_HELPERS if SMP
83 select HAVE_SYSCALL_WRAPPERS
84 select HAVE_FUNCTION_TRACER
85 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
86 select HAVE_FTRACE_MCOUNT_RECORD
87 select HAVE_SYSCALL_TRACEPOINTS
88 select HAVE_DYNAMIC_FTRACE
89 select HAVE_FUNCTION_GRAPH_TRACER
90 select HAVE_DEFAULT_NO_SPIN_MUTEXES
93 select HAVE_KRETPROBES
94 select HAVE_KVM if 64BIT
95 select HAVE_ARCH_TRACEHOOK
96 select INIT_ALL_POSSIBLE
97 select HAVE_PERF_EVENTS
99 config SCHED_OMIT_FRAME_POINTER
103 source "init/Kconfig"
105 source "kernel/Kconfig.freezer"
109 comment "Processor type and features"
111 source "kernel/time/Kconfig"
116 Select this option if you have a 64 bit IBM zSeries machine
117 and want to use the 64 bit addressing mode.
127 bool "Symmetric multi-processing support"
129 This enables support for systems with more than one CPU. If you have
130 a system with only one CPU, like most personal computers, say N. If
131 you have a system with more than one CPU, say Y.
133 If you say N here, the kernel will run on single and multiprocessor
134 machines, but will use only one CPU of a multiprocessor machine. If
135 you say Y here, the kernel will run on many, but not all,
136 singleprocessor machines. On a singleprocessor machine, the kernel
137 will run faster if you say N here.
139 See also the SMP-HOWTO available at
140 <http://www.tldp.org/docs.html#howto>.
142 Even if you don't know what to do here, say Y.
145 int "Maximum number of CPUs (2-64)"
148 default "32" if !64BIT
149 default "64" if 64BIT
151 This allows you to specify the maximum number of CPUs which this
152 kernel will support. The maximum supported value is 64 and the
153 minimum value which makes sense is 2.
155 This is purely to save memory - each supported CPU adds
156 approximately sixteen kilobytes to the kernel image.
159 bool "Support for hot-pluggable CPUs"
164 Say Y here to be able to turn CPUs off and on. CPUs
165 can be controlled through /sys/devices/system/cpu/cpu#.
166 Say N if you want to disable CPU hotplug.
169 bool "IEEE FPU emulation"
172 This option is required for IEEE compliant floating point arithmetic
173 on older S/390 machines. Say Y unless you know your machine doesn't
177 bool "Kernel support for 31 bit emulation"
179 select COMPAT_BINFMT_ELF
181 Select this option if you want to enable your system kernel to
182 handle system-calls from ELF binaries for 31 bit ESA. This option
183 (and some other stuff like libraries and such) is needed for
184 executing 31 bit applications. It is safe to say "Y".
186 config SYSVIPC_COMPAT
188 depends on COMPAT && SYSVIPC
192 def_bool y if COMPAT && KEYS
198 config S390_SWITCH_AMODE
199 bool "Switch kernel/user addressing modes"
201 This option allows to switch the addressing modes of kernel and user
202 space. The kernel parameter switch_amode=on will enable this feature,
203 default is disabled. Enabling this (via kernel parameter) on machines
204 earlier than IBM System z9-109 EC/BC will reduce system performance.
206 Note that this option will also be selected by selecting the execute
207 protection option below. Enabling the execute protection via the
208 noexec kernel parameter will also switch the addressing modes,
209 independent of the switch_amode kernel parameter.
212 config S390_EXEC_PROTECT
213 bool "Data execute protection"
214 select S390_SWITCH_AMODE
216 This option allows to enable a buffer overflow protection for user
217 space programs and it also selects the addressing mode option above.
218 The kernel parameter noexec=on will enable this feature and also
219 switch the addressing modes, default is disabled. Enabling this (via
220 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
221 will reduce system performance.
223 comment "Code generation options"
226 prompt "Processor type"
230 bool "S/390 model G5 and G6"
233 Select this to build a 31 bit kernel that works
234 on all S/390 and zSeries machines.
237 bool "IBM eServer zSeries model z800 and z900"
239 Select this to optimize for zSeries machines. This
240 will enable some optimizations that are not available
241 on older 31 bit only CPUs.
244 bool "IBM eServer zSeries model z890 and z990"
246 Select this enable optimizations for model z890/z990.
247 This will be slightly faster but does not work on
248 older machines such as the z900.
253 Select this to enable optimizations for IBM System z9-109, IBM
254 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
255 Class (z9 BC). The kernel will be slightly faster but will not
256 work on older machines such as the z990, z890, z900, and z800.
259 bool "IBM System z10"
261 Select this to enable optimizations for IBM System z10. The
262 kernel will be slightly faster but will not work on older
263 machines such as the z990, z890, z900, z800, z9-109, z9-ec
269 bool "Pack kernel stack"
271 This option enables the compiler option -mkernel-backchain if it
272 is available. If the option is available the compiler supports
273 the new stack layout which dramatically reduces the minimum stack
274 frame size. With an old compiler a non-leaf function needs a
275 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
276 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
277 and 24 byte on 64 bit.
279 Say Y if you are unsure.
282 bool "Use 8kb for kernel stack instead of 16kb"
283 depends on PACK_STACK && 64BIT && !LOCKDEP
285 If you say Y here and the compiler supports the -mkernel-backchain
286 option the kernel will use a smaller kernel stack size. The reduced
287 size is 8kb instead of 16kb. This allows to run more threads on a
288 system and reduces the pressure on the memory management for higher
289 order page allocations.
291 Say N if you are unsure.
294 bool "Detect kernel stack overflow"
296 This option enables the compiler option -mstack-guard and
297 -mstack-size if they are available. If the compiler supports them
298 it will emit additional code to each function prolog to trigger
299 an illegal operation if the kernel stack is about to overflow.
301 Say N if you are unsure.
304 int "Size of the guard area (128-1024)"
306 depends on CHECK_STACK
309 This allows you to specify the size of the guard area at the lower
310 end of the kernel stack. If the kernel stack points into the guard
311 area on function entry an illegal operation is triggered. The size
312 needs to be a power of 2. Please keep in mind that the size of an
313 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
314 The minimum size for the stack guard should be 256 for 31 bit and
318 bool "Emit compiler warnings for function with broken stack usage"
320 This option enables the compiler options -mwarn-framesize and
321 -mwarn-dynamicstack. If the compiler supports these options it
322 will generate warnings for function which either use alloca or
323 create a stack frame bigger than CONFIG_WARN_STACK_SIZE.
325 Say N if you are unsure.
327 config WARN_STACK_SIZE
328 int "Maximum frame size considered safe (128-2048)"
330 depends on WARN_STACK
333 This allows you to specify the maximum frame size a function may
334 have without the compiler complaining about it.
336 config ARCH_POPULATES_NODE_MAP
339 comment "Kernel preemption"
341 source "kernel/Kconfig.preempt"
343 config ARCH_SPARSEMEM_ENABLE
345 select SPARSEMEM_VMEMMAP_ENABLE
346 select SPARSEMEM_VMEMMAP
347 select SPARSEMEM_STATIC if !64BIT
349 config ARCH_SPARSEMEM_DEFAULT
352 config ARCH_SELECT_MEMORY_MODEL
355 config ARCH_ENABLE_MEMORY_HOTPLUG
359 config ARCH_ENABLE_MEMORY_HOTREMOVE
362 config ARCH_HIBERNATION_POSSIBLE
367 comment "I/O subsystem configuration"
370 tristate "QDIO support"
372 This driver provides the Queued Direct I/O base support for
375 To compile this driver as a module, choose M here: the
376 module will be called qdio.
381 tristate "Support for CHSC subchannels"
383 This driver allows usage of CHSC subchannels. A CHSC subchannel
384 is usually present on LPAR only.
385 The driver creates a device /dev/chsc, which may be used to
386 obtain I/O configuration information about the machine and
387 to issue asynchronous chsc commands (DANGEROUS).
388 You will usually only want to use this interface on a special
389 LPAR designated for system management.
391 To compile this driver as a module, choose M here: the
392 module will be called chsc_sch.
399 bool "Builtin IPL record support"
401 If you want to use the produced kernel to IPL directly from a
402 device, you have to merge a bootsector specific to the device
403 into the first bytes of the kernel. You will have to select the
407 prompt "IPL method generated into head.S"
411 Select "tape" if you want to IPL the image from a Tape.
413 Select "vm_reader" if you are running under VM/ESA and want
414 to IPL the image from the emulated card reader.
424 source "fs/Kconfig.binfmt"
426 config FORCE_MAX_ZONEORDER
431 bool "Show crashed user process info"
433 Say Y to print all process fault locations to the console. This is
434 a debugging option; you probably do not want to set it unless you
435 are an S390 port maintainer.
438 bool "Pseudo page fault support"
440 Select this option, if you want to use PFAULT pseudo page fault
441 handling under VM. If running native or in LPAR, this option
442 has no effect. If your VM does not support PFAULT, PAGEEX
443 pseudo page fault handling will be used.
444 Note that VM 4.2 supports PFAULT but has a bug in its
445 implementation that causes some problems.
446 Everybody who wants to run Linux under VM != VM4.2 should select
450 bool "VM shared kernel support"
452 Select this option, if you want to share the text segment of the
453 Linux kernel between different VM guests. This reduces memory
454 usage with lots of guests but greatly increases kernel size.
455 Also if a kernel was IPL'ed from a shared segment the kexec system
457 You should only select this option if you know what you are
458 doing and want to exploit this feature.
461 tristate "Cooperative memory management"
463 Select this option, if you want to enable the kernel interface
464 to reduce the memory size of the system. This is accomplished
465 by allocating pages of memory and put them "on hold". This only
466 makes sense for a system running under VM where the unused pages
467 will be reused by VM for other guest systems. The interface
468 allows an external monitor to balance memory of many systems.
469 Everybody who wants to run Linux under VM should select this
473 bool "/proc interface to cooperative memory management"
476 Select this option to enable the /proc interface to the
477 cooperative memory management.
480 bool "IUCV special message interface to cooperative memory management"
481 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
483 Select this option to enable the special message interface to
484 the cooperative memory management.
487 bool "Linux - VM Monitor Stream, base infrastructure"
490 This provides a kernel interface for creating and updating z/VM APPLDATA
491 monitor records. The monitor records are updated at certain time
492 intervals, once the timer is started.
493 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
494 i.e. enables or disables monitoring on the Linux side.
495 A custom interval value (in seconds) can be written to
496 /proc/appldata/interval.
498 Defaults are 60 seconds interval and timer off.
499 The /proc entries can also be read from, showing the current settings.
502 tristate "Monitor memory management statistics"
503 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
505 This provides memory management related data to the Linux - VM Monitor
506 Stream, like paging/swapping rate, memory utilisation, etc.
507 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
508 APPLDATA monitor record, i.e. enables or disables monitoring this record
512 The /proc entry can also be read from, showing the current settings.
514 This can also be compiled as a module, which will be called
518 tristate "Monitor OS statistics"
519 depends on APPLDATA_BASE
521 This provides OS related data to the Linux - VM Monitor Stream, like
522 CPU utilisation, etc.
523 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
524 APPLDATA monitor record, i.e. enables or disables monitoring this record
528 This can also be compiled as a module, which will be called
531 config APPLDATA_NET_SUM
532 tristate "Monitor overall network statistics"
533 depends on APPLDATA_BASE && NET
535 This provides network related data to the Linux - VM Monitor Stream,
536 currently there is only a total sum of network I/O statistics, no
538 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
539 APPLDATA monitor record, i.e. enables or disables monitoring this record
543 This can also be compiled as a module, which will be called
546 source kernel/Kconfig.hz
549 bool "s390 hypervisor file system support"
550 select SYS_HYPERVISOR
553 This is a virtual file system intended to provide accounting
554 information in an s390 hypervisor environment.
557 bool "kexec system call"
559 kexec is a system call that implements the ability to shutdown your
560 current kernel, and to start another kernel. It is like a reboot
561 but is independent of hardware/microcode support.
564 bool "zfcpdump support"
568 Select this option if you want to build an zfcpdump enabled kernel.
569 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
572 bool "s390 guest support for KVM (EXPERIMENTAL)"
573 depends on 64BIT && EXPERIMENTAL
576 select VIRTIO_CONSOLE
578 Select this option if you want to run the kernel as a guest under
579 the KVM hypervisor. This will add detection for KVM as well as a
580 virtio transport. If KVM is detected, the virtio console will be
584 bool "Enable seccomp to safely compute untrusted bytecode"
588 This kernel feature is useful for number crunching applications
589 that may need to compute untrusted bytecode during their
590 execution. By using pipes or other transports made available to
591 the process as file descriptors supporting the read/write
592 syscalls, it's possible to isolate those applications in
593 their own address space using seccomp. Once seccomp is
594 enabled via /proc/<pid>/seccomp, it cannot be disabled
595 and the task is only allowed to execute a few safe syscalls
596 defined by each seccomp mode.
602 menu "Power Management"
604 source "kernel/power/Kconfig"
616 source "drivers/Kconfig"
620 source "arch/s390/Kconfig.debug"
622 source "security/Kconfig"
624 source "crypto/Kconfig"
628 source "arch/s390/kvm/Kconfig"