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
34 config GENERIC_BUG_RELATIVE_POINTERS
43 config ARCH_DMA_ADDR_T_64BIT
46 config GENERIC_LOCKBREAK
47 def_bool y if SMP && PREEMPT
52 config VIRT_CPU_ACCOUNTING
55 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
60 select USE_GENERIC_SMP_HELPERS if SMP
61 select GENERIC_CPU_DEVICES if !SMP
62 select HAVE_SYSCALL_WRAPPERS
63 select HAVE_FUNCTION_TRACER
64 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
65 select HAVE_FTRACE_MCOUNT_RECORD
66 select HAVE_C_RECORDMCOUNT
67 select HAVE_SYSCALL_TRACEPOINTS
68 select HAVE_DYNAMIC_FTRACE
69 select HAVE_FUNCTION_GRAPH_TRACER
70 select HAVE_REGS_AND_STACK_ACCESS_API
73 select HAVE_KRETPROBES
74 select HAVE_KVM if 64BIT
75 select HAVE_ARCH_TRACEHOOK
76 select INIT_ALL_POSSIBLE
78 select HAVE_PERF_EVENTS
79 select ARCH_HAVE_NMI_SAFE_CMPXCHG
80 select HAVE_KERNEL_GZIP
81 select HAVE_KERNEL_BZIP2
82 select HAVE_KERNEL_LZMA
83 select HAVE_KERNEL_LZO
85 select HAVE_ARCH_MUTEX_CPU_RELAX
86 select HAVE_ARCH_JUMP_LABEL if !MARCH_G5
87 select ARCH_SAVE_PAGE_KEYS if HIBERNATION
89 select HAVE_MEMBLOCK_NODE_MAP
90 select ARCH_DISCARD_MEMBLOCK
91 select ARCH_INLINE_SPIN_TRYLOCK
92 select ARCH_INLINE_SPIN_TRYLOCK_BH
93 select ARCH_INLINE_SPIN_LOCK
94 select ARCH_INLINE_SPIN_LOCK_BH
95 select ARCH_INLINE_SPIN_LOCK_IRQ
96 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
97 select ARCH_INLINE_SPIN_UNLOCK
98 select ARCH_INLINE_SPIN_UNLOCK_BH
99 select ARCH_INLINE_SPIN_UNLOCK_IRQ
100 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
101 select ARCH_INLINE_READ_TRYLOCK
102 select ARCH_INLINE_READ_LOCK
103 select ARCH_INLINE_READ_LOCK_BH
104 select ARCH_INLINE_READ_LOCK_IRQ
105 select ARCH_INLINE_READ_LOCK_IRQSAVE
106 select ARCH_INLINE_READ_UNLOCK
107 select ARCH_INLINE_READ_UNLOCK_BH
108 select ARCH_INLINE_READ_UNLOCK_IRQ
109 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
110 select ARCH_INLINE_WRITE_TRYLOCK
111 select ARCH_INLINE_WRITE_LOCK
112 select ARCH_INLINE_WRITE_LOCK_BH
113 select ARCH_INLINE_WRITE_LOCK_IRQ
114 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
115 select ARCH_INLINE_WRITE_UNLOCK
116 select ARCH_INLINE_WRITE_UNLOCK_BH
117 select ARCH_INLINE_WRITE_UNLOCK_IRQ
118 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
119 select GENERIC_TIME_VSYSCALL
120 select GENERIC_CLOCKEVENTS
121 select KTIME_SCALAR if 32BIT
123 config SCHED_OMIT_FRAME_POINTER
126 source "init/Kconfig"
128 source "kernel/Kconfig.freezer"
132 comment "Processor type and features"
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.
146 prompt "Symmetric multi-processing support"
148 This enables support for systems with more than one CPU. If you have
149 a system with only one CPU, like most personal computers, say N. If
150 you have a system with more than one CPU, say Y.
152 If you say N here, the kernel will run on single and multiprocessor
153 machines, but will use only one CPU of a multiprocessor machine. If
154 you say Y here, the kernel will run on many, but not all,
155 singleprocessor machines. On a singleprocessor machine, the kernel
156 will run faster if you say N here.
158 See also the SMP-HOWTO available at
159 <http://www.tldp.org/docs.html#howto>.
161 Even if you don't know what to do here, say Y.
164 int "Maximum number of CPUs (2-64)"
167 default "32" if !64BIT
168 default "64" if 64BIT
170 This allows you to specify the maximum number of CPUs which this
171 kernel will support. The maximum supported value is 64 and the
172 minimum value which makes sense is 2.
174 This is purely to save memory - each supported CPU adds
175 approximately sixteen kilobytes to the kernel image.
179 prompt "Support for hot-pluggable CPUs"
183 Say Y here to be able to turn CPUs off and on. CPUs
184 can be controlled through /sys/devices/system/cpu/cpu#.
185 Say N if you want to disable CPU hotplug.
192 prompt "Book scheduler support"
196 Book scheduler support improves the CPU scheduler's decision making
197 when dealing with machines that have several books.
201 prompt "IEEE FPU emulation"
204 This option is required for IEEE compliant floating point arithmetic
205 on older ESA/390 machines. Say Y unless you know your machine doesn't
210 prompt "Kernel support for 31 bit emulation"
212 select COMPAT_BINFMT_ELF
213 select ARCH_WANT_OLD_COMPAT_IPC
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
221 def_bool y if COMPAT && SYSVIPC
224 def_bool y if COMPAT && KEYS
229 comment "Code generation options"
232 prompt "Processor type"
236 bool "System/390 model G5 and G6"
239 Select this to build a 31 bit kernel that works
240 on all ESA/390 and z/Architecture machines.
243 bool "IBM zSeries model z800 and z900"
245 Select this to enable optimizations for model z800/z900 (2064 and
246 2066 series). This will enable some optimizations that are not
247 available on older ESA/390 (31 Bit) only CPUs.
250 bool "IBM zSeries model z890 and z990"
252 Select this to enable optimizations for model z890/z990 (2084 and
253 2086 series). The kernel will be slightly faster but will not work
259 Select this to enable optimizations for IBM System z9 (2094 and
260 2096 series). The kernel will be slightly faster but will not work
264 bool "IBM System z10"
266 Select this to enable optimizations for IBM System z10 (2097 and
267 2098 series). The kernel will be slightly faster but will not work
271 bool "IBM zEnterprise 114 and 196"
273 Select this to enable optimizations for IBM zEnterprise 114 and 196
274 (2818 and 2817 series). The kernel will be slightly faster but will
275 not work on older machines.
281 prompt "Pack kernel stack"
283 This option enables the compiler option -mkernel-backchain if it
284 is available. If the option is available the compiler supports
285 the new stack layout which dramatically reduces the minimum stack
286 frame size. With an old compiler a non-leaf function needs a
287 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
288 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
289 and 24 byte on 64 bit.
291 Say Y if you are unsure.
295 prompt "Use 8kb for kernel stack instead of 16kb"
296 depends on PACK_STACK && 64BIT && !LOCKDEP
298 If you say Y here and the compiler supports the -mkernel-backchain
299 option the kernel will use a smaller kernel stack size. The reduced
300 size is 8kb instead of 16kb. This allows to run more threads on a
301 system and reduces the pressure on the memory management for higher
302 order page allocations.
304 Say N if you are unsure.
308 prompt "Detect kernel stack overflow"
310 This option enables the compiler option -mstack-guard and
311 -mstack-size if they are available. If the compiler supports them
312 it will emit additional code to each function prolog to trigger
313 an illegal operation if the kernel stack is about to overflow.
315 Say N if you are unsure.
318 int "Size of the guard area (128-1024)"
320 depends on CHECK_STACK
323 This allows you to specify the size of the guard area at the lower
324 end of the kernel stack. If the kernel stack points into the guard
325 area on function entry an illegal operation is triggered. The size
326 needs to be a power of 2. Please keep in mind that the size of an
327 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
328 The minimum size for the stack guard should be 256 for 31 bit and
331 config WARN_DYNAMIC_STACK
333 prompt "Emit compiler warnings for function with dynamic stack usage"
335 This option enables the compiler option -mwarn-dynamicstack. If the
336 compiler supports this options generates warnings for functions
337 that dynamically allocate stack space using alloca.
339 Say N if you are unsure.
341 comment "Kernel preemption"
343 source "kernel/Kconfig.preempt"
345 config ARCH_SPARSEMEM_ENABLE
347 select SPARSEMEM_VMEMMAP_ENABLE
348 select SPARSEMEM_VMEMMAP
349 select SPARSEMEM_STATIC if !64BIT
351 config ARCH_SPARSEMEM_DEFAULT
354 config ARCH_SELECT_MEMORY_MODEL
357 config ARCH_ENABLE_MEMORY_HOTPLUG
358 def_bool y if SPARSEMEM
360 config ARCH_ENABLE_MEMORY_HOTREMOVE
363 config ARCH_HIBERNATION_POSSIBLE
368 comment "I/O subsystem configuration"
372 prompt "QDIO support"
374 This driver provides the Queued Direct I/O base support for
377 To compile this driver as a module, choose M here: the
378 module will be called qdio.
384 prompt "Support for CHSC subchannels"
386 This driver allows usage of CHSC subchannels. A CHSC subchannel
387 is usually present on LPAR only.
388 The driver creates a device /dev/chsc, which may be used to
389 obtain I/O configuration information about the machine and
390 to issue asynchronous chsc commands (DANGEROUS).
391 You will usually only want to use this interface on a special
392 LPAR designated for system management.
394 To compile this driver as a module, choose M here: the
395 module will be called chsc_sch.
403 prompt "Builtin IPL record support"
405 If you want to use the produced kernel to IPL directly from a
406 device, you have to merge a bootsector specific to the device
407 into the first bytes of the kernel. You will have to select the
411 prompt "IPL method generated into head.S"
415 Select "tape" if you want to IPL the image from a Tape.
417 Select "vm_reader" if you are running under VM/ESA and want
418 to IPL the image from the emulated card reader.
428 source "fs/Kconfig.binfmt"
430 config FORCE_MAX_ZONEORDER
436 prompt "Pseudo page fault support"
438 Select this option, if you want to use PFAULT pseudo page fault
439 handling under VM. If running native or in LPAR, this option
440 has no effect. If your VM does not support PFAULT, PAGEEX
441 pseudo page fault handling will be used.
442 Note that VM 4.2 supports PFAULT but has a bug in its
443 implementation that causes some problems.
444 Everybody who wants to run Linux under VM != VM4.2 should select
449 prompt "VM shared kernel support"
451 Select this option, if you want to share the text segment of the
452 Linux kernel between different VM guests. This reduces memory
453 usage with lots of guests but greatly increases kernel size.
454 Also if a kernel was IPL'ed from a shared segment the kexec system
456 You should only select this option if you know what you are
457 doing and want to exploit this feature.
461 prompt "Cooperative memory management"
463 Select this option, if you want to enable the kernel interface
464 to reduce the memory size of the system. This is accomplished
465 by allocating pages of memory and put them "on hold". This only
466 makes sense for a system running under VM where the unused pages
467 will be reused by VM for other guest systems. The interface
468 allows an external monitor to balance memory of many systems.
469 Everybody who wants to run Linux under VM should select this
474 prompt "IUCV special message interface to cooperative memory management"
475 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
477 Select this option to enable the special message interface to
478 the cooperative memory management.
482 prompt "Linux - VM Monitor Stream, base infrastructure"
485 This provides a kernel interface for creating and updating z/VM APPLDATA
486 monitor records. The monitor records are updated at certain time
487 intervals, once the timer is started.
488 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
489 i.e. enables or disables monitoring on the Linux side.
490 A custom interval value (in seconds) can be written to
491 /proc/appldata/interval.
493 Defaults are 60 seconds interval and timer off.
494 The /proc entries can also be read from, showing the current settings.
498 prompt "Monitor memory management statistics"
499 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
501 This provides memory management related data to the Linux - VM Monitor
502 Stream, like paging/swapping rate, memory utilisation, etc.
503 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
504 APPLDATA monitor record, i.e. enables or disables monitoring this record
508 The /proc entry can also be read from, showing the current settings.
510 This can also be compiled as a module, which will be called
515 prompt "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
530 prompt "Monitor overall network statistics"
531 depends on APPLDATA_BASE && NET
533 This provides network related data to the Linux - VM Monitor Stream,
534 currently there is only a total sum of network I/O statistics, no
536 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
537 APPLDATA monitor record, i.e. enables or disables monitoring this record
541 This can also be compiled as a module, which will be called
544 source kernel/Kconfig.hz
548 prompt "s390 hypervisor file system support"
549 select SYS_HYPERVISOR
551 This is a virtual file system intended to provide accounting
552 information in an s390 hypervisor environment.
556 prompt "kexec system call"
558 kexec is a system call that implements the ability to shutdown your
559 current kernel, and to start another kernel. It is like a reboot
560 but is independent of hardware/microcode support.
563 bool "kernel crash dumps"
567 Generate crash dump after being started by kexec.
568 Crash dump kernels are loaded in the main kernel with kexec-tools
569 into a specially reserved region and then later executed after
570 a crash by kdump/kexec.
571 For more details see Documentation/kdump/kdump.txt
575 prompt "zfcpdump support"
578 Select this option if you want to build an zfcpdump enabled kernel.
579 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
583 prompt "s390 guest support for KVM (EXPERIMENTAL)"
584 depends on 64BIT && EXPERIMENTAL
585 select VIRTUALIZATION
588 select VIRTIO_CONSOLE
590 Select this option if you want to run the kernel as a guest under
591 the KVM hypervisor. This will add detection for KVM as well as a
592 virtio transport. If KVM is detected, the virtio console will be
597 prompt "Enable seccomp to safely compute untrusted bytecode"
600 This kernel feature is useful for number crunching applications
601 that may need to compute untrusted bytecode during their
602 execution. By using pipes or other transports made available to
603 the process as file descriptors supporting the read/write
604 syscalls, it's possible to isolate those applications in
605 their own address space using seccomp. Once seccomp is
606 enabled via /proc/<pid>/seccomp, it cannot be disabled
607 and the task is only allowed to execute a few safe syscalls
608 defined by each seccomp mode.
614 menu "Power Management"
616 source "kernel/power/Kconfig"
628 source "drivers/Kconfig"
632 source "arch/s390/Kconfig.debug"
634 source "security/Kconfig"
636 source "crypto/Kconfig"
640 source "arch/s390/kvm/Kconfig"