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
195 config S390_SWITCH_AMODE
196 bool "Switch kernel/user addressing modes"
198 This option allows to switch the addressing modes of kernel and user
199 space. The kernel parameter switch_amode=on will enable this feature,
200 default is disabled. Enabling this (via kernel parameter) on machines
201 earlier than IBM System z9-109 EC/BC will reduce system performance.
203 Note that this option will also be selected by selecting the execute
204 protection option below. Enabling the execute protection via the
205 noexec kernel parameter will also switch the addressing modes,
206 independent of the switch_amode kernel parameter.
209 config S390_EXEC_PROTECT
210 bool "Data execute protection"
211 select S390_SWITCH_AMODE
213 This option allows to enable a buffer overflow protection for user
214 space programs and it also selects the addressing mode option above.
215 The kernel parameter noexec=on will enable this feature and also
216 switch the addressing modes, default is disabled. Enabling this (via
217 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
218 will reduce system performance.
220 comment "Code generation options"
223 prompt "Processor type"
227 bool "S/390 model G5 and G6"
230 Select this to build a 31 bit kernel that works
231 on all S/390 and zSeries machines.
234 bool "IBM eServer zSeries model z800 and z900"
236 Select this to optimize for zSeries machines. This
237 will enable some optimizations that are not available
238 on older 31 bit only CPUs.
241 bool "IBM eServer zSeries model z890 and z990"
243 Select this enable optimizations for model z890/z990.
244 This will be slightly faster but does not work on
245 older machines such as the z900.
250 Select this to enable optimizations for IBM System z9-109, IBM
251 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
252 Class (z9 BC). The kernel will be slightly faster but will not
253 work on older machines such as the z990, z890, z900, and z800.
256 bool "IBM System z10"
258 Select this to enable optimizations for IBM System z10. The
259 kernel will be slightly faster but will not work on older
260 machines such as the z990, z890, z900, z800, z9-109, z9-ec
266 bool "Pack kernel stack"
268 This option enables the compiler option -mkernel-backchain if it
269 is available. If the option is available the compiler supports
270 the new stack layout which dramatically reduces the minimum stack
271 frame size. With an old compiler a non-leaf function needs a
272 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
273 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
274 and 24 byte on 64 bit.
276 Say Y if you are unsure.
279 bool "Use 8kb for kernel stack instead of 16kb"
280 depends on PACK_STACK && 64BIT && !LOCKDEP
282 If you say Y here and the compiler supports the -mkernel-backchain
283 option the kernel will use a smaller kernel stack size. The reduced
284 size is 8kb instead of 16kb. This allows to run more threads on a
285 system and reduces the pressure on the memory management for higher
286 order page allocations.
288 Say N if you are unsure.
291 bool "Detect kernel stack overflow"
293 This option enables the compiler option -mstack-guard and
294 -mstack-size if they are available. If the compiler supports them
295 it will emit additional code to each function prolog to trigger
296 an illegal operation if the kernel stack is about to overflow.
298 Say N if you are unsure.
301 int "Size of the guard area (128-1024)"
303 depends on CHECK_STACK
306 This allows you to specify the size of the guard area at the lower
307 end of the kernel stack. If the kernel stack points into the guard
308 area on function entry an illegal operation is triggered. The size
309 needs to be a power of 2. Please keep in mind that the size of an
310 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
311 The minimum size for the stack guard should be 256 for 31 bit and
315 bool "Emit compiler warnings for function with broken stack usage"
317 This option enables the compiler options -mwarn-framesize and
318 -mwarn-dynamicstack. If the compiler supports these options it
319 will generate warnings for function which either use alloca or
320 create a stack frame bigger than CONFIG_WARN_STACK_SIZE.
322 Say N if you are unsure.
324 config WARN_STACK_SIZE
325 int "Maximum frame size considered safe (128-2048)"
327 depends on WARN_STACK
330 This allows you to specify the maximum frame size a function may
331 have without the compiler complaining about it.
333 config ARCH_POPULATES_NODE_MAP
336 comment "Kernel preemption"
338 source "kernel/Kconfig.preempt"
340 config ARCH_SPARSEMEM_ENABLE
342 select SPARSEMEM_VMEMMAP_ENABLE
343 select SPARSEMEM_VMEMMAP
344 select SPARSEMEM_STATIC if !64BIT
346 config ARCH_SPARSEMEM_DEFAULT
349 config ARCH_SELECT_MEMORY_MODEL
352 config ARCH_ENABLE_MEMORY_HOTPLUG
356 config ARCH_ENABLE_MEMORY_HOTREMOVE
359 config ARCH_HIBERNATION_POSSIBLE
364 comment "I/O subsystem configuration"
367 tristate "QDIO support"
369 This driver provides the Queued Direct I/O base support for
372 To compile this driver as a module, choose M here: the
373 module will be called qdio.
378 tristate "Support for CHSC subchannels"
380 This driver allows usage of CHSC subchannels. A CHSC subchannel
381 is usually present on LPAR only.
382 The driver creates a device /dev/chsc, which may be used to
383 obtain I/O configuration information about the machine and
384 to issue asynchronous chsc commands (DANGEROUS).
385 You will usually only want to use this interface on a special
386 LPAR designated for system management.
388 To compile this driver as a module, choose M here: the
389 module will be called chsc_sch.
396 bool "Builtin IPL record support"
398 If you want to use the produced kernel to IPL directly from a
399 device, you have to merge a bootsector specific to the device
400 into the first bytes of the kernel. You will have to select the
404 prompt "IPL method generated into head.S"
408 Select "tape" if you want to IPL the image from a Tape.
410 Select "vm_reader" if you are running under VM/ESA and want
411 to IPL the image from the emulated card reader.
421 source "fs/Kconfig.binfmt"
423 config FORCE_MAX_ZONEORDER
428 bool "Show crashed user process info"
430 Say Y to print all process fault locations to the console. This is
431 a debugging option; you probably do not want to set it unless you
432 are an S390 port maintainer.
435 bool "Pseudo page fault support"
437 Select this option, if you want to use PFAULT pseudo page fault
438 handling under VM. If running native or in LPAR, this option
439 has no effect. If your VM does not support PFAULT, PAGEEX
440 pseudo page fault handling will be used.
441 Note that VM 4.2 supports PFAULT but has a bug in its
442 implementation that causes some problems.
443 Everybody who wants to run Linux under VM != VM4.2 should select
447 bool "VM shared kernel support"
449 Select this option, if you want to share the text segment of the
450 Linux kernel between different VM guests. This reduces memory
451 usage with lots of guests but greatly increases kernel size.
452 Also if a kernel was IPL'ed from a shared segment the kexec system
454 You should only select this option if you know what you are
455 doing and want to exploit this feature.
458 tristate "Cooperative memory management"
460 Select this option, if you want to enable the kernel interface
461 to reduce the memory size of the system. This is accomplished
462 by allocating pages of memory and put them "on hold". This only
463 makes sense for a system running under VM where the unused pages
464 will be reused by VM for other guest systems. The interface
465 allows an external monitor to balance memory of many systems.
466 Everybody who wants to run Linux under VM should select this
470 bool "/proc interface to cooperative memory management"
473 Select this option to enable the /proc interface to the
474 cooperative memory management.
477 bool "IUCV special message interface to cooperative memory management"
478 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
480 Select this option to enable the special message interface to
481 the cooperative memory management.
484 bool "Linux - VM Monitor Stream, base infrastructure"
487 This provides a kernel interface for creating and updating z/VM APPLDATA
488 monitor records. The monitor records are updated at certain time
489 intervals, once the timer is started.
490 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
491 i.e. enables or disables monitoring on the Linux side.
492 A custom interval value (in seconds) can be written to
493 /proc/appldata/interval.
495 Defaults are 60 seconds interval and timer off.
496 The /proc entries can also be read from, showing the current settings.
499 tristate "Monitor memory management statistics"
500 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
502 This provides memory management related data to the Linux - VM Monitor
503 Stream, like paging/swapping rate, memory utilisation, etc.
504 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
505 APPLDATA monitor record, i.e. enables or disables monitoring this record
509 The /proc entry can also be read from, showing the current settings.
511 This can also be compiled as a module, which will be called
515 tristate "Monitor OS statistics"
516 depends on APPLDATA_BASE
518 This provides OS related data to the Linux - VM Monitor Stream, like
519 CPU utilisation, etc.
520 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
521 APPLDATA monitor record, i.e. enables or disables monitoring this record
525 This can also be compiled as a module, which will be called
528 config APPLDATA_NET_SUM
529 tristate "Monitor overall network statistics"
530 depends on APPLDATA_BASE && NET
532 This provides network related data to the Linux - VM Monitor Stream,
533 currently there is only a total sum of network I/O statistics, no
535 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
536 APPLDATA monitor record, i.e. enables or disables monitoring this record
540 This can also be compiled as a module, which will be called
543 source kernel/Kconfig.hz
546 bool "s390 hypervisor file system support"
547 select SYS_HYPERVISOR
550 This is a virtual file system intended to provide accounting
551 information in an s390 hypervisor environment.
554 bool "kexec system call"
556 kexec is a system call that implements the ability to shutdown your
557 current kernel, and to start another kernel. It is like a reboot
558 but is independent of hardware/microcode support.
561 bool "zfcpdump support"
565 Select this option if you want to build an zfcpdump enabled kernel.
566 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
569 bool "s390 guest support for KVM (EXPERIMENTAL)"
570 depends on 64BIT && EXPERIMENTAL
573 select VIRTIO_CONSOLE
575 Select this option if you want to run the kernel as a guest under
576 the KVM hypervisor. This will add detection for KVM as well as a
577 virtio transport. If KVM is detected, the virtio console will be
581 bool "Enable seccomp to safely compute untrusted bytecode"
585 This kernel feature is useful for number crunching applications
586 that may need to compute untrusted bytecode during their
587 execution. By using pipes or other transports made available to
588 the process as file descriptors supporting the read/write
589 syscalls, it's possible to isolate those applications in
590 their own address space using seccomp. Once seccomp is
591 enabled via /proc/<pid>/seccomp, it cannot be disabled
592 and the task is only allowed to execute a few safe syscalls
593 defined by each seccomp mode.
599 menu "Power Management"
601 source "kernel/power/Kconfig"
613 source "drivers/Kconfig"
617 source "arch/s390/Kconfig.debug"
619 source "security/Kconfig"
621 source "crypto/Kconfig"
625 source "arch/s390/kvm/Kconfig"