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 GENERIC_CPU_DEVICES if !SMP
68 select HAVE_SYSCALL_WRAPPERS
69 select HAVE_FUNCTION_TRACER
70 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
71 select HAVE_FTRACE_MCOUNT_RECORD
72 select HAVE_C_RECORDMCOUNT
73 select HAVE_SYSCALL_TRACEPOINTS
74 select HAVE_DYNAMIC_FTRACE
75 select HAVE_FUNCTION_GRAPH_TRACER
76 select HAVE_REGS_AND_STACK_ACCESS_API
79 select HAVE_KRETPROBES
80 select HAVE_KVM if 64BIT
81 select HAVE_ARCH_TRACEHOOK
82 select INIT_ALL_POSSIBLE
84 select HAVE_PERF_EVENTS
85 select ARCH_HAVE_NMI_SAFE_CMPXCHG
86 select HAVE_KERNEL_GZIP
87 select HAVE_KERNEL_BZIP2
88 select HAVE_KERNEL_LZMA
89 select HAVE_KERNEL_LZO
91 select HAVE_ARCH_MUTEX_CPU_RELAX
92 select HAVE_ARCH_JUMP_LABEL if !MARCH_G5
93 select ARCH_SAVE_PAGE_KEYS if HIBERNATION
95 select HAVE_MEMBLOCK_NODE_MAP
96 select ARCH_DISCARD_MEMBLOCK
97 select ARCH_INLINE_SPIN_TRYLOCK
98 select ARCH_INLINE_SPIN_TRYLOCK_BH
99 select ARCH_INLINE_SPIN_LOCK
100 select ARCH_INLINE_SPIN_LOCK_BH
101 select ARCH_INLINE_SPIN_LOCK_IRQ
102 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
103 select ARCH_INLINE_SPIN_UNLOCK
104 select ARCH_INLINE_SPIN_UNLOCK_BH
105 select ARCH_INLINE_SPIN_UNLOCK_IRQ
106 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
107 select ARCH_INLINE_READ_TRYLOCK
108 select ARCH_INLINE_READ_LOCK
109 select ARCH_INLINE_READ_LOCK_BH
110 select ARCH_INLINE_READ_LOCK_IRQ
111 select ARCH_INLINE_READ_LOCK_IRQSAVE
112 select ARCH_INLINE_READ_UNLOCK
113 select ARCH_INLINE_READ_UNLOCK_BH
114 select ARCH_INLINE_READ_UNLOCK_IRQ
115 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
116 select ARCH_INLINE_WRITE_TRYLOCK
117 select ARCH_INLINE_WRITE_LOCK
118 select ARCH_INLINE_WRITE_LOCK_BH
119 select ARCH_INLINE_WRITE_LOCK_IRQ
120 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
121 select ARCH_INLINE_WRITE_UNLOCK
122 select ARCH_INLINE_WRITE_UNLOCK_BH
123 select ARCH_INLINE_WRITE_UNLOCK_IRQ
124 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
126 config SCHED_OMIT_FRAME_POINTER
129 source "init/Kconfig"
131 source "kernel/Kconfig.freezer"
135 comment "Processor type and features"
137 source "kernel/time/Kconfig"
141 prompt "64 bit kernel"
143 Select this option if you have an IBM z/Architecture machine
144 and want to use the 64 bit addressing mode.
154 prompt "Symmetric multi-processing support"
156 This enables support for systems with more than one CPU. If you have
157 a system with only one CPU, like most personal computers, say N. If
158 you have a system with more than one CPU, say Y.
160 If you say N here, the kernel will run on single and multiprocessor
161 machines, but will use only one CPU of a multiprocessor machine. If
162 you say Y here, the kernel will run on many, but not all,
163 singleprocessor machines. On a singleprocessor machine, the kernel
164 will run faster if you say N here.
166 See also the SMP-HOWTO available at
167 <http://www.tldp.org/docs.html#howto>.
169 Even if you don't know what to do here, say Y.
172 int "Maximum number of CPUs (2-64)"
175 default "32" if !64BIT
176 default "64" if 64BIT
178 This allows you to specify the maximum number of CPUs which this
179 kernel will support. The maximum supported value is 64 and the
180 minimum value which makes sense is 2.
182 This is purely to save memory - each supported CPU adds
183 approximately sixteen kilobytes to the kernel image.
187 prompt "Support for hot-pluggable CPUs"
191 Say Y here to be able to turn CPUs off and on. CPUs
192 can be controlled through /sys/devices/system/cpu/cpu#.
193 Say N if you want to disable CPU hotplug.
200 prompt "Book scheduler support"
204 Book scheduler support improves the CPU scheduler's decision making
205 when dealing with machines that have several books.
209 prompt "IEEE FPU emulation"
212 This option is required for IEEE compliant floating point arithmetic
213 on older ESA/390 machines. Say Y unless you know your machine doesn't
218 prompt "Kernel support for 31 bit emulation"
220 select COMPAT_BINFMT_ELF if BINFMT_ELF
221 select ARCH_WANT_OLD_COMPAT_IPC
223 Select this option if you want to enable your system kernel to
224 handle system-calls from ELF binaries for 31 bit ESA. This option
225 (and some other stuff like libraries and such) is needed for
226 executing 31 bit applications. It is safe to say "Y".
228 config SYSVIPC_COMPAT
229 def_bool y if COMPAT && SYSVIPC
232 def_bool y if COMPAT && KEYS
237 config HAVE_MARCH_Z900_FEATURES
240 config HAVE_MARCH_Z990_FEATURES
242 select HAVE_MARCH_Z900_FEATURES
244 config HAVE_MARCH_Z9_109_FEATURES
246 select HAVE_MARCH_Z990_FEATURES
248 config HAVE_MARCH_Z10_FEATURES
250 select HAVE_MARCH_Z9_109_FEATURES
252 config HAVE_MARCH_Z196_FEATURES
254 select HAVE_MARCH_Z10_FEATURES
256 comment "Code generation options"
259 prompt "Processor type"
263 bool "System/390 model G5 and G6"
266 Select this to build a 31 bit kernel that works
267 on all ESA/390 and z/Architecture machines.
270 bool "IBM zSeries model z800 and z900"
271 select HAVE_MARCH_Z900_FEATURES if 64BIT
273 Select this to enable optimizations for model z800/z900 (2064 and
274 2066 series). This will enable some optimizations that are not
275 available on older ESA/390 (31 Bit) only CPUs.
278 bool "IBM zSeries model z890 and z990"
279 select HAVE_MARCH_Z990_FEATURES if 64BIT
281 Select this to enable optimizations for model z890/z990 (2084 and
282 2086 series). The kernel will be slightly faster but will not work
287 select HAVE_MARCH_Z9_109_FEATURES if 64BIT
289 Select this to enable optimizations for IBM System z9 (2094 and
290 2096 series). The kernel will be slightly faster but will not work
294 bool "IBM System z10"
295 select HAVE_MARCH_Z10_FEATURES if 64BIT
297 Select this to enable optimizations for IBM System z10 (2097 and
298 2098 series). The kernel will be slightly faster but will not work
302 bool "IBM zEnterprise 114 and 196"
303 select HAVE_MARCH_Z196_FEATURES if 64BIT
305 Select this to enable optimizations for IBM zEnterprise 114 and 196
306 (2818 and 2817 series). The kernel will be slightly faster but will
307 not work on older machines.
313 prompt "Pack kernel stack"
315 This option enables the compiler option -mkernel-backchain if it
316 is available. If the option is available the compiler supports
317 the new stack layout which dramatically reduces the minimum stack
318 frame size. With an old compiler a non-leaf function needs a
319 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
320 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
321 and 24 byte on 64 bit.
323 Say Y if you are unsure.
327 prompt "Use 8kb for kernel stack instead of 16kb"
328 depends on PACK_STACK && 64BIT && !LOCKDEP
330 If you say Y here and the compiler supports the -mkernel-backchain
331 option the kernel will use a smaller kernel stack size. The reduced
332 size is 8kb instead of 16kb. This allows to run more threads on a
333 system and reduces the pressure on the memory management for higher
334 order page allocations.
336 Say N if you are unsure.
340 prompt "Detect kernel stack overflow"
342 This option enables the compiler option -mstack-guard and
343 -mstack-size if they are available. If the compiler supports them
344 it will emit additional code to each function prolog to trigger
345 an illegal operation if the kernel stack is about to overflow.
347 Say N if you are unsure.
350 int "Size of the guard area (128-1024)"
352 depends on CHECK_STACK
355 This allows you to specify the size of the guard area at the lower
356 end of the kernel stack. If the kernel stack points into the guard
357 area on function entry an illegal operation is triggered. The size
358 needs to be a power of 2. Please keep in mind that the size of an
359 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
360 The minimum size for the stack guard should be 256 for 31 bit and
363 config WARN_DYNAMIC_STACK
365 prompt "Emit compiler warnings for function with dynamic stack usage"
367 This option enables the compiler option -mwarn-dynamicstack. If the
368 compiler supports this options generates warnings for functions
369 that dynamically allocate stack space using alloca.
371 Say N if you are unsure.
373 comment "Kernel preemption"
375 source "kernel/Kconfig.preempt"
377 config ARCH_SPARSEMEM_ENABLE
379 select SPARSEMEM_VMEMMAP_ENABLE
380 select SPARSEMEM_VMEMMAP
381 select SPARSEMEM_STATIC if !64BIT
383 config ARCH_SPARSEMEM_DEFAULT
386 config ARCH_SELECT_MEMORY_MODEL
389 config ARCH_ENABLE_MEMORY_HOTPLUG
390 def_bool y if SPARSEMEM
392 config ARCH_ENABLE_MEMORY_HOTREMOVE
395 config ARCH_HIBERNATION_POSSIBLE
400 comment "I/O subsystem configuration"
404 prompt "QDIO support"
406 This driver provides the Queued Direct I/O base support for
409 To compile this driver as a module, choose M here: the
410 module will be called qdio.
416 prompt "Support for CHSC subchannels"
418 This driver allows usage of CHSC subchannels. A CHSC subchannel
419 is usually present on LPAR only.
420 The driver creates a device /dev/chsc, which may be used to
421 obtain I/O configuration information about the machine and
422 to issue asynchronous chsc commands (DANGEROUS).
423 You will usually only want to use this interface on a special
424 LPAR designated for system management.
426 To compile this driver as a module, choose M here: the
427 module will be called chsc_sch.
433 source "fs/Kconfig.binfmt"
435 config FORCE_MAX_ZONEORDER
441 prompt "Pseudo page fault support"
443 Select this option, if you want to use PFAULT pseudo page fault
444 handling under VM. If running native or in LPAR, this option
445 has no effect. If your VM does not support PFAULT, PAGEEX
446 pseudo page fault handling will be used.
447 Note that VM 4.2 supports PFAULT but has a bug in its
448 implementation that causes some problems.
449 Everybody who wants to run Linux under VM != VM4.2 should select
454 prompt "VM shared kernel support"
456 Select this option, if you want to share the text segment of the
457 Linux kernel between different VM guests. This reduces memory
458 usage with lots of guests but greatly increases kernel size.
459 Also if a kernel was IPL'ed from a shared segment the kexec system
461 You should only select this option if you know what you are
462 doing and want to exploit this feature.
466 prompt "Cooperative memory management"
468 Select this option, if you want to enable the kernel interface
469 to reduce the memory size of the system. This is accomplished
470 by allocating pages of memory and put them "on hold". This only
471 makes sense for a system running under VM where the unused pages
472 will be reused by VM for other guest systems. The interface
473 allows an external monitor to balance memory of many systems.
474 Everybody who wants to run Linux under VM should select this
479 prompt "IUCV special message interface to cooperative memory management"
480 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
482 Select this option to enable the special message interface to
483 the cooperative memory management.
487 prompt "Linux - VM Monitor Stream, base infrastructure"
490 This provides a kernel interface for creating and updating z/VM APPLDATA
491 monitor records. The monitor records are updated at certain time
492 intervals, once the timer is started.
493 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
494 i.e. enables or disables monitoring on the Linux side.
495 A custom interval value (in seconds) can be written to
496 /proc/appldata/interval.
498 Defaults are 60 seconds interval and timer off.
499 The /proc entries can also be read from, showing the current settings.
503 prompt "Monitor memory management statistics"
504 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
506 This provides memory management related data to the Linux - VM Monitor
507 Stream, like paging/swapping rate, memory utilisation, etc.
508 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
509 APPLDATA monitor record, i.e. enables or disables monitoring this record
513 The /proc entry can also be read from, showing the current settings.
515 This can also be compiled as a module, which will be called
520 prompt "Monitor OS statistics"
521 depends on APPLDATA_BASE
523 This provides OS related data to the Linux - VM Monitor Stream, like
524 CPU utilisation, etc.
525 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
526 APPLDATA monitor record, i.e. enables or disables monitoring this record
530 This can also be compiled as a module, which will be called
533 config APPLDATA_NET_SUM
535 prompt "Monitor overall network statistics"
536 depends on APPLDATA_BASE && NET
538 This provides network related data to the Linux - VM Monitor Stream,
539 currently there is only a total sum of network I/O statistics, no
541 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
542 APPLDATA monitor record, i.e. enables or disables monitoring this record
546 This can also be compiled as a module, which will be called
549 source kernel/Kconfig.hz
553 prompt "s390 hypervisor file system support"
554 select SYS_HYPERVISOR
556 This is a virtual file system intended to provide accounting
557 information in an s390 hypervisor environment.
561 prompt "kexec system call"
563 kexec is a system call that implements the ability to shutdown your
564 current kernel, and to start another kernel. It is like a reboot
565 but is independent of hardware/microcode support.
568 bool "kernel crash dumps"
569 depends on 64BIT && SMP
572 Generate crash dump after being started by kexec.
573 Crash dump kernels are loaded in the main kernel with kexec-tools
574 into a specially reserved region and then later executed after
575 a crash by kdump/kexec.
576 For more details see Documentation/kdump/kdump.txt
580 prompt "zfcpdump support"
583 Select this option if you want to build an zfcpdump enabled kernel.
584 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
588 prompt "s390 guest support for KVM (EXPERIMENTAL)"
589 depends on 64BIT && EXPERIMENTAL
590 select VIRTUALIZATION
593 select VIRTIO_CONSOLE
595 Select this option if you want to run the kernel as a guest under
596 the KVM hypervisor. This will add detection for KVM as well as a
597 virtio transport. If KVM is detected, the virtio console will be
602 prompt "Enable seccomp to safely compute untrusted bytecode"
605 This kernel feature is useful for number crunching applications
606 that may need to compute untrusted bytecode during their
607 execution. By using pipes or other transports made available to
608 the process as file descriptors supporting the read/write
609 syscalls, it's possible to isolate those applications in
610 their own address space using seccomp. Once seccomp is
611 enabled via /proc/<pid>/seccomp, it cannot be disabled
612 and the task is only allowed to execute a few safe syscalls
613 defined by each seccomp mode.
619 menu "Power Management"
621 source "kernel/power/Kconfig"
633 source "drivers/Kconfig"
637 source "arch/s390/Kconfig.debug"
639 source "security/Kconfig"
641 source "crypto/Kconfig"
645 source "arch/s390/kvm/Kconfig"