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_GET_USER_PAGES_FAST
91 select HAVE_ARCH_MUTEX_CPU_RELAX
92 select HAVE_ARCH_JUMP_LABEL if !MARCH_G5
93 select ARCH_SAVE_PAGE_KEYS if HIBERNATION
94 select ARCH_INLINE_SPIN_TRYLOCK
95 select ARCH_INLINE_SPIN_TRYLOCK_BH
96 select ARCH_INLINE_SPIN_LOCK
97 select ARCH_INLINE_SPIN_LOCK_BH
98 select ARCH_INLINE_SPIN_LOCK_IRQ
99 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
100 select ARCH_INLINE_SPIN_UNLOCK
101 select ARCH_INLINE_SPIN_UNLOCK_BH
102 select ARCH_INLINE_SPIN_UNLOCK_IRQ
103 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
104 select ARCH_INLINE_READ_TRYLOCK
105 select ARCH_INLINE_READ_LOCK
106 select ARCH_INLINE_READ_LOCK_BH
107 select ARCH_INLINE_READ_LOCK_IRQ
108 select ARCH_INLINE_READ_LOCK_IRQSAVE
109 select ARCH_INLINE_READ_UNLOCK
110 select ARCH_INLINE_READ_UNLOCK_BH
111 select ARCH_INLINE_READ_UNLOCK_IRQ
112 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
113 select ARCH_INLINE_WRITE_TRYLOCK
114 select ARCH_INLINE_WRITE_LOCK
115 select ARCH_INLINE_WRITE_LOCK_BH
116 select ARCH_INLINE_WRITE_LOCK_IRQ
117 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
118 select ARCH_INLINE_WRITE_UNLOCK
119 select ARCH_INLINE_WRITE_UNLOCK_BH
120 select ARCH_INLINE_WRITE_UNLOCK_IRQ
121 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
123 config SCHED_OMIT_FRAME_POINTER
126 source "init/Kconfig"
128 source "kernel/Kconfig.freezer"
132 comment "Processor type and features"
134 source "kernel/time/Kconfig"
138 prompt "64 bit kernel"
140 Select this option if you have an IBM z/Architecture machine
141 and want to use the 64 bit addressing mode.
151 prompt "Symmetric multi-processing support"
153 This enables support for systems with more than one CPU. If you have
154 a system with only one CPU, like most personal computers, say N. If
155 you have a system with more than one CPU, say Y.
157 If you say N here, the kernel will run on single and multiprocessor
158 machines, but will use only one CPU of a multiprocessor machine. If
159 you say Y here, the kernel will run on many, but not all,
160 singleprocessor machines. On a singleprocessor machine, the kernel
161 will run faster if you say N here.
163 See also the SMP-HOWTO available at
164 <http://www.tldp.org/docs.html#howto>.
166 Even if you don't know what to do here, say Y.
169 int "Maximum number of CPUs (2-64)"
172 default "32" if !64BIT
173 default "64" if 64BIT
175 This allows you to specify the maximum number of CPUs which this
176 kernel will support. The maximum supported value is 64 and the
177 minimum value which makes sense is 2.
179 This is purely to save memory - each supported CPU adds
180 approximately sixteen kilobytes to the kernel image.
184 prompt "Support for hot-pluggable CPUs"
188 Say Y here to be able to turn CPUs off and on. CPUs
189 can be controlled through /sys/devices/system/cpu/cpu#.
190 Say N if you want to disable CPU hotplug.
194 prompt "Multi-core scheduler support"
197 Multi-core scheduler support improves the CPU scheduler's decision
198 making when dealing with multi-core CPU chips at a cost of slightly
199 increased overhead in some places.
203 prompt "Book scheduler support"
204 depends on SMP && SCHED_MC
206 Book scheduler support improves the CPU scheduler's decision making
207 when dealing with machines that have several books.
211 prompt "IEEE FPU emulation"
214 This option is required for IEEE compliant floating point arithmetic
215 on older ESA/390 machines. Say Y unless you know your machine doesn't
220 prompt "Kernel support for 31 bit emulation"
222 select COMPAT_BINFMT_ELF
224 Select this option if you want to enable your system kernel to
225 handle system-calls from ELF binaries for 31 bit ESA. This option
226 (and some other stuff like libraries and such) is needed for
227 executing 31 bit applications. It is safe to say "Y".
229 config SYSVIPC_COMPAT
230 def_bool y if COMPAT && SYSVIPC
233 def_bool y if COMPAT && KEYS
238 comment "Code generation options"
241 prompt "Processor type"
245 bool "System/390 model G5 and G6"
248 Select this to build a 31 bit kernel that works
249 on all ESA/390 and z/Architecture machines.
252 bool "IBM zSeries model z800 and z900"
254 Select this to enable optimizations for model z800/z900 (2064 and
255 2066 series). This will enable some optimizations that are not
256 available on older ESA/390 (31 Bit) only CPUs.
259 bool "IBM zSeries model z890 and z990"
261 Select this to enable optimizations for model z890/z990 (2084 and
262 2086 series). The kernel will be slightly faster but will not work
268 Select this to enable optimizations for IBM System z9 (2094 and
269 2096 series). The kernel will be slightly faster but will not work
273 bool "IBM System z10"
275 Select this to enable optimizations for IBM System z10 (2097 and
276 2098 series). The kernel will be slightly faster but will not work
280 bool "IBM zEnterprise 114 and 196"
282 Select this to enable optimizations for IBM zEnterprise 114 and 196
283 (2818 and 2817 series). The kernel will be slightly faster but will
284 not work on older machines.
290 prompt "Pack kernel stack"
292 This option enables the compiler option -mkernel-backchain if it
293 is available. If the option is available the compiler supports
294 the new stack layout which dramatically reduces the minimum stack
295 frame size. With an old compiler a non-leaf function needs a
296 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
297 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
298 and 24 byte on 64 bit.
300 Say Y if you are unsure.
304 prompt "Use 8kb for kernel stack instead of 16kb"
305 depends on PACK_STACK && 64BIT && !LOCKDEP
307 If you say Y here and the compiler supports the -mkernel-backchain
308 option the kernel will use a smaller kernel stack size. The reduced
309 size is 8kb instead of 16kb. This allows to run more threads on a
310 system and reduces the pressure on the memory management for higher
311 order page allocations.
313 Say N if you are unsure.
317 prompt "Detect kernel stack overflow"
319 This option enables the compiler option -mstack-guard and
320 -mstack-size if they are available. If the compiler supports them
321 it will emit additional code to each function prolog to trigger
322 an illegal operation if the kernel stack is about to overflow.
324 Say N if you are unsure.
327 int "Size of the guard area (128-1024)"
329 depends on CHECK_STACK
332 This allows you to specify the size of the guard area at the lower
333 end of the kernel stack. If the kernel stack points into the guard
334 area on function entry an illegal operation is triggered. The size
335 needs to be a power of 2. Please keep in mind that the size of an
336 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
337 The minimum size for the stack guard should be 256 for 31 bit and
340 config WARN_DYNAMIC_STACK
342 prompt "Emit compiler warnings for function with dynamic stack usage"
344 This option enables the compiler option -mwarn-dynamicstack. If the
345 compiler supports this options generates warnings for functions
346 that dynamically allocate stack space using alloca.
348 Say N if you are unsure.
350 config ARCH_POPULATES_NODE_MAP
353 comment "Kernel preemption"
355 source "kernel/Kconfig.preempt"
357 config ARCH_SPARSEMEM_ENABLE
359 select SPARSEMEM_VMEMMAP_ENABLE
360 select SPARSEMEM_VMEMMAP
361 select SPARSEMEM_STATIC if !64BIT
363 config ARCH_SPARSEMEM_DEFAULT
366 config ARCH_SELECT_MEMORY_MODEL
369 config ARCH_ENABLE_MEMORY_HOTPLUG
370 def_bool y if SPARSEMEM
372 config ARCH_ENABLE_MEMORY_HOTREMOVE
375 config ARCH_HIBERNATION_POSSIBLE
380 comment "I/O subsystem configuration"
384 prompt "QDIO support"
386 This driver provides the Queued Direct I/O base support for
389 To compile this driver as a module, choose M here: the
390 module will be called qdio.
396 prompt "Support for CHSC subchannels"
398 This driver allows usage of CHSC subchannels. A CHSC subchannel
399 is usually present on LPAR only.
400 The driver creates a device /dev/chsc, which may be used to
401 obtain I/O configuration information about the machine and
402 to issue asynchronous chsc commands (DANGEROUS).
403 You will usually only want to use this interface on a special
404 LPAR designated for system management.
406 To compile this driver as a module, choose M here: the
407 module will be called chsc_sch.
415 prompt "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
448 prompt "Pseudo page fault support"
450 Select this option, if you want to use PFAULT pseudo page fault
451 handling under VM. If running native or in LPAR, this option
452 has no effect. If your VM does not support PFAULT, PAGEEX
453 pseudo page fault handling will be used.
454 Note that VM 4.2 supports PFAULT but has a bug in its
455 implementation that causes some problems.
456 Everybody who wants to run Linux under VM != VM4.2 should select
461 prompt "VM shared kernel support"
463 Select this option, if you want to share the text segment of the
464 Linux kernel between different VM guests. This reduces memory
465 usage with lots of guests but greatly increases kernel size.
466 Also if a kernel was IPL'ed from a shared segment the kexec system
468 You should only select this option if you know what you are
469 doing and want to exploit this feature.
473 prompt "Cooperative memory management"
475 Select this option, if you want to enable the kernel interface
476 to reduce the memory size of the system. This is accomplished
477 by allocating pages of memory and put them "on hold". This only
478 makes sense for a system running under VM where the unused pages
479 will be reused by VM for other guest systems. The interface
480 allows an external monitor to balance memory of many systems.
481 Everybody who wants to run Linux under VM should select this
486 prompt "IUCV special message interface to cooperative memory management"
487 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
489 Select this option to enable the special message interface to
490 the cooperative memory management.
494 prompt "Linux - VM Monitor Stream, base infrastructure"
497 This provides a kernel interface for creating and updating z/VM APPLDATA
498 monitor records. The monitor records are updated at certain time
499 intervals, once the timer is started.
500 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
501 i.e. enables or disables monitoring on the Linux side.
502 A custom interval value (in seconds) can be written to
503 /proc/appldata/interval.
505 Defaults are 60 seconds interval and timer off.
506 The /proc entries can also be read from, showing the current settings.
510 prompt "Monitor memory management statistics"
511 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
513 This provides memory management related data to the Linux - VM Monitor
514 Stream, like paging/swapping rate, memory utilisation, etc.
515 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
516 APPLDATA monitor record, i.e. enables or disables monitoring this record
520 The /proc entry can also be read from, showing the current settings.
522 This can also be compiled as a module, which will be called
527 prompt "Monitor OS statistics"
528 depends on APPLDATA_BASE
530 This provides OS related data to the Linux - VM Monitor Stream, like
531 CPU utilisation, etc.
532 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
533 APPLDATA monitor record, i.e. enables or disables monitoring this record
537 This can also be compiled as a module, which will be called
540 config APPLDATA_NET_SUM
542 prompt "Monitor overall network statistics"
543 depends on APPLDATA_BASE && NET
545 This provides network related data to the Linux - VM Monitor Stream,
546 currently there is only a total sum of network I/O statistics, no
548 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
549 APPLDATA monitor record, i.e. enables or disables monitoring this record
553 This can also be compiled as a module, which will be called
556 source kernel/Kconfig.hz
560 prompt "s390 hypervisor file system support"
561 select SYS_HYPERVISOR
563 This is a virtual file system intended to provide accounting
564 information in an s390 hypervisor environment.
568 prompt "kexec system call"
570 kexec is a system call that implements the ability to shutdown your
571 current kernel, and to start another kernel. It is like a reboot
572 but is independent of hardware/microcode support.
575 bool "kernel crash dumps"
579 Generate crash dump after being started by kexec.
580 Crash dump kernels are loaded in the main kernel with kexec-tools
581 into a specially reserved region and then later executed after
582 a crash by kdump/kexec.
583 For more details see Documentation/kdump/kdump.txt
587 prompt "zfcpdump support"
590 Select this option if you want to build an zfcpdump enabled kernel.
591 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
595 prompt "s390 guest support for KVM (EXPERIMENTAL)"
596 depends on 64BIT && EXPERIMENTAL
597 select VIRTUALIZATION
600 select VIRTIO_CONSOLE
602 Select this option if you want to run the kernel as a guest under
603 the KVM hypervisor. This will add detection for KVM as well as a
604 virtio transport. If KVM is detected, the virtio console will be
609 prompt "Enable seccomp to safely compute untrusted bytecode"
612 This kernel feature is useful for number crunching applications
613 that may need to compute untrusted bytecode during their
614 execution. By using pipes or other transports made available to
615 the process as file descriptors supporting the read/write
616 syscalls, it's possible to isolate those applications in
617 their own address space using seccomp. Once seccomp is
618 enabled via /proc/<pid>/seccomp, it cannot be disabled
619 and the task is only allowed to execute a few safe syscalls
620 defined by each seccomp mode.
626 menu "Power Management"
628 source "kernel/power/Kconfig"
640 source "drivers/Kconfig"
644 source "arch/s390/Kconfig.debug"
646 source "security/Kconfig"
648 source "crypto/Kconfig"
652 source "arch/s390/kvm/Kconfig"