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_SMP_IDLE_THREAD
120 select GENERIC_TIME_VSYSCALL
121 select GENERIC_CLOCKEVENTS
122 select KTIME_SCALAR if 32BIT
124 config SCHED_OMIT_FRAME_POINTER
127 source "init/Kconfig"
129 source "kernel/Kconfig.freezer"
133 comment "Processor type and features"
137 prompt "64 bit kernel"
139 Select this option if you have an IBM z/Architecture machine
140 and want to use the 64 bit addressing mode.
147 prompt "Symmetric multi-processing support"
149 This enables support for systems with more than one CPU. If you have
150 a system with only one CPU, like most personal computers, say N. If
151 you have a system with more than one CPU, say Y.
153 If you say N here, the kernel will run on single and multiprocessor
154 machines, but will use only one CPU of a multiprocessor machine. If
155 you say Y here, the kernel will run on many, but not all,
156 singleprocessor machines. On a singleprocessor machine, the kernel
157 will run faster if you say N here.
159 See also the SMP-HOWTO available at
160 <http://www.tldp.org/docs.html#howto>.
162 Even if you don't know what to do here, say Y.
165 int "Maximum number of CPUs (2-64)"
168 default "32" if !64BIT
169 default "64" if 64BIT
171 This allows you to specify the maximum number of CPUs which this
172 kernel will support. The maximum supported value is 64 and the
173 minimum value which makes sense is 2.
175 This is purely to save memory - each supported CPU adds
176 approximately sixteen kilobytes to the kernel image.
180 prompt "Support for hot-pluggable CPUs"
184 Say Y here to be able to turn CPUs off and on. CPUs
185 can be controlled through /sys/devices/system/cpu/cpu#.
186 Say N if you want to disable CPU hotplug.
193 prompt "Book scheduler support"
197 Book scheduler support improves the CPU scheduler's decision making
198 when dealing with machines that have several books.
202 prompt "IEEE FPU emulation"
205 This option is required for IEEE compliant floating point arithmetic
206 on older ESA/390 machines. Say Y unless you know your machine doesn't
211 prompt "Kernel support for 31 bit emulation"
213 select COMPAT_BINFMT_ELF if BINFMT_ELF
214 select ARCH_WANT_OLD_COMPAT_IPC
216 Select this option if you want to enable your system kernel to
217 handle system-calls from ELF binaries for 31 bit ESA. This option
218 (and some other stuff like libraries and such) is needed for
219 executing 31 bit applications. It is safe to say "Y".
221 config SYSVIPC_COMPAT
222 def_bool y if COMPAT && SYSVIPC
225 def_bool y if COMPAT && KEYS
230 config HAVE_MARCH_Z900_FEATURES
233 config HAVE_MARCH_Z990_FEATURES
235 select HAVE_MARCH_Z900_FEATURES
237 config HAVE_MARCH_Z9_109_FEATURES
239 select HAVE_MARCH_Z990_FEATURES
241 config HAVE_MARCH_Z10_FEATURES
243 select HAVE_MARCH_Z9_109_FEATURES
245 config HAVE_MARCH_Z196_FEATURES
247 select HAVE_MARCH_Z10_FEATURES
249 comment "Code generation options"
252 prompt "Processor type"
256 bool "System/390 model G5 and G6"
259 Select this to build a 31 bit kernel that works
260 on all ESA/390 and z/Architecture machines.
263 bool "IBM zSeries model z800 and z900"
264 select HAVE_MARCH_Z900_FEATURES if 64BIT
266 Select this to enable optimizations for model z800/z900 (2064 and
267 2066 series). This will enable some optimizations that are not
268 available on older ESA/390 (31 Bit) only CPUs.
271 bool "IBM zSeries model z890 and z990"
272 select HAVE_MARCH_Z990_FEATURES if 64BIT
274 Select this to enable optimizations for model z890/z990 (2084 and
275 2086 series). The kernel will be slightly faster but will not work
280 select HAVE_MARCH_Z9_109_FEATURES if 64BIT
282 Select this to enable optimizations for IBM System z9 (2094 and
283 2096 series). The kernel will be slightly faster but will not work
287 bool "IBM System z10"
288 select HAVE_MARCH_Z10_FEATURES if 64BIT
290 Select this to enable optimizations for IBM System z10 (2097 and
291 2098 series). The kernel will be slightly faster but will not work
295 bool "IBM zEnterprise 114 and 196"
296 select HAVE_MARCH_Z196_FEATURES if 64BIT
298 Select this to enable optimizations for IBM zEnterprise 114 and 196
299 (2818 and 2817 series). The kernel will be slightly faster but will
300 not work on older machines.
306 prompt "Pack kernel stack"
308 This option enables the compiler option -mkernel-backchain if it
309 is available. If the option is available the compiler supports
310 the new stack layout which dramatically reduces the minimum stack
311 frame size. With an old compiler a non-leaf function needs a
312 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
313 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
314 and 24 byte on 64 bit.
316 Say Y if you are unsure.
320 prompt "Use 8kb for kernel stack instead of 16kb"
321 depends on PACK_STACK && 64BIT && !LOCKDEP
323 If you say Y here and the compiler supports the -mkernel-backchain
324 option the kernel will use a smaller kernel stack size. The reduced
325 size is 8kb instead of 16kb. This allows to run more threads on a
326 system and reduces the pressure on the memory management for higher
327 order page allocations.
329 Say N if you are unsure.
333 prompt "Detect kernel stack overflow"
335 This option enables the compiler option -mstack-guard and
336 -mstack-size if they are available. If the compiler supports them
337 it will emit additional code to each function prolog to trigger
338 an illegal operation if the kernel stack is about to overflow.
340 Say N if you are unsure.
343 int "Size of the guard area (128-1024)"
345 depends on CHECK_STACK
348 This allows you to specify the size of the guard area at the lower
349 end of the kernel stack. If the kernel stack points into the guard
350 area on function entry an illegal operation is triggered. The size
351 needs to be a power of 2. Please keep in mind that the size of an
352 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
353 The minimum size for the stack guard should be 256 for 31 bit and
356 config WARN_DYNAMIC_STACK
358 prompt "Emit compiler warnings for function with dynamic stack usage"
360 This option enables the compiler option -mwarn-dynamicstack. If the
361 compiler supports this options generates warnings for functions
362 that dynamically allocate stack space using alloca.
364 Say N if you are unsure.
366 comment "Kernel preemption"
368 source "kernel/Kconfig.preempt"
370 config ARCH_SPARSEMEM_ENABLE
372 select SPARSEMEM_VMEMMAP_ENABLE
373 select SPARSEMEM_VMEMMAP
374 select SPARSEMEM_STATIC if !64BIT
376 config ARCH_SPARSEMEM_DEFAULT
379 config ARCH_SELECT_MEMORY_MODEL
382 config ARCH_ENABLE_MEMORY_HOTPLUG
383 def_bool y if SPARSEMEM
385 config ARCH_ENABLE_MEMORY_HOTREMOVE
388 config ARCH_HIBERNATION_POSSIBLE
393 comment "I/O subsystem configuration"
397 prompt "QDIO support"
399 This driver provides the Queued Direct I/O base support for
402 To compile this driver as a module, choose M here: the
403 module will be called qdio.
409 prompt "Support for CHSC subchannels"
411 This driver allows usage of CHSC subchannels. A CHSC subchannel
412 is usually present on LPAR only.
413 The driver creates a device /dev/chsc, which may be used to
414 obtain I/O configuration information about the machine and
415 to issue asynchronous chsc commands (DANGEROUS).
416 You will usually only want to use this interface on a special
417 LPAR designated for system management.
419 To compile this driver as a module, choose M here: the
420 module will be called chsc_sch.
426 source "fs/Kconfig.binfmt"
428 config FORCE_MAX_ZONEORDER
434 prompt "Pseudo page fault support"
436 Select this option, if you want to use PFAULT pseudo page fault
437 handling under VM. If running native or in LPAR, this option
438 has no effect. If your VM does not support PFAULT, PAGEEX
439 pseudo page fault handling will be used.
440 Note that VM 4.2 supports PFAULT but has a bug in its
441 implementation that causes some problems.
442 Everybody who wants to run Linux under VM != VM4.2 should select
447 prompt "VM shared kernel support"
449 Select this option, if you want to share the text segment of the
450 Linux kernel between different VM guests. This reduces memory
451 usage with lots of guests but greatly increases kernel size.
452 Also if a kernel was IPL'ed from a shared segment the kexec system
454 You should only select this option if you know what you are
455 doing and want to exploit this feature.
459 prompt "Cooperative memory management"
461 Select this option, if you want to enable the kernel interface
462 to reduce the memory size of the system. This is accomplished
463 by allocating pages of memory and put them "on hold". This only
464 makes sense for a system running under VM where the unused pages
465 will be reused by VM for other guest systems. The interface
466 allows an external monitor to balance memory of many systems.
467 Everybody who wants to run Linux under VM should select this
472 prompt "IUCV special message interface to cooperative memory management"
473 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
475 Select this option to enable the special message interface to
476 the cooperative memory management.
480 prompt "Linux - VM Monitor Stream, base infrastructure"
483 This provides a kernel interface for creating and updating z/VM APPLDATA
484 monitor records. The monitor records are updated at certain time
485 intervals, once the timer is started.
486 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
487 i.e. enables or disables monitoring on the Linux side.
488 A custom interval value (in seconds) can be written to
489 /proc/appldata/interval.
491 Defaults are 60 seconds interval and timer off.
492 The /proc entries can also be read from, showing the current settings.
496 prompt "Monitor memory management statistics"
497 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
499 This provides memory management related data to the Linux - VM Monitor
500 Stream, like paging/swapping rate, memory utilisation, etc.
501 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
502 APPLDATA monitor record, i.e. enables or disables monitoring this record
506 The /proc entry can also be read from, showing the current settings.
508 This can also be compiled as a module, which will be called
513 prompt "Monitor OS statistics"
514 depends on APPLDATA_BASE
516 This provides OS related data to the Linux - VM Monitor Stream, like
517 CPU utilisation, etc.
518 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
519 APPLDATA monitor record, i.e. enables or disables monitoring this record
523 This can also be compiled as a module, which will be called
526 config APPLDATA_NET_SUM
528 prompt "Monitor overall network statistics"
529 depends on APPLDATA_BASE && NET
531 This provides network related data to the Linux - VM Monitor Stream,
532 currently there is only a total sum of network I/O statistics, no
534 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
535 APPLDATA monitor record, i.e. enables or disables monitoring this record
539 This can also be compiled as a module, which will be called
542 source kernel/Kconfig.hz
546 prompt "s390 hypervisor file system support"
547 select SYS_HYPERVISOR
549 This is a virtual file system intended to provide accounting
550 information in an s390 hypervisor environment.
554 prompt "kexec system call"
556 kexec is a system call that implements the ability to shutdown your
557 current kernel, and to start another kernel. It is like a reboot
558 but is independent of hardware/microcode support.
561 bool "kernel crash dumps"
562 depends on 64BIT && SMP
565 Generate crash dump after being started by kexec.
566 Crash dump kernels are loaded in the main kernel with kexec-tools
567 into a specially reserved region and then later executed after
568 a crash by kdump/kexec.
569 For more details see Documentation/kdump/kdump.txt
573 prompt "zfcpdump support"
576 Select this option if you want to build an zfcpdump enabled kernel.
577 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
581 prompt "s390 guest support for KVM (EXPERIMENTAL)"
582 depends on 64BIT && EXPERIMENTAL
583 select VIRTUALIZATION
586 select VIRTIO_CONSOLE
588 Select this option if you want to run the kernel as a guest under
589 the KVM hypervisor. This will add detection for KVM as well as a
590 virtio transport. If KVM is detected, the virtio console will be
595 prompt "Enable seccomp to safely compute untrusted bytecode"
598 This kernel feature is useful for number crunching applications
599 that may need to compute untrusted bytecode during their
600 execution. By using pipes or other transports made available to
601 the process as file descriptors supporting the read/write
602 syscalls, it's possible to isolate those applications in
603 their own address space using seccomp. Once seccomp is
604 enabled via /proc/<pid>/seccomp, it cannot be disabled
605 and the task is only allowed to execute a few safe syscalls
606 defined by each seccomp mode.
612 menu "Power Management"
614 source "kernel/power/Kconfig"
626 source "drivers/Kconfig"
630 source "arch/s390/Kconfig.debug"
632 source "security/Kconfig"
634 source "crypto/Kconfig"
638 source "arch/s390/kvm/Kconfig"