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 ARCH_HAVE_NMI_SAFE_CMPXCHG
85 select HAVE_KERNEL_GZIP
86 select HAVE_KERNEL_BZIP2
87 select HAVE_KERNEL_LZMA
88 select HAVE_KERNEL_LZO
90 select HAVE_ARCH_MUTEX_CPU_RELAX
91 select HAVE_ARCH_JUMP_LABEL if !MARCH_G5
92 select ARCH_SAVE_PAGE_KEYS if HIBERNATION
94 select HAVE_MEMBLOCK_NODE_MAP
95 select ARCH_DISCARD_MEMBLOCK
96 select ARCH_INLINE_SPIN_TRYLOCK
97 select ARCH_INLINE_SPIN_TRYLOCK_BH
98 select ARCH_INLINE_SPIN_LOCK
99 select ARCH_INLINE_SPIN_LOCK_BH
100 select ARCH_INLINE_SPIN_LOCK_IRQ
101 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
102 select ARCH_INLINE_SPIN_UNLOCK
103 select ARCH_INLINE_SPIN_UNLOCK_BH
104 select ARCH_INLINE_SPIN_UNLOCK_IRQ
105 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
106 select ARCH_INLINE_READ_TRYLOCK
107 select ARCH_INLINE_READ_LOCK
108 select ARCH_INLINE_READ_LOCK_BH
109 select ARCH_INLINE_READ_LOCK_IRQ
110 select ARCH_INLINE_READ_LOCK_IRQSAVE
111 select ARCH_INLINE_READ_UNLOCK
112 select ARCH_INLINE_READ_UNLOCK_BH
113 select ARCH_INLINE_READ_UNLOCK_IRQ
114 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
115 select ARCH_INLINE_WRITE_TRYLOCK
116 select ARCH_INLINE_WRITE_LOCK
117 select ARCH_INLINE_WRITE_LOCK_BH
118 select ARCH_INLINE_WRITE_LOCK_IRQ
119 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
120 select ARCH_INLINE_WRITE_UNLOCK
121 select ARCH_INLINE_WRITE_UNLOCK_BH
122 select ARCH_INLINE_WRITE_UNLOCK_IRQ
123 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
125 config SCHED_OMIT_FRAME_POINTER
128 source "init/Kconfig"
130 source "kernel/Kconfig.freezer"
134 comment "Processor type and features"
136 source "kernel/time/Kconfig"
140 prompt "64 bit kernel"
142 Select this option if you have an IBM z/Architecture machine
143 and want to use the 64 bit addressing mode.
153 prompt "Symmetric multi-processing support"
155 This enables support for systems with more than one CPU. If you have
156 a system with only one CPU, like most personal computers, say N. If
157 you have a system with more than one CPU, say Y.
159 If you say N here, the kernel will run on single and multiprocessor
160 machines, but will use only one CPU of a multiprocessor machine. If
161 you say Y here, the kernel will run on many, but not all,
162 singleprocessor machines. On a singleprocessor machine, the kernel
163 will run faster if you say N here.
165 See also the SMP-HOWTO available at
166 <http://www.tldp.org/docs.html#howto>.
168 Even if you don't know what to do here, say Y.
171 int "Maximum number of CPUs (2-64)"
174 default "32" if !64BIT
175 default "64" if 64BIT
177 This allows you to specify the maximum number of CPUs which this
178 kernel will support. The maximum supported value is 64 and the
179 minimum value which makes sense is 2.
181 This is purely to save memory - each supported CPU adds
182 approximately sixteen kilobytes to the kernel image.
186 prompt "Support for hot-pluggable CPUs"
190 Say Y here to be able to turn CPUs off and on. CPUs
191 can be controlled through /sys/devices/system/cpu/cpu#.
192 Say N if you want to disable CPU hotplug.
199 prompt "Book scheduler support"
203 Book scheduler support improves the CPU scheduler's decision making
204 when dealing with machines that have several books.
208 prompt "IEEE FPU emulation"
211 This option is required for IEEE compliant floating point arithmetic
212 on older ESA/390 machines. Say Y unless you know your machine doesn't
217 prompt "Kernel support for 31 bit emulation"
219 select COMPAT_BINFMT_ELF
221 Select this option if you want to enable your system kernel to
222 handle system-calls from ELF binaries for 31 bit ESA. This option
223 (and some other stuff like libraries and such) is needed for
224 executing 31 bit applications. It is safe to say "Y".
226 config SYSVIPC_COMPAT
227 def_bool y if COMPAT && SYSVIPC
230 def_bool y if COMPAT && KEYS
235 comment "Code generation options"
238 prompt "Processor type"
242 bool "System/390 model G5 and G6"
245 Select this to build a 31 bit kernel that works
246 on all ESA/390 and z/Architecture machines.
249 bool "IBM zSeries model z800 and z900"
251 Select this to enable optimizations for model z800/z900 (2064 and
252 2066 series). This will enable some optimizations that are not
253 available on older ESA/390 (31 Bit) only CPUs.
256 bool "IBM zSeries model z890 and z990"
258 Select this to enable optimizations for model z890/z990 (2084 and
259 2086 series). The kernel will be slightly faster but will not work
265 Select this to enable optimizations for IBM System z9 (2094 and
266 2096 series). The kernel will be slightly faster but will not work
270 bool "IBM System z10"
272 Select this to enable optimizations for IBM System z10 (2097 and
273 2098 series). The kernel will be slightly faster but will not work
277 bool "IBM zEnterprise 114 and 196"
279 Select this to enable optimizations for IBM zEnterprise 114 and 196
280 (2818 and 2817 series). The kernel will be slightly faster but will
281 not work on older machines.
287 prompt "Pack kernel stack"
289 This option enables the compiler option -mkernel-backchain if it
290 is available. If the option is available the compiler supports
291 the new stack layout which dramatically reduces the minimum stack
292 frame size. With an old compiler a non-leaf function needs a
293 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
294 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
295 and 24 byte on 64 bit.
297 Say Y if you are unsure.
301 prompt "Use 8kb for kernel stack instead of 16kb"
302 depends on PACK_STACK && 64BIT && !LOCKDEP
304 If you say Y here and the compiler supports the -mkernel-backchain
305 option the kernel will use a smaller kernel stack size. The reduced
306 size is 8kb instead of 16kb. This allows to run more threads on a
307 system and reduces the pressure on the memory management for higher
308 order page allocations.
310 Say N if you are unsure.
314 prompt "Detect kernel stack overflow"
316 This option enables the compiler option -mstack-guard and
317 -mstack-size if they are available. If the compiler supports them
318 it will emit additional code to each function prolog to trigger
319 an illegal operation if the kernel stack is about to overflow.
321 Say N if you are unsure.
324 int "Size of the guard area (128-1024)"
326 depends on CHECK_STACK
329 This allows you to specify the size of the guard area at the lower
330 end of the kernel stack. If the kernel stack points into the guard
331 area on function entry an illegal operation is triggered. The size
332 needs to be a power of 2. Please keep in mind that the size of an
333 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
334 The minimum size for the stack guard should be 256 for 31 bit and
337 config WARN_DYNAMIC_STACK
339 prompt "Emit compiler warnings for function with dynamic stack usage"
341 This option enables the compiler option -mwarn-dynamicstack. If the
342 compiler supports this options generates warnings for functions
343 that dynamically allocate stack space using alloca.
345 Say N if you are unsure.
347 comment "Kernel preemption"
349 source "kernel/Kconfig.preempt"
351 config ARCH_SPARSEMEM_ENABLE
353 select SPARSEMEM_VMEMMAP_ENABLE
354 select SPARSEMEM_VMEMMAP
355 select SPARSEMEM_STATIC if !64BIT
357 config ARCH_SPARSEMEM_DEFAULT
360 config ARCH_SELECT_MEMORY_MODEL
363 config ARCH_ENABLE_MEMORY_HOTPLUG
364 def_bool y if SPARSEMEM
366 config ARCH_ENABLE_MEMORY_HOTREMOVE
369 config ARCH_HIBERNATION_POSSIBLE
374 comment "I/O subsystem configuration"
378 prompt "QDIO support"
380 This driver provides the Queued Direct I/O base support for
383 To compile this driver as a module, choose M here: the
384 module will be called qdio.
390 prompt "Support for CHSC subchannels"
392 This driver allows usage of CHSC subchannels. A CHSC subchannel
393 is usually present on LPAR only.
394 The driver creates a device /dev/chsc, which may be used to
395 obtain I/O configuration information about the machine and
396 to issue asynchronous chsc commands (DANGEROUS).
397 You will usually only want to use this interface on a special
398 LPAR designated for system management.
400 To compile this driver as a module, choose M here: the
401 module will be called chsc_sch.
409 prompt "Builtin IPL record support"
411 If you want to use the produced kernel to IPL directly from a
412 device, you have to merge a bootsector specific to the device
413 into the first bytes of the kernel. You will have to select the
417 prompt "IPL method generated into head.S"
421 Select "tape" if you want to IPL the image from a Tape.
423 Select "vm_reader" if you are running under VM/ESA and want
424 to IPL the image from the emulated card reader.
434 source "fs/Kconfig.binfmt"
436 config FORCE_MAX_ZONEORDER
442 prompt "Pseudo page fault support"
444 Select this option, if you want to use PFAULT pseudo page fault
445 handling under VM. If running native or in LPAR, this option
446 has no effect. If your VM does not support PFAULT, PAGEEX
447 pseudo page fault handling will be used.
448 Note that VM 4.2 supports PFAULT but has a bug in its
449 implementation that causes some problems.
450 Everybody who wants to run Linux under VM != VM4.2 should select
455 prompt "VM shared kernel support"
457 Select this option, if you want to share the text segment of the
458 Linux kernel between different VM guests. This reduces memory
459 usage with lots of guests but greatly increases kernel size.
460 Also if a kernel was IPL'ed from a shared segment the kexec system
462 You should only select this option if you know what you are
463 doing and want to exploit this feature.
467 prompt "Cooperative memory management"
469 Select this option, if you want to enable the kernel interface
470 to reduce the memory size of the system. This is accomplished
471 by allocating pages of memory and put them "on hold". This only
472 makes sense for a system running under VM where the unused pages
473 will be reused by VM for other guest systems. The interface
474 allows an external monitor to balance memory of many systems.
475 Everybody who wants to run Linux under VM should select this
480 prompt "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.
488 prompt "Linux - VM Monitor Stream, base infrastructure"
491 This provides a kernel interface for creating and updating z/VM APPLDATA
492 monitor records. The monitor records are updated at certain time
493 intervals, once the timer is started.
494 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
495 i.e. enables or disables monitoring on the Linux side.
496 A custom interval value (in seconds) can be written to
497 /proc/appldata/interval.
499 Defaults are 60 seconds interval and timer off.
500 The /proc entries can also be read from, showing the current settings.
504 prompt "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
521 prompt "Monitor OS statistics"
522 depends on APPLDATA_BASE
524 This provides OS related data to the Linux - VM Monitor Stream, like
525 CPU utilisation, etc.
526 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
527 APPLDATA monitor record, i.e. enables or disables monitoring this record
531 This can also be compiled as a module, which will be called
534 config APPLDATA_NET_SUM
536 prompt "Monitor overall network statistics"
537 depends on APPLDATA_BASE && NET
539 This provides network related data to the Linux - VM Monitor Stream,
540 currently there is only a total sum of network I/O statistics, no
542 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
543 APPLDATA monitor record, i.e. enables or disables monitoring this record
547 This can also be compiled as a module, which will be called
550 source kernel/Kconfig.hz
554 prompt "s390 hypervisor file system support"
555 select SYS_HYPERVISOR
557 This is a virtual file system intended to provide accounting
558 information in an s390 hypervisor environment.
562 prompt "kexec system call"
564 kexec is a system call that implements the ability to shutdown your
565 current kernel, and to start another kernel. It is like a reboot
566 but is independent of hardware/microcode support.
569 bool "kernel crash dumps"
573 Generate crash dump after being started by kexec.
574 Crash dump kernels are loaded in the main kernel with kexec-tools
575 into a specially reserved region and then later executed after
576 a crash by kdump/kexec.
577 For more details see Documentation/kdump/kdump.txt
581 prompt "zfcpdump support"
584 Select this option if you want to build an zfcpdump enabled kernel.
585 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
589 prompt "s390 guest support for KVM (EXPERIMENTAL)"
590 depends on 64BIT && EXPERIMENTAL
591 select VIRTUALIZATION
594 select VIRTIO_CONSOLE
596 Select this option if you want to run the kernel as a guest under
597 the KVM hypervisor. This will add detection for KVM as well as a
598 virtio transport. If KVM is detected, the virtio console will be
603 prompt "Enable seccomp to safely compute untrusted bytecode"
606 This kernel feature is useful for number crunching applications
607 that may need to compute untrusted bytecode during their
608 execution. By using pipes or other transports made available to
609 the process as file descriptors supporting the read/write
610 syscalls, it's possible to isolate those applications in
611 their own address space using seccomp. Once seccomp is
612 enabled via /proc/<pid>/seccomp, it cannot be disabled
613 and the task is only allowed to execute a few safe syscalls
614 defined by each seccomp mode.
620 menu "Power Management"
622 source "kernel/power/Kconfig"
634 source "drivers/Kconfig"
638 source "arch/s390/Kconfig.debug"
640 source "security/Kconfig"
642 source "crypto/Kconfig"
646 source "arch/s390/kvm/Kconfig"