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
43 config GENERIC_TIME_VSYSCALL
46 config GENERIC_CLOCKEVENTS
54 config GENERIC_BUG_RELATIVE_POINTERS
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_REGS_AND_STACK_ACCESS_API
91 select HAVE_DEFAULT_NO_SPIN_MUTEXES
94 select HAVE_KRETPROBES
95 select HAVE_KVM if 64BIT
96 select HAVE_ARCH_TRACEHOOK
97 select INIT_ALL_POSSIBLE
99 select HAVE_PERF_EVENTS
100 select HAVE_KERNEL_GZIP
101 select HAVE_KERNEL_BZIP2
102 select HAVE_KERNEL_LZMA
103 select HAVE_KERNEL_LZO
104 select ARCH_INLINE_SPIN_TRYLOCK
105 select ARCH_INLINE_SPIN_TRYLOCK_BH
106 select ARCH_INLINE_SPIN_LOCK
107 select ARCH_INLINE_SPIN_LOCK_BH
108 select ARCH_INLINE_SPIN_LOCK_IRQ
109 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
110 select ARCH_INLINE_SPIN_UNLOCK
111 select ARCH_INLINE_SPIN_UNLOCK_BH
112 select ARCH_INLINE_SPIN_UNLOCK_IRQ
113 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
114 select ARCH_INLINE_READ_TRYLOCK
115 select ARCH_INLINE_READ_LOCK
116 select ARCH_INLINE_READ_LOCK_BH
117 select ARCH_INLINE_READ_LOCK_IRQ
118 select ARCH_INLINE_READ_LOCK_IRQSAVE
119 select ARCH_INLINE_READ_UNLOCK
120 select ARCH_INLINE_READ_UNLOCK_BH
121 select ARCH_INLINE_READ_UNLOCK_IRQ
122 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
123 select ARCH_INLINE_WRITE_TRYLOCK
124 select ARCH_INLINE_WRITE_LOCK
125 select ARCH_INLINE_WRITE_LOCK_BH
126 select ARCH_INLINE_WRITE_LOCK_IRQ
127 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
128 select ARCH_INLINE_WRITE_UNLOCK
129 select ARCH_INLINE_WRITE_UNLOCK_BH
130 select ARCH_INLINE_WRITE_UNLOCK_IRQ
131 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
133 config SCHED_OMIT_FRAME_POINTER
137 source "init/Kconfig"
139 source "kernel/Kconfig.freezer"
143 comment "Processor type and features"
145 source "kernel/time/Kconfig"
150 Select this option if you have a 64 bit IBM zSeries machine
151 and want to use the 64 bit addressing mode.
161 bool "Symmetric multi-processing support"
163 This enables support for systems with more than one CPU. If you have
164 a system with only one CPU, like most personal computers, say N. If
165 you have a system with more than one CPU, say Y.
167 If you say N here, the kernel will run on single and multiprocessor
168 machines, but will use only one CPU of a multiprocessor machine. If
169 you say Y here, the kernel will run on many, but not all,
170 singleprocessor machines. On a singleprocessor machine, the kernel
171 will run faster if you say N here.
173 See also the SMP-HOWTO available at
174 <http://www.tldp.org/docs.html#howto>.
176 Even if you don't know what to do here, say Y.
179 int "Maximum number of CPUs (2-64)"
182 default "32" if !64BIT
183 default "64" if 64BIT
185 This allows you to specify the maximum number of CPUs which this
186 kernel will support. The maximum supported value is 64 and the
187 minimum value which makes sense is 2.
189 This is purely to save memory - each supported CPU adds
190 approximately sixteen kilobytes to the kernel image.
193 bool "Support for hot-pluggable CPUs"
198 Say Y here to be able to turn CPUs off and on. CPUs
199 can be controlled through /sys/devices/system/cpu/cpu#.
200 Say N if you want to disable CPU hotplug.
203 bool "IEEE FPU emulation"
206 This option is required for IEEE compliant floating point arithmetic
207 on older S/390 machines. Say Y unless you know your machine doesn't
211 bool "Kernel support for 31 bit emulation"
213 select COMPAT_BINFMT_ELF
215 Select this option if you want to enable your system kernel to
216 handle system-calls from ELF binaries for 31 bit ESA. This option
217 (and some other stuff like libraries and such) is needed for
218 executing 31 bit applications. It is safe to say "Y".
220 config SYSVIPC_COMPAT
222 depends on COMPAT && SYSVIPC
229 config S390_EXEC_PROTECT
230 bool "Data execute protection"
232 This option allows to enable a buffer overflow protection for user
233 space programs and it also selects the addressing mode option above.
234 The kernel parameter noexec=on will enable this feature and also
235 switch the addressing modes, default is disabled. Enabling this (via
236 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
237 will reduce system performance.
239 comment "Code generation options"
242 prompt "Processor type"
246 bool "S/390 model G5 and G6"
249 Select this to build a 31 bit kernel that works
250 on all S/390 and zSeries machines.
253 bool "IBM eServer zSeries model z800 and z900"
255 Select this to optimize for zSeries machines. This
256 will enable some optimizations that are not available
257 on older 31 bit only CPUs.
260 bool "IBM eServer zSeries model z890 and z990"
262 Select this enable optimizations for model z890/z990.
263 This will be slightly faster but does not work on
264 older machines such as the z900.
269 Select this to enable optimizations for IBM System z9-109, IBM
270 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
271 Class (z9 BC). The kernel will be slightly faster but will not
272 work on older machines such as the z990, z890, z900, and z800.
275 bool "IBM System z10"
277 Select this to enable optimizations for IBM System z10. The
278 kernel will be slightly faster but will not work on older
279 machines such as the z990, z890, z900, z800, z9-109, z9-ec
285 bool "Pack kernel stack"
287 This option enables the compiler option -mkernel-backchain if it
288 is available. If the option is available the compiler supports
289 the new stack layout which dramatically reduces the minimum stack
290 frame size. With an old compiler a non-leaf function needs a
291 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
292 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
293 and 24 byte on 64 bit.
295 Say Y if you are unsure.
298 bool "Use 8kb for kernel stack instead of 16kb"
299 depends on PACK_STACK && 64BIT && !LOCKDEP
301 If you say Y here and the compiler supports the -mkernel-backchain
302 option the kernel will use a smaller kernel stack size. The reduced
303 size is 8kb instead of 16kb. This allows to run more threads on a
304 system and reduces the pressure on the memory management for higher
305 order page allocations.
307 Say N if you are unsure.
310 bool "Detect kernel stack overflow"
312 This option enables the compiler option -mstack-guard and
313 -mstack-size if they are available. If the compiler supports them
314 it will emit additional code to each function prolog to trigger
315 an illegal operation if the kernel stack is about to overflow.
317 Say N if you are unsure.
320 int "Size of the guard area (128-1024)"
322 depends on CHECK_STACK
325 This allows you to specify the size of the guard area at the lower
326 end of the kernel stack. If the kernel stack points into the guard
327 area on function entry an illegal operation is triggered. The size
328 needs to be a power of 2. Please keep in mind that the size of an
329 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
330 The minimum size for the stack guard should be 256 for 31 bit and
334 bool "Emit compiler warnings for function with broken stack usage"
336 This option enables the compiler options -mwarn-framesize and
337 -mwarn-dynamicstack. If the compiler supports these options it
338 will generate warnings for function which either use alloca or
339 create a stack frame bigger than CONFIG_WARN_STACK_SIZE.
341 Say N if you are unsure.
343 config WARN_STACK_SIZE
344 int "Maximum frame size considered safe (128-2048)"
346 depends on WARN_STACK
349 This allows you to specify the maximum frame size a function may
350 have without the compiler complaining about it.
352 config ARCH_POPULATES_NODE_MAP
355 comment "Kernel preemption"
357 source "kernel/Kconfig.preempt"
359 config ARCH_SPARSEMEM_ENABLE
361 select SPARSEMEM_VMEMMAP_ENABLE
362 select SPARSEMEM_VMEMMAP
363 select SPARSEMEM_STATIC if !64BIT
365 config ARCH_SPARSEMEM_DEFAULT
368 config ARCH_SELECT_MEMORY_MODEL
371 config ARCH_ENABLE_MEMORY_HOTPLUG
375 config ARCH_ENABLE_MEMORY_HOTREMOVE
378 config ARCH_HIBERNATION_POSSIBLE
383 comment "I/O subsystem configuration"
386 tristate "QDIO support"
388 This driver provides the Queued Direct I/O base support for
391 To compile this driver as a module, choose M here: the
392 module will be called qdio.
397 tristate "Support for CHSC subchannels"
399 This driver allows usage of CHSC subchannels. A CHSC subchannel
400 is usually present on LPAR only.
401 The driver creates a device /dev/chsc, which may be used to
402 obtain I/O configuration information about the machine and
403 to issue asynchronous chsc commands (DANGEROUS).
404 You will usually only want to use this interface on a special
405 LPAR designated for system management.
407 To compile this driver as a module, choose M here: the
408 module will be called chsc_sch.
415 bool "Builtin IPL record support"
417 If you want to use the produced kernel to IPL directly from a
418 device, you have to merge a bootsector specific to the device
419 into the first bytes of the kernel. You will have to select the
423 prompt "IPL method generated into head.S"
427 Select "tape" if you want to IPL the image from a Tape.
429 Select "vm_reader" if you are running under VM/ESA and want
430 to IPL the image from the emulated card reader.
440 source "fs/Kconfig.binfmt"
442 config FORCE_MAX_ZONEORDER
447 bool "Pseudo page fault support"
449 Select this option, if you want to use PFAULT pseudo page fault
450 handling under VM. If running native or in LPAR, this option
451 has no effect. If your VM does not support PFAULT, PAGEEX
452 pseudo page fault handling will be used.
453 Note that VM 4.2 supports PFAULT but has a bug in its
454 implementation that causes some problems.
455 Everybody who wants to run Linux under VM != VM4.2 should select
459 bool "VM shared kernel support"
461 Select this option, if you want to share the text segment of the
462 Linux kernel between different VM guests. This reduces memory
463 usage with lots of guests but greatly increases kernel size.
464 Also if a kernel was IPL'ed from a shared segment the kexec system
466 You should only select this option if you know what you are
467 doing and want to exploit this feature.
470 tristate "Cooperative memory management"
472 Select this option, if you want to enable the kernel interface
473 to reduce the memory size of the system. This is accomplished
474 by allocating pages of memory and put them "on hold". This only
475 makes sense for a system running under VM where the unused pages
476 will be reused by VM for other guest systems. The interface
477 allows an external monitor to balance memory of many systems.
478 Everybody who wants to run Linux under VM should select this
482 bool "IUCV special message interface to cooperative memory management"
483 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
485 Select this option to enable the special message interface to
486 the cooperative memory management.
489 bool "Linux - VM Monitor Stream, base infrastructure"
492 This provides a kernel interface for creating and updating z/VM APPLDATA
493 monitor records. The monitor records are updated at certain time
494 intervals, once the timer is started.
495 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
496 i.e. enables or disables monitoring on the Linux side.
497 A custom interval value (in seconds) can be written to
498 /proc/appldata/interval.
500 Defaults are 60 seconds interval and timer off.
501 The /proc entries can also be read from, showing the current settings.
504 tristate "Monitor memory management statistics"
505 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
507 This provides memory management related data to the Linux - VM Monitor
508 Stream, like paging/swapping rate, memory utilisation, etc.
509 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
510 APPLDATA monitor record, i.e. enables or disables monitoring this record
514 The /proc entry can also be read from, showing the current settings.
516 This can also be compiled as a module, which will be called
520 tristate "Monitor OS statistics"
521 depends on APPLDATA_BASE
523 This provides OS related data to the Linux - VM Monitor Stream, like
524 CPU utilisation, etc.
525 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
526 APPLDATA monitor record, i.e. enables or disables monitoring this record
530 This can also be compiled as a module, which will be called
533 config APPLDATA_NET_SUM
534 tristate "Monitor overall network statistics"
535 depends on APPLDATA_BASE && NET
537 This provides network related data to the Linux - VM Monitor Stream,
538 currently there is only a total sum of network I/O statistics, no
540 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
541 APPLDATA monitor record, i.e. enables or disables monitoring this record
545 This can also be compiled as a module, which will be called
548 source kernel/Kconfig.hz
551 bool "s390 hypervisor file system support"
552 select SYS_HYPERVISOR
555 This is a virtual file system intended to provide accounting
556 information in an s390 hypervisor environment.
559 bool "kexec system call"
561 kexec is a system call that implements the ability to shutdown your
562 current kernel, and to start another kernel. It is like a reboot
563 but is independent of hardware/microcode support.
566 bool "zfcpdump support"
570 Select this option if you want to build an zfcpdump enabled kernel.
571 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
574 bool "s390 guest support for KVM (EXPERIMENTAL)"
575 depends on 64BIT && EXPERIMENTAL
578 select VIRTIO_CONSOLE
580 Select this option if you want to run the kernel as a guest under
581 the KVM hypervisor. This will add detection for KVM as well as a
582 virtio transport. If KVM is detected, the virtio console will be
586 bool "Enable seccomp to safely compute untrusted bytecode"
590 This kernel feature is useful for number crunching applications
591 that may need to compute untrusted bytecode during their
592 execution. By using pipes or other transports made available to
593 the process as file descriptors supporting the read/write
594 syscalls, it's possible to isolate those applications in
595 their own address space using seccomp. Once seccomp is
596 enabled via /proc/<pid>/seccomp, it cannot be disabled
597 and the task is only allowed to execute a few safe syscalls
598 defined by each seccomp mode.
604 menu "Power Management"
606 source "kernel/power/Kconfig"
618 source "drivers/Kconfig"
622 source "arch/s390/Kconfig.debug"
624 source "security/Kconfig"
626 source "crypto/Kconfig"
630 source "arch/s390/kvm/Kconfig"