10 config STACKTRACE_SUPPORT
13 config HAVE_LATENCYTOP_SUPPORT
16 config RWSEM_GENERIC_SPINLOCK
19 config RWSEM_XCHGADD_ALGORITHM
22 config ARCH_HAS_ILOG2_U32
25 config ARCH_HAS_ILOG2_U64
28 config GENERIC_HWEIGHT
31 config GENERIC_TIME_VSYSCALL
34 config GENERIC_CLOCKEVENTS
40 config GENERIC_BUG_RELATIVE_POINTERS
49 config ARCH_DMA_ADDR_T_64BIT
52 config GENERIC_LOCKBREAK
53 def_bool y if SMP && PREEMPT
58 config VIRT_CPU_ACCOUNTING
61 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
66 select USE_GENERIC_SMP_HELPERS if SMP
67 select HAVE_SYSCALL_WRAPPERS
68 select HAVE_FUNCTION_TRACER
69 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
70 select HAVE_FTRACE_MCOUNT_RECORD
71 select HAVE_C_RECORDMCOUNT
72 select HAVE_SYSCALL_TRACEPOINTS
73 select HAVE_DYNAMIC_FTRACE
74 select HAVE_FUNCTION_GRAPH_TRACER
75 select HAVE_REGS_AND_STACK_ACCESS_API
78 select HAVE_KRETPROBES
79 select HAVE_KVM if 64BIT
80 select HAVE_ARCH_TRACEHOOK
81 select INIT_ALL_POSSIBLE
83 select HAVE_PERF_EVENTS
84 select HAVE_KERNEL_GZIP
85 select HAVE_KERNEL_BZIP2
86 select HAVE_KERNEL_LZMA
87 select HAVE_KERNEL_LZO
89 select HAVE_GET_USER_PAGES_FAST
90 select HAVE_ARCH_MUTEX_CPU_RELAX
91 select HAVE_ARCH_JUMP_LABEL if !MARCH_G5
92 select ARCH_INLINE_SPIN_TRYLOCK
93 select ARCH_INLINE_SPIN_TRYLOCK_BH
94 select ARCH_INLINE_SPIN_LOCK
95 select ARCH_INLINE_SPIN_LOCK_BH
96 select ARCH_INLINE_SPIN_LOCK_IRQ
97 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
98 select ARCH_INLINE_SPIN_UNLOCK
99 select ARCH_INLINE_SPIN_UNLOCK_BH
100 select ARCH_INLINE_SPIN_UNLOCK_IRQ
101 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
102 select ARCH_INLINE_READ_TRYLOCK
103 select ARCH_INLINE_READ_LOCK
104 select ARCH_INLINE_READ_LOCK_BH
105 select ARCH_INLINE_READ_LOCK_IRQ
106 select ARCH_INLINE_READ_LOCK_IRQSAVE
107 select ARCH_INLINE_READ_UNLOCK
108 select ARCH_INLINE_READ_UNLOCK_BH
109 select ARCH_INLINE_READ_UNLOCK_IRQ
110 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
111 select ARCH_INLINE_WRITE_TRYLOCK
112 select ARCH_INLINE_WRITE_LOCK
113 select ARCH_INLINE_WRITE_LOCK_BH
114 select ARCH_INLINE_WRITE_LOCK_IRQ
115 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
116 select ARCH_INLINE_WRITE_UNLOCK
117 select ARCH_INLINE_WRITE_UNLOCK_BH
118 select ARCH_INLINE_WRITE_UNLOCK_IRQ
119 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
121 config SCHED_OMIT_FRAME_POINTER
124 source "init/Kconfig"
126 source "kernel/Kconfig.freezer"
130 comment "Processor type and features"
132 source "kernel/time/Kconfig"
136 prompt "64 bit kernel"
138 Select this option if you have an IBM z/Architecture machine
139 and want to use the 64 bit addressing mode.
149 prompt "Symmetric multi-processing support"
151 This enables support for systems with more than one CPU. If you have
152 a system with only one CPU, like most personal computers, say N. If
153 you have a system with more than one CPU, say Y.
155 If you say N here, the kernel will run on single and multiprocessor
156 machines, but will use only one CPU of a multiprocessor machine. If
157 you say Y here, the kernel will run on many, but not all,
158 singleprocessor machines. On a singleprocessor machine, the kernel
159 will run faster if you say N here.
161 See also the SMP-HOWTO available at
162 <http://www.tldp.org/docs.html#howto>.
164 Even if you don't know what to do here, say Y.
167 int "Maximum number of CPUs (2-64)"
170 default "32" if !64BIT
171 default "64" if 64BIT
173 This allows you to specify the maximum number of CPUs which this
174 kernel will support. The maximum supported value is 64 and the
175 minimum value which makes sense is 2.
177 This is purely to save memory - each supported CPU adds
178 approximately sixteen kilobytes to the kernel image.
182 prompt "Support for hot-pluggable CPUs"
186 Say Y here to be able to turn CPUs off and on. CPUs
187 can be controlled through /sys/devices/system/cpu/cpu#.
188 Say N if you want to disable CPU hotplug.
192 prompt "Multi-core scheduler support"
195 Multi-core scheduler support improves the CPU scheduler's decision
196 making when dealing with multi-core CPU chips at a cost of slightly
197 increased overhead in some places.
201 prompt "Book scheduler support"
202 depends on SMP && SCHED_MC
204 Book scheduler support improves the CPU scheduler's decision making
205 when dealing with machines that have several books.
209 prompt "IEEE FPU emulation"
212 This option is required for IEEE compliant floating point arithmetic
213 on older ESA/390 machines. Say Y unless you know your machine doesn't
218 prompt "Kernel support for 31 bit emulation"
220 select COMPAT_BINFMT_ELF
222 Select this option if you want to enable your system kernel to
223 handle system-calls from ELF binaries for 31 bit ESA. This option
224 (and some other stuff like libraries and such) is needed for
225 executing 31 bit applications. It is safe to say "Y".
227 config SYSVIPC_COMPAT
228 def_bool y if COMPAT && SYSVIPC
233 comment "Code generation options"
236 prompt "Processor type"
240 bool "System/390 model G5 and G6"
243 Select this to build a 31 bit kernel that works
244 on all ESA/390 and z/Architecture machines.
247 bool "IBM zSeries model z800 and z900"
249 Select this to enable optimizations for model z800/z900 (2064 and
250 2066 series). This will enable some optimizations that are not
251 available on older ESA/390 (31 Bit) only CPUs.
254 bool "IBM zSeries model z890 and z990"
256 Select this to enable optimizations for model z890/z990 (2084 and
257 2086 series). The kernel will be slightly faster but will not work
263 Select this to enable optimizations for IBM System z9 (2094 and
264 2096 series). The kernel will be slightly faster but will not work
268 bool "IBM System z10"
270 Select this to enable optimizations for IBM System z10 (2097 and
271 2098 series). The kernel will be slightly faster but will not work
275 bool "IBM zEnterprise 196"
277 Select this to enable optimizations for IBM zEnterprise 196
278 (2817 series). The kernel will be slightly faster but will not work
285 prompt "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.
299 prompt "Use 8kb for kernel stack instead of 16kb"
300 depends on PACK_STACK && 64BIT && !LOCKDEP
302 If you say Y here and the compiler supports the -mkernel-backchain
303 option the kernel will use a smaller kernel stack size. The reduced
304 size is 8kb instead of 16kb. This allows to run more threads on a
305 system and reduces the pressure on the memory management for higher
306 order page allocations.
308 Say N if you are unsure.
312 prompt "Detect kernel stack overflow"
314 This option enables the compiler option -mstack-guard and
315 -mstack-size if they are available. If the compiler supports them
316 it will emit additional code to each function prolog to trigger
317 an illegal operation if the kernel stack is about to overflow.
319 Say N if you are unsure.
322 int "Size of the guard area (128-1024)"
324 depends on CHECK_STACK
327 This allows you to specify the size of the guard area at the lower
328 end of the kernel stack. If the kernel stack points into the guard
329 area on function entry an illegal operation is triggered. The size
330 needs to be a power of 2. Please keep in mind that the size of an
331 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
332 The minimum size for the stack guard should be 256 for 31 bit and
335 config WARN_DYNAMIC_STACK
337 prompt "Emit compiler warnings for function with dynamic stack usage"
339 This option enables the compiler option -mwarn-dynamicstack. If the
340 compiler supports this options generates warnings for functions
341 that dynamically allocate stack space using alloca.
343 Say N if you are unsure.
345 config ARCH_POPULATES_NODE_MAP
348 comment "Kernel preemption"
350 source "kernel/Kconfig.preempt"
352 config ARCH_SPARSEMEM_ENABLE
354 select SPARSEMEM_VMEMMAP_ENABLE
355 select SPARSEMEM_VMEMMAP
356 select SPARSEMEM_STATIC if !64BIT
358 config ARCH_SPARSEMEM_DEFAULT
361 config ARCH_SELECT_MEMORY_MODEL
364 config ARCH_ENABLE_MEMORY_HOTPLUG
365 def_bool y if SPARSEMEM
367 config ARCH_ENABLE_MEMORY_HOTREMOVE
370 config ARCH_HIBERNATION_POSSIBLE
375 comment "I/O subsystem configuration"
379 prompt "QDIO support"
381 This driver provides the Queued Direct I/O base support for
384 To compile this driver as a module, choose M here: the
385 module will be called qdio.
391 prompt "Support for CHSC subchannels"
393 This driver allows usage of CHSC subchannels. A CHSC subchannel
394 is usually present on LPAR only.
395 The driver creates a device /dev/chsc, which may be used to
396 obtain I/O configuration information about the machine and
397 to issue asynchronous chsc commands (DANGEROUS).
398 You will usually only want to use this interface on a special
399 LPAR designated for system management.
401 To compile this driver as a module, choose M here: the
402 module will be called chsc_sch.
410 prompt "Builtin IPL record support"
412 If you want to use the produced kernel to IPL directly from a
413 device, you have to merge a bootsector specific to the device
414 into the first bytes of the kernel. You will have to select the
418 prompt "IPL method generated into head.S"
422 Select "tape" if you want to IPL the image from a Tape.
424 Select "vm_reader" if you are running under VM/ESA and want
425 to IPL the image from the emulated card reader.
435 source "fs/Kconfig.binfmt"
437 config FORCE_MAX_ZONEORDER
443 prompt "Pseudo page fault support"
445 Select this option, if you want to use PFAULT pseudo page fault
446 handling under VM. If running native or in LPAR, this option
447 has no effect. If your VM does not support PFAULT, PAGEEX
448 pseudo page fault handling will be used.
449 Note that VM 4.2 supports PFAULT but has a bug in its
450 implementation that causes some problems.
451 Everybody who wants to run Linux under VM != VM4.2 should select
456 prompt "VM shared kernel support"
458 Select this option, if you want to share the text segment of the
459 Linux kernel between different VM guests. This reduces memory
460 usage with lots of guests but greatly increases kernel size.
461 Also if a kernel was IPL'ed from a shared segment the kexec system
463 You should only select this option if you know what you are
464 doing and want to exploit this feature.
468 prompt "Cooperative memory management"
470 Select this option, if you want to enable the kernel interface
471 to reduce the memory size of the system. This is accomplished
472 by allocating pages of memory and put them "on hold". This only
473 makes sense for a system running under VM where the unused pages
474 will be reused by VM for other guest systems. The interface
475 allows an external monitor to balance memory of many systems.
476 Everybody who wants to run Linux under VM should select this
481 prompt "IUCV special message interface to cooperative memory management"
482 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
484 Select this option to enable the special message interface to
485 the cooperative memory management.
489 prompt "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.
505 prompt "Monitor memory management statistics"
506 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
508 This provides memory management related data to the Linux - VM Monitor
509 Stream, like paging/swapping rate, memory utilisation, etc.
510 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
511 APPLDATA monitor record, i.e. enables or disables monitoring this record
515 The /proc entry can also be read from, showing the current settings.
517 This can also be compiled as a module, which will be called
522 prompt "Monitor OS statistics"
523 depends on APPLDATA_BASE
525 This provides OS related data to the Linux - VM Monitor Stream, like
526 CPU utilisation, etc.
527 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
528 APPLDATA monitor record, i.e. enables or disables monitoring this record
532 This can also be compiled as a module, which will be called
535 config APPLDATA_NET_SUM
537 prompt "Monitor overall network statistics"
538 depends on APPLDATA_BASE && NET
540 This provides network related data to the Linux - VM Monitor Stream,
541 currently there is only a total sum of network I/O statistics, no
543 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
544 APPLDATA monitor record, i.e. enables or disables monitoring this record
548 This can also be compiled as a module, which will be called
551 source kernel/Kconfig.hz
555 prompt "s390 hypervisor file system support"
556 select SYS_HYPERVISOR
558 This is a virtual file system intended to provide accounting
559 information in an s390 hypervisor environment.
563 prompt "kexec system call"
565 kexec is a system call that implements the ability to shutdown your
566 current kernel, and to start another kernel. It is like a reboot
567 but is independent of hardware/microcode support.
571 prompt "zfcpdump support"
574 Select this option if you want to build an zfcpdump enabled kernel.
575 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
579 prompt "s390 guest support for KVM (EXPERIMENTAL)"
580 depends on 64BIT && EXPERIMENTAL
583 select VIRTIO_CONSOLE
585 Select this option if you want to run the kernel as a guest under
586 the KVM hypervisor. This will add detection for KVM as well as a
587 virtio transport. If KVM is detected, the virtio console will be
592 prompt "Enable seccomp to safely compute untrusted bytecode"
595 This kernel feature is useful for number crunching applications
596 that may need to compute untrusted bytecode during their
597 execution. By using pipes or other transports made available to
598 the process as file descriptors supporting the read/write
599 syscalls, it's possible to isolate those applications in
600 their own address space using seccomp. Once seccomp is
601 enabled via /proc/<pid>/seccomp, it cannot be disabled
602 and the task is only allowed to execute a few safe syscalls
603 defined by each seccomp mode.
609 menu "Power Management"
611 source "kernel/power/Kconfig"
623 source "drivers/Kconfig"
627 source "arch/s390/Kconfig.debug"
629 source "security/Kconfig"
631 source "crypto/Kconfig"
635 source "arch/s390/kvm/Kconfig"