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 HAVE_CMPXCHG_LOCAL
91 select ARCH_DISCARD_MEMBLOCK
92 select ARCH_INLINE_SPIN_TRYLOCK
93 select ARCH_INLINE_SPIN_TRYLOCK_BH
94 select ARCH_INLINE_SPIN_LOCK
95 select ARCH_INLINE_SPIN_LOCK_BH
96 select ARCH_INLINE_SPIN_LOCK_IRQ
97 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
98 select ARCH_INLINE_SPIN_UNLOCK
99 select ARCH_INLINE_SPIN_UNLOCK_BH
100 select ARCH_INLINE_SPIN_UNLOCK_IRQ
101 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
102 select ARCH_INLINE_READ_TRYLOCK
103 select ARCH_INLINE_READ_LOCK
104 select ARCH_INLINE_READ_LOCK_BH
105 select ARCH_INLINE_READ_LOCK_IRQ
106 select ARCH_INLINE_READ_LOCK_IRQSAVE
107 select ARCH_INLINE_READ_UNLOCK
108 select ARCH_INLINE_READ_UNLOCK_BH
109 select ARCH_INLINE_READ_UNLOCK_IRQ
110 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
111 select ARCH_INLINE_WRITE_TRYLOCK
112 select ARCH_INLINE_WRITE_LOCK
113 select ARCH_INLINE_WRITE_LOCK_BH
114 select ARCH_INLINE_WRITE_LOCK_IRQ
115 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
116 select ARCH_INLINE_WRITE_UNLOCK
117 select ARCH_INLINE_WRITE_UNLOCK_BH
118 select ARCH_INLINE_WRITE_UNLOCK_IRQ
119 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
120 select GENERIC_SMP_IDLE_THREAD
121 select GENERIC_TIME_VSYSCALL
122 select GENERIC_CLOCKEVENTS
123 select KTIME_SCALAR if 32BIT
125 config SCHED_OMIT_FRAME_POINTER
128 source "init/Kconfig"
130 source "kernel/Kconfig.freezer"
134 comment "Processor type and features"
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.
148 prompt "Symmetric multi-processing support"
150 This enables support for systems with more than one CPU. If you have
151 a system with only one CPU, like most personal computers, say N. If
152 you have a system with more than one CPU, say Y.
154 If you say N here, the kernel will run on single and multiprocessor
155 machines, but will use only one CPU of a multiprocessor machine. If
156 you say Y here, the kernel will run on many, but not all,
157 singleprocessor machines. On a singleprocessor machine, the kernel
158 will run faster if you say N here.
160 See also the SMP-HOWTO available at
161 <http://www.tldp.org/docs.html#howto>.
163 Even if you don't know what to do here, say Y.
166 int "Maximum number of CPUs (2-64)"
169 default "32" if !64BIT
170 default "64" if 64BIT
172 This allows you to specify the maximum number of CPUs which this
173 kernel will support. The maximum supported value is 64 and the
174 minimum value which makes sense is 2.
176 This is purely to save memory - each supported CPU adds
177 approximately sixteen kilobytes to the kernel image.
181 prompt "Support for hot-pluggable CPUs"
185 Say Y here to be able to turn CPUs off and on. CPUs
186 can be controlled through /sys/devices/system/cpu/cpu#.
187 Say N if you want to disable CPU hotplug.
194 prompt "Book scheduler support"
198 Book scheduler support improves the CPU scheduler's decision making
199 when dealing with machines that have several books.
203 prompt "IEEE FPU emulation"
206 This option is required for IEEE compliant floating point arithmetic
207 on older ESA/390 machines. Say Y unless you know your machine doesn't
212 prompt "Kernel support for 31 bit emulation"
214 select COMPAT_BINFMT_ELF if BINFMT_ELF
215 select ARCH_WANT_OLD_COMPAT_IPC
217 Select this option if you want to enable your system kernel to
218 handle system-calls from ELF binaries for 31 bit ESA. This option
219 (and some other stuff like libraries and such) is needed for
220 executing 31 bit applications. It is safe to say "Y".
222 config SYSVIPC_COMPAT
223 def_bool y if COMPAT && SYSVIPC
226 def_bool y if COMPAT && KEYS
231 config HAVE_MARCH_Z900_FEATURES
234 config HAVE_MARCH_Z990_FEATURES
236 select HAVE_MARCH_Z900_FEATURES
238 config HAVE_MARCH_Z9_109_FEATURES
240 select HAVE_MARCH_Z990_FEATURES
242 config HAVE_MARCH_Z10_FEATURES
244 select HAVE_MARCH_Z9_109_FEATURES
246 config HAVE_MARCH_Z196_FEATURES
248 select HAVE_MARCH_Z10_FEATURES
250 comment "Code generation options"
253 prompt "Processor type"
257 bool "System/390 model G5 and G6"
260 Select this to build a 31 bit kernel that works
261 on all ESA/390 and z/Architecture machines.
264 bool "IBM zSeries model z800 and z900"
265 select HAVE_MARCH_Z900_FEATURES if 64BIT
267 Select this to enable optimizations for model z800/z900 (2064 and
268 2066 series). This will enable some optimizations that are not
269 available on older ESA/390 (31 Bit) only CPUs.
272 bool "IBM zSeries model z890 and z990"
273 select HAVE_MARCH_Z990_FEATURES if 64BIT
275 Select this to enable optimizations for model z890/z990 (2084 and
276 2086 series). The kernel will be slightly faster but will not work
281 select HAVE_MARCH_Z9_109_FEATURES if 64BIT
283 Select this to enable optimizations for IBM System z9 (2094 and
284 2096 series). The kernel will be slightly faster but will not work
288 bool "IBM System z10"
289 select HAVE_MARCH_Z10_FEATURES if 64BIT
291 Select this to enable optimizations for IBM System z10 (2097 and
292 2098 series). The kernel will be slightly faster but will not work
296 bool "IBM zEnterprise 114 and 196"
297 select HAVE_MARCH_Z196_FEATURES if 64BIT
299 Select this to enable optimizations for IBM zEnterprise 114 and 196
300 (2818 and 2817 series). The kernel will be slightly faster but will
301 not work on older machines.
307 prompt "Pack kernel stack"
309 This option enables the compiler option -mkernel-backchain if it
310 is available. If the option is available the compiler supports
311 the new stack layout which dramatically reduces the minimum stack
312 frame size. With an old compiler a non-leaf function needs a
313 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
314 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
315 and 24 byte on 64 bit.
317 Say Y if you are unsure.
321 prompt "Use 8kb for kernel stack instead of 16kb"
322 depends on PACK_STACK && 64BIT && !LOCKDEP
324 If you say Y here and the compiler supports the -mkernel-backchain
325 option the kernel will use a smaller kernel stack size. The reduced
326 size is 8kb instead of 16kb. This allows to run more threads on a
327 system and reduces the pressure on the memory management for higher
328 order page allocations.
330 Say N if you are unsure.
334 prompt "Detect kernel stack overflow"
336 This option enables the compiler option -mstack-guard and
337 -mstack-size if they are available. If the compiler supports them
338 it will emit additional code to each function prolog to trigger
339 an illegal operation if the kernel stack is about to overflow.
341 Say N if you are unsure.
344 int "Size of the guard area (128-1024)"
346 depends on CHECK_STACK
349 This allows you to specify the size of the guard area at the lower
350 end of the kernel stack. If the kernel stack points into the guard
351 area on function entry an illegal operation is triggered. The size
352 needs to be a power of 2. Please keep in mind that the size of an
353 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
354 The minimum size for the stack guard should be 256 for 31 bit and
357 config WARN_DYNAMIC_STACK
359 prompt "Emit compiler warnings for function with dynamic stack usage"
361 This option enables the compiler option -mwarn-dynamicstack. If the
362 compiler supports this options generates warnings for functions
363 that dynamically allocate stack space using alloca.
365 Say N if you are unsure.
367 comment "Kernel preemption"
369 source "kernel/Kconfig.preempt"
371 config ARCH_SPARSEMEM_ENABLE
373 select SPARSEMEM_VMEMMAP_ENABLE
374 select SPARSEMEM_VMEMMAP
375 select SPARSEMEM_STATIC if !64BIT
377 config ARCH_SPARSEMEM_DEFAULT
380 config ARCH_SELECT_MEMORY_MODEL
383 config ARCH_ENABLE_MEMORY_HOTPLUG
384 def_bool y if SPARSEMEM
386 config ARCH_ENABLE_MEMORY_HOTREMOVE
389 config ARCH_HIBERNATION_POSSIBLE
394 comment "I/O subsystem configuration"
398 prompt "QDIO support"
400 This driver provides the Queued Direct I/O base support for
403 To compile this driver as a module, choose M here: the
404 module will be called qdio.
410 prompt "Support for CHSC subchannels"
412 This driver allows usage of CHSC subchannels. A CHSC subchannel
413 is usually present on LPAR only.
414 The driver creates a device /dev/chsc, which may be used to
415 obtain I/O configuration information about the machine and
416 to issue asynchronous chsc commands (DANGEROUS).
417 You will usually only want to use this interface on a special
418 LPAR designated for system management.
420 To compile this driver as a module, choose M here: the
421 module will be called chsc_sch.
427 source "fs/Kconfig.binfmt"
429 config FORCE_MAX_ZONEORDER
435 prompt "Pseudo page fault support"
437 Select this option, if you want to use PFAULT pseudo page fault
438 handling under VM. If running native or in LPAR, this option
439 has no effect. If your VM does not support PFAULT, PAGEEX
440 pseudo page fault handling will be used.
441 Note that VM 4.2 supports PFAULT but has a bug in its
442 implementation that causes some problems.
443 Everybody who wants to run Linux under VM != VM4.2 should select
448 prompt "VM shared kernel support"
450 Select this option, if you want to share the text segment of the
451 Linux kernel between different VM guests. This reduces memory
452 usage with lots of guests but greatly increases kernel size.
453 Also if a kernel was IPL'ed from a shared segment the kexec system
455 You should only select this option if you know what you are
456 doing and want to exploit this feature.
460 prompt "Cooperative memory management"
462 Select this option, if you want to enable the kernel interface
463 to reduce the memory size of the system. This is accomplished
464 by allocating pages of memory and put them "on hold". This only
465 makes sense for a system running under VM where the unused pages
466 will be reused by VM for other guest systems. The interface
467 allows an external monitor to balance memory of many systems.
468 Everybody who wants to run Linux under VM should select this
473 prompt "IUCV special message interface to cooperative memory management"
474 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
476 Select this option to enable the special message interface to
477 the cooperative memory management.
481 prompt "Linux - VM Monitor Stream, base infrastructure"
484 This provides a kernel interface for creating and updating z/VM APPLDATA
485 monitor records. The monitor records are updated at certain time
486 intervals, once the timer is started.
487 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
488 i.e. enables or disables monitoring on the Linux side.
489 A custom interval value (in seconds) can be written to
490 /proc/appldata/interval.
492 Defaults are 60 seconds interval and timer off.
493 The /proc entries can also be read from, showing the current settings.
497 prompt "Monitor memory management statistics"
498 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
500 This provides memory management related data to the Linux - VM Monitor
501 Stream, like paging/swapping rate, memory utilisation, etc.
502 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
503 APPLDATA monitor record, i.e. enables or disables monitoring this record
507 The /proc entry can also be read from, showing the current settings.
509 This can also be compiled as a module, which will be called
514 prompt "Monitor OS statistics"
515 depends on APPLDATA_BASE
517 This provides OS related data to the Linux - VM Monitor Stream, like
518 CPU utilisation, etc.
519 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
520 APPLDATA monitor record, i.e. enables or disables monitoring this record
524 This can also be compiled as a module, which will be called
527 config APPLDATA_NET_SUM
529 prompt "Monitor overall network statistics"
530 depends on APPLDATA_BASE && NET
532 This provides network related data to the Linux - VM Monitor Stream,
533 currently there is only a total sum of network I/O statistics, no
535 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
536 APPLDATA monitor record, i.e. enables or disables monitoring this record
540 This can also be compiled as a module, which will be called
543 source kernel/Kconfig.hz
547 prompt "s390 hypervisor file system support"
548 select SYS_HYPERVISOR
550 This is a virtual file system intended to provide accounting
551 information in an s390 hypervisor environment.
555 prompt "kexec system call"
557 kexec is a system call that implements the ability to shutdown your
558 current kernel, and to start another kernel. It is like a reboot
559 but is independent of hardware/microcode support.
562 bool "kernel crash dumps"
563 depends on 64BIT && SMP
566 Generate crash dump after being started by kexec.
567 Crash dump kernels are loaded in the main kernel with kexec-tools
568 into a specially reserved region and then later executed after
569 a crash by kdump/kexec.
570 For more details see Documentation/kdump/kdump.txt
574 prompt "zfcpdump support"
577 Select this option if you want to build an zfcpdump enabled kernel.
578 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
582 prompt "s390 guest support for KVM (EXPERIMENTAL)"
583 depends on 64BIT && EXPERIMENTAL
584 select VIRTUALIZATION
587 select VIRTIO_CONSOLE
589 Select this option if you want to run the kernel as a guest under
590 the KVM hypervisor. This will add detection for KVM as well as a
591 virtio transport. If KVM is detected, the virtio console will be
596 prompt "Enable seccomp to safely compute untrusted bytecode"
599 This kernel feature is useful for number crunching applications
600 that may need to compute untrusted bytecode during their
601 execution. By using pipes or other transports made available to
602 the process as file descriptors supporting the read/write
603 syscalls, it's possible to isolate those applications in
604 their own address space using seccomp. Once seccomp is
605 enabled via /proc/<pid>/seccomp, it cannot be disabled
606 and the task is only allowed to execute a few safe syscalls
607 defined by each seccomp mode.
613 menu "Power Management"
615 source "kernel/power/Kconfig"
627 source "drivers/Kconfig"
631 source "arch/s390/Kconfig.debug"
633 source "security/Kconfig"
635 source "crypto/Kconfig"
639 source "arch/s390/kvm/Kconfig"