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 HAVE_RCU_TABLE_FREE if SMP
94 select ARCH_SAVE_PAGE_KEYS if HIBERNATION
95 select ARCH_INLINE_SPIN_TRYLOCK
96 select ARCH_INLINE_SPIN_TRYLOCK_BH
97 select ARCH_INLINE_SPIN_LOCK
98 select ARCH_INLINE_SPIN_LOCK_BH
99 select ARCH_INLINE_SPIN_LOCK_IRQ
100 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
101 select ARCH_INLINE_SPIN_UNLOCK
102 select ARCH_INLINE_SPIN_UNLOCK_BH
103 select ARCH_INLINE_SPIN_UNLOCK_IRQ
104 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
105 select ARCH_INLINE_READ_TRYLOCK
106 select ARCH_INLINE_READ_LOCK
107 select ARCH_INLINE_READ_LOCK_BH
108 select ARCH_INLINE_READ_LOCK_IRQ
109 select ARCH_INLINE_READ_LOCK_IRQSAVE
110 select ARCH_INLINE_READ_UNLOCK
111 select ARCH_INLINE_READ_UNLOCK_BH
112 select ARCH_INLINE_READ_UNLOCK_IRQ
113 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
114 select ARCH_INLINE_WRITE_TRYLOCK
115 select ARCH_INLINE_WRITE_LOCK
116 select ARCH_INLINE_WRITE_LOCK_BH
117 select ARCH_INLINE_WRITE_LOCK_IRQ
118 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
119 select ARCH_INLINE_WRITE_UNLOCK
120 select ARCH_INLINE_WRITE_UNLOCK_BH
121 select ARCH_INLINE_WRITE_UNLOCK_IRQ
122 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
123 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
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.
196 prompt "Multi-core scheduler support"
199 Multi-core scheduler support improves the CPU scheduler's decision
200 making when dealing with multi-core CPU chips at a cost of slightly
201 increased overhead in some places.
205 prompt "Book scheduler support"
206 depends on SMP && SCHED_MC
208 Book scheduler support improves the CPU scheduler's decision making
209 when dealing with machines that have several books.
213 prompt "IEEE FPU emulation"
216 This option is required for IEEE compliant floating point arithmetic
217 on older ESA/390 machines. Say Y unless you know your machine doesn't
222 prompt "Kernel support for 31 bit emulation"
224 select COMPAT_BINFMT_ELF
226 Select this option if you want to enable your system kernel to
227 handle system-calls from ELF binaries for 31 bit ESA. This option
228 (and some other stuff like libraries and such) is needed for
229 executing 31 bit applications. It is safe to say "Y".
231 config SYSVIPC_COMPAT
232 def_bool y if COMPAT && SYSVIPC
237 comment "Code generation options"
240 prompt "Processor type"
244 bool "System/390 model G5 and G6"
247 Select this to build a 31 bit kernel that works
248 on all ESA/390 and z/Architecture machines.
251 bool "IBM zSeries model z800 and z900"
253 Select this to enable optimizations for model z800/z900 (2064 and
254 2066 series). This will enable some optimizations that are not
255 available on older ESA/390 (31 Bit) only CPUs.
258 bool "IBM zSeries model z890 and z990"
260 Select this to enable optimizations for model z890/z990 (2084 and
261 2086 series). The kernel will be slightly faster but will not work
267 Select this to enable optimizations for IBM System z9 (2094 and
268 2096 series). The kernel will be slightly faster but will not work
272 bool "IBM System z10"
274 Select this to enable optimizations for IBM System z10 (2097 and
275 2098 series). The kernel will be slightly faster but will not work
279 bool "IBM zEnterprise 114 and 196"
281 Select this to enable optimizations for IBM zEnterprise 114 and 196
282 (2818 and 2817 series). The kernel will be slightly faster but will
283 not work on older machines.
289 prompt "Pack kernel stack"
291 This option enables the compiler option -mkernel-backchain if it
292 is available. If the option is available the compiler supports
293 the new stack layout which dramatically reduces the minimum stack
294 frame size. With an old compiler a non-leaf function needs a
295 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
296 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
297 and 24 byte on 64 bit.
299 Say Y if you are unsure.
303 prompt "Use 8kb for kernel stack instead of 16kb"
304 depends on PACK_STACK && 64BIT && !LOCKDEP
306 If you say Y here and the compiler supports the -mkernel-backchain
307 option the kernel will use a smaller kernel stack size. The reduced
308 size is 8kb instead of 16kb. This allows to run more threads on a
309 system and reduces the pressure on the memory management for higher
310 order page allocations.
312 Say N if you are unsure.
316 prompt "Detect kernel stack overflow"
318 This option enables the compiler option -mstack-guard and
319 -mstack-size if they are available. If the compiler supports them
320 it will emit additional code to each function prolog to trigger
321 an illegal operation if the kernel stack is about to overflow.
323 Say N if you are unsure.
326 int "Size of the guard area (128-1024)"
328 depends on CHECK_STACK
331 This allows you to specify the size of the guard area at the lower
332 end of the kernel stack. If the kernel stack points into the guard
333 area on function entry an illegal operation is triggered. The size
334 needs to be a power of 2. Please keep in mind that the size of an
335 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
336 The minimum size for the stack guard should be 256 for 31 bit and
339 config WARN_DYNAMIC_STACK
341 prompt "Emit compiler warnings for function with dynamic stack usage"
343 This option enables the compiler option -mwarn-dynamicstack. If the
344 compiler supports this options generates warnings for functions
345 that dynamically allocate stack space using alloca.
347 Say N if you are unsure.
349 config ARCH_POPULATES_NODE_MAP
352 comment "Kernel preemption"
354 source "kernel/Kconfig.preempt"
356 config ARCH_SPARSEMEM_ENABLE
358 select SPARSEMEM_VMEMMAP_ENABLE
359 select SPARSEMEM_VMEMMAP
360 select SPARSEMEM_STATIC if !64BIT
362 config ARCH_SPARSEMEM_DEFAULT
365 config ARCH_SELECT_MEMORY_MODEL
368 config ARCH_ENABLE_MEMORY_HOTPLUG
369 def_bool y if SPARSEMEM
371 config ARCH_ENABLE_MEMORY_HOTREMOVE
374 config ARCH_HIBERNATION_POSSIBLE
379 comment "I/O subsystem configuration"
383 prompt "QDIO support"
385 This driver provides the Queued Direct I/O base support for
388 To compile this driver as a module, choose M here: the
389 module will be called qdio.
395 prompt "Support for CHSC subchannels"
397 This driver allows usage of CHSC subchannels. A CHSC subchannel
398 is usually present on LPAR only.
399 The driver creates a device /dev/chsc, which may be used to
400 obtain I/O configuration information about the machine and
401 to issue asynchronous chsc commands (DANGEROUS).
402 You will usually only want to use this interface on a special
403 LPAR designated for system management.
405 To compile this driver as a module, choose M here: the
406 module will be called chsc_sch.
414 prompt "Builtin IPL record support"
416 If you want to use the produced kernel to IPL directly from a
417 device, you have to merge a bootsector specific to the device
418 into the first bytes of the kernel. You will have to select the
422 prompt "IPL method generated into head.S"
426 Select "tape" if you want to IPL the image from a Tape.
428 Select "vm_reader" if you are running under VM/ESA and want
429 to IPL the image from the emulated card reader.
439 source "fs/Kconfig.binfmt"
441 config FORCE_MAX_ZONEORDER
447 prompt "Pseudo page fault support"
449 Select this option, if you want to use PFAULT pseudo page fault
450 handling under VM. If running native or in LPAR, this option
451 has no effect. If your VM does not support PFAULT, PAGEEX
452 pseudo page fault handling will be used.
453 Note that VM 4.2 supports PFAULT but has a bug in its
454 implementation that causes some problems.
455 Everybody who wants to run Linux under VM != VM4.2 should select
460 prompt "VM shared kernel support"
462 Select this option, if you want to share the text segment of the
463 Linux kernel between different VM guests. This reduces memory
464 usage with lots of guests but greatly increases kernel size.
465 Also if a kernel was IPL'ed from a shared segment the kexec system
467 You should only select this option if you know what you are
468 doing and want to exploit this feature.
472 prompt "Cooperative memory management"
474 Select this option, if you want to enable the kernel interface
475 to reduce the memory size of the system. This is accomplished
476 by allocating pages of memory and put them "on hold". This only
477 makes sense for a system running under VM where the unused pages
478 will be reused by VM for other guest systems. The interface
479 allows an external monitor to balance memory of many systems.
480 Everybody who wants to run Linux under VM should select this
485 prompt "IUCV special message interface to cooperative memory management"
486 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
488 Select this option to enable the special message interface to
489 the cooperative memory management.
493 prompt "Linux - VM Monitor Stream, base infrastructure"
496 This provides a kernel interface for creating and updating z/VM APPLDATA
497 monitor records. The monitor records are updated at certain time
498 intervals, once the timer is started.
499 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
500 i.e. enables or disables monitoring on the Linux side.
501 A custom interval value (in seconds) can be written to
502 /proc/appldata/interval.
504 Defaults are 60 seconds interval and timer off.
505 The /proc entries can also be read from, showing the current settings.
509 prompt "Monitor memory management statistics"
510 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
512 This provides memory management related data to the Linux - VM Monitor
513 Stream, like paging/swapping rate, memory utilisation, etc.
514 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
515 APPLDATA monitor record, i.e. enables or disables monitoring this record
519 The /proc entry can also be read from, showing the current settings.
521 This can also be compiled as a module, which will be called
526 prompt "Monitor OS statistics"
527 depends on APPLDATA_BASE
529 This provides OS related data to the Linux - VM Monitor Stream, like
530 CPU utilisation, etc.
531 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
532 APPLDATA monitor record, i.e. enables or disables monitoring this record
536 This can also be compiled as a module, which will be called
539 config APPLDATA_NET_SUM
541 prompt "Monitor overall network statistics"
542 depends on APPLDATA_BASE && NET
544 This provides network related data to the Linux - VM Monitor Stream,
545 currently there is only a total sum of network I/O statistics, no
547 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
548 APPLDATA monitor record, i.e. enables or disables monitoring this record
552 This can also be compiled as a module, which will be called
555 source kernel/Kconfig.hz
559 prompt "s390 hypervisor file system support"
560 select SYS_HYPERVISOR
562 This is a virtual file system intended to provide accounting
563 information in an s390 hypervisor environment.
567 prompt "kexec system call"
569 kexec is a system call that implements the ability to shutdown your
570 current kernel, and to start another kernel. It is like a reboot
571 but is independent of hardware/microcode support.
574 bool "kernel crash dumps"
577 Generate crash dump after being started by kexec.
578 Crash dump kernels are loaded in the main kernel with kexec-tools
579 into a specially reserved region and then later executed after
580 a crash by kdump/kexec.
581 For more details see Documentation/kdump/kdump.txt
585 prompt "zfcpdump support"
588 Select this option if you want to build an zfcpdump enabled kernel.
589 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
593 prompt "s390 guest support for KVM (EXPERIMENTAL)"
594 depends on 64BIT && EXPERIMENTAL
595 select VIRTUALIZATION
598 select VIRTIO_CONSOLE
600 Select this option if you want to run the kernel as a guest under
601 the KVM hypervisor. This will add detection for KVM as well as a
602 virtio transport. If KVM is detected, the virtio console will be
607 prompt "Enable seccomp to safely compute untrusted bytecode"
610 This kernel feature is useful for number crunching applications
611 that may need to compute untrusted bytecode during their
612 execution. By using pipes or other transports made available to
613 the process as file descriptors supporting the read/write
614 syscalls, it's possible to isolate those applications in
615 their own address space using seccomp. Once seccomp is
616 enabled via /proc/<pid>/seccomp, it cannot be disabled
617 and the task is only allowed to execute a few safe syscalls
618 defined by each seccomp mode.
624 menu "Power Management"
626 source "kernel/power/Kconfig"
638 source "drivers/Kconfig"
642 source "arch/s390/Kconfig.debug"
644 source "security/Kconfig"
646 source "crypto/Kconfig"
650 source "arch/s390/kvm/Kconfig"