10 config LOCKDEP_SUPPORT
13 config STACKTRACE_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
37 config ARCH_DMA_ADDR_T_64BIT
40 config GENERIC_LOCKBREAK
41 def_bool y if SMP && PREEMPT
46 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
62 config ARCH_SUPPORTS_UPROBES
70 select ARCH_HAS_DEVMEM_IS_ALLOWED
71 select ARCH_HAS_ELF_RANDOMIZE
72 select ARCH_HAS_GCOV_PROFILE_ALL
73 select ARCH_HAS_GIGANTIC_PAGE
75 select ARCH_HAS_SG_CHAIN
76 select ARCH_HAS_UBSAN_SANITIZE_ALL
77 select ARCH_HAVE_NMI_SAFE_CMPXCHG
78 select ARCH_INLINE_READ_LOCK
79 select ARCH_INLINE_READ_LOCK_BH
80 select ARCH_INLINE_READ_LOCK_IRQ
81 select ARCH_INLINE_READ_LOCK_IRQSAVE
82 select ARCH_INLINE_READ_TRYLOCK
83 select ARCH_INLINE_READ_UNLOCK
84 select ARCH_INLINE_READ_UNLOCK_BH
85 select ARCH_INLINE_READ_UNLOCK_IRQ
86 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
87 select ARCH_INLINE_SPIN_LOCK
88 select ARCH_INLINE_SPIN_LOCK_BH
89 select ARCH_INLINE_SPIN_LOCK_IRQ
90 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
91 select ARCH_INLINE_SPIN_TRYLOCK
92 select ARCH_INLINE_SPIN_TRYLOCK_BH
93 select ARCH_INLINE_SPIN_UNLOCK
94 select ARCH_INLINE_SPIN_UNLOCK_BH
95 select ARCH_INLINE_SPIN_UNLOCK_IRQ
96 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
97 select ARCH_INLINE_WRITE_LOCK
98 select ARCH_INLINE_WRITE_LOCK_BH
99 select ARCH_INLINE_WRITE_LOCK_IRQ
100 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
101 select ARCH_INLINE_WRITE_TRYLOCK
102 select ARCH_INLINE_WRITE_UNLOCK
103 select ARCH_INLINE_WRITE_UNLOCK_BH
104 select ARCH_INLINE_WRITE_UNLOCK_IRQ
105 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
106 select ARCH_SAVE_PAGE_KEYS if HIBERNATION
107 select ARCH_SUPPORTS_ATOMIC_RMW
108 select ARCH_SUPPORTS_NUMA_BALANCING
109 select ARCH_USE_BUILTIN_BSWAP
110 select ARCH_USE_CMPXCHG_LOCKREF
111 select ARCH_WANTS_DYNAMIC_TASK_STRUCT
112 select ARCH_WANTS_PROT_NUMA_PROT_NONE
113 select ARCH_WANTS_UBSAN_NO_NULL
114 select ARCH_WANT_IPC_PARSE_VERSION
115 select BUILDTIME_EXTABLE_SORT
116 select CLONE_BACKWARDS2
117 select DYNAMIC_FTRACE if FUNCTION_TRACER
118 select GENERIC_CLOCKEVENTS
119 select GENERIC_CPU_AUTOPROBE
120 select GENERIC_CPU_DEVICES if !SMP
121 select GENERIC_FIND_FIRST_BIT
122 select GENERIC_SMP_IDLE_THREAD
123 select GENERIC_TIME_VSYSCALL
124 select HAVE_ALIGNED_STRUCT_PAGE if SLUB
125 select HAVE_ARCH_AUDITSYSCALL
126 select HAVE_ARCH_EARLY_PFN_TO_NID
127 select HAVE_ARCH_HARDENED_USERCOPY
128 select HAVE_ARCH_JUMP_LABEL
129 select CPU_NO_EFFICIENT_FFS if !HAVE_MARCH_Z9_109_FEATURES
130 select HAVE_ARCH_SECCOMP_FILTER
131 select HAVE_ARCH_SOFT_DIRTY
132 select HAVE_ARCH_TRACEHOOK
133 select HAVE_ARCH_TRANSPARENT_HUGEPAGE
134 select HAVE_EBPF_JIT if PACK_STACK && HAVE_MARCH_Z196_FEATURES
135 select HAVE_CMPXCHG_DOUBLE
136 select HAVE_CMPXCHG_LOCAL
137 select HAVE_DEBUG_KMEMLEAK
138 select HAVE_DMA_API_DEBUG
139 select HAVE_DMA_CONTIGUOUS
140 select HAVE_DYNAMIC_FTRACE
141 select HAVE_DYNAMIC_FTRACE_WITH_REGS
142 select HAVE_EFFICIENT_UNALIGNED_ACCESS
143 select HAVE_EXIT_THREAD
144 select HAVE_FTRACE_MCOUNT_RECORD
145 select HAVE_FUNCTION_GRAPH_TRACER
146 select HAVE_FUNCTION_TRACER
147 select HAVE_FUTEX_CMPXCHG if FUTEX
148 select HAVE_KERNEL_BZIP2
149 select HAVE_KERNEL_GZIP
150 select HAVE_KERNEL_LZ4
151 select HAVE_KERNEL_LZMA
152 select HAVE_KERNEL_LZO
153 select HAVE_KERNEL_XZ
155 select HAVE_KRETPROBES
157 select HAVE_LIVEPATCH
159 select HAVE_MEMBLOCK_NODE_MAP
160 select HAVE_MEMBLOCK_PHYS_MAP
161 select HAVE_MOD_ARCH_SPECIFIC
163 select HAVE_PERF_EVENTS
164 select HAVE_REGS_AND_STACK_ACCESS_API
165 select HAVE_SYSCALL_TRACEPOINTS
166 select HAVE_VIRT_CPU_ACCOUNTING
167 select MODULES_USE_ELF_RELA
170 select OLD_SIGSUSPEND3
172 select SYSCTL_EXCEPTION_TRACE
173 select THREAD_INFO_IN_TASK
175 select VIRT_CPU_ACCOUNTING
176 select ARCH_HAS_SCALED_CPUTIME
181 config SCHED_OMIT_FRAME_POINTER
184 config PGTABLE_LEVELS
188 source "init/Kconfig"
190 source "kernel/Kconfig.freezer"
192 source "kernel/livepatch/Kconfig"
194 menu "Processor type and features"
196 config HAVE_MARCH_Z900_FEATURES
199 config HAVE_MARCH_Z990_FEATURES
201 select HAVE_MARCH_Z900_FEATURES
203 config HAVE_MARCH_Z9_109_FEATURES
205 select HAVE_MARCH_Z990_FEATURES
207 config HAVE_MARCH_Z10_FEATURES
209 select HAVE_MARCH_Z9_109_FEATURES
211 config HAVE_MARCH_Z196_FEATURES
213 select HAVE_MARCH_Z10_FEATURES
215 config HAVE_MARCH_ZEC12_FEATURES
217 select HAVE_MARCH_Z196_FEATURES
219 config HAVE_MARCH_Z13_FEATURES
221 select HAVE_MARCH_ZEC12_FEATURES
224 prompt "Processor type"
228 bool "IBM zSeries model z800 and z900"
229 select HAVE_MARCH_Z900_FEATURES
231 Select this to enable optimizations for model z800/z900 (2064 and
232 2066 series). This will enable some optimizations that are not
233 available on older ESA/390 (31 Bit) only CPUs.
236 bool "IBM zSeries model z890 and z990"
237 select HAVE_MARCH_Z990_FEATURES
239 Select this to enable optimizations for model z890/z990 (2084 and
240 2086 series). The kernel will be slightly faster but will not work
245 select HAVE_MARCH_Z9_109_FEATURES
247 Select this to enable optimizations for IBM System z9 (2094 and
248 2096 series). The kernel will be slightly faster but will not work
252 bool "IBM System z10"
253 select HAVE_MARCH_Z10_FEATURES
255 Select this to enable optimizations for IBM System z10 (2097 and
256 2098 series). The kernel will be slightly faster but will not work
260 bool "IBM zEnterprise 114 and 196"
261 select HAVE_MARCH_Z196_FEATURES
263 Select this to enable optimizations for IBM zEnterprise 114 and 196
264 (2818 and 2817 series). The kernel will be slightly faster but will
265 not work on older machines.
268 bool "IBM zBC12 and zEC12"
269 select HAVE_MARCH_ZEC12_FEATURES
271 Select this to enable optimizations for IBM zBC12 and zEC12 (2828 and
272 2827 series). The kernel will be slightly faster but will not work on
276 bool "IBM z13s and z13"
277 select HAVE_MARCH_Z13_FEATURES
279 Select this to enable optimizations for IBM z13s and z13 (2965 and
280 2964 series). The kernel will be slightly faster but will not work on
285 config MARCH_Z900_TUNE
286 def_bool TUNE_Z900 || MARCH_Z900 && TUNE_DEFAULT
288 config MARCH_Z990_TUNE
289 def_bool TUNE_Z990 || MARCH_Z990 && TUNE_DEFAULT
291 config MARCH_Z9_109_TUNE
292 def_bool TUNE_Z9_109 || MARCH_Z9_109 && TUNE_DEFAULT
294 config MARCH_Z10_TUNE
295 def_bool TUNE_Z10 || MARCH_Z10 && TUNE_DEFAULT
297 config MARCH_Z196_TUNE
298 def_bool TUNE_Z196 || MARCH_Z196 && TUNE_DEFAULT
300 config MARCH_ZEC12_TUNE
301 def_bool TUNE_ZEC12 || MARCH_ZEC12 && TUNE_DEFAULT
303 config MARCH_Z13_TUNE
304 def_bool TUNE_Z13 || MARCH_Z13 && TUNE_DEFAULT
307 prompt "Tune code generation"
310 Cause the compiler to tune (-mtune) the generated code for a machine.
311 This will make the code run faster on the selected machine but
312 somewhat slower on other machines.
313 This option only changes how the compiler emits instructions, not the
314 selection of instructions itself, so the resulting kernel will run on
320 Tune the generated code for the target processor for which the kernel
324 bool "IBM zSeries model z800 and z900"
327 bool "IBM zSeries model z890 and z990"
333 bool "IBM System z10"
336 bool "IBM zEnterprise 114 and 196"
339 bool "IBM zBC12 and zEC12"
351 prompt "Kernel support for 31 bit emulation"
352 select COMPAT_BINFMT_ELF if BINFMT_ELF
353 select ARCH_WANT_OLD_COMPAT_IPC
354 select COMPAT_OLD_SIGACTION
357 Select this option if you want to enable your system kernel to
358 handle system-calls from ELF binaries for 31 bit ESA. This option
359 (and some other stuff like libraries and such) is needed for
360 executing 31 bit applications. It is safe to say "Y".
362 config SYSVIPC_COMPAT
363 def_bool y if COMPAT && SYSVIPC
366 def_bool y if COMPAT && KEYS
370 prompt "Symmetric multi-processing support"
372 This enables support for systems with more than one CPU. If you have
373 a system with only one CPU, like most personal computers, say N. If
374 you have a system with more than one CPU, say Y.
376 If you say N here, the kernel will run on uni- and multiprocessor
377 machines, but will use only one CPU of a multiprocessor machine. If
378 you say Y here, the kernel will run on many, but not all,
379 uniprocessor machines. On a uniprocessor machine, the kernel
380 will run faster if you say N here.
382 See also the SMP-HOWTO available at
383 <http://www.tldp.org/docs.html#howto>.
385 Even if you don't know what to do here, say Y.
388 int "Maximum number of CPUs (2-512)"
393 This allows you to specify the maximum number of CPUs which this
394 kernel will support. The maximum supported value is 512 and the
395 minimum value which makes sense is 2.
397 This is purely to save memory - each supported CPU adds
398 approximately sixteen kilobytes to the kernel image.
402 prompt "Support for hot-pluggable CPUs"
405 Say Y here to be able to turn CPUs off and on. CPUs
406 can be controlled through /sys/devices/system/cpu/cpu#.
407 Say N if you want to disable CPU hotplug.
409 # Some NUMA nodes have memory ranges that span
410 # other nodes. Even though a pfn is valid and
411 # between a node's start and end pfns, it may not
412 # reside on that node. See memmap_init_zone()
413 # for details. <- They meant memory holes!
414 config NODES_SPAN_OTHER_NODES
419 depends on SMP && SCHED_TOPOLOGY
424 This option adds NUMA support to the kernel.
426 An operation mode can be selected by appending
427 numa=<method> to the kernel command line.
429 The default behaviour is identical to appending numa=plain to
430 the command line. This will create just one node with all
431 available memory and all CPUs in it.
434 int "Maximum NUMA nodes (as a power of 2)"
439 Specify the maximum number of NUMA nodes available on the target
440 system. Increases memory reserved to accommodate various tables.
442 menu "Select NUMA modes"
446 bool "NUMA emulation"
449 Numa emulation mode will split the available system memory into
450 equal chunks which then are distributed over the configured number
451 of nodes in a round-robin manner.
453 The number of fake nodes is limited by the number of available memory
454 chunks (i.e. memory size / fake size) and the number of supported
457 The CPUs are assigned to the nodes in a way that partially respects
458 the original machine topology (if supported by the machine).
459 Fair distribution of the CPUs is not guaranteed.
462 hex "NUMA emulation memory chunk size"
464 range 0x400000 0x100000000
467 Select the default size by which the memory is chopped and then
468 assigned to emulated NUMA nodes.
470 This can be overridden by specifying
474 on the kernel command line where also suffixes K, M, G, and T are
491 config SCHED_TOPOLOGY
493 prompt "Topology scheduler support"
500 Topology scheduler support improves the CPU scheduler's decision
501 making when dealing with machines that have multi-threading,
502 multiple cores or multiple books.
504 source kernel/Kconfig.preempt
506 source kernel/Kconfig.hz
512 config ARCH_SPARSEMEM_ENABLE
514 select SPARSEMEM_VMEMMAP_ENABLE
515 select SPARSEMEM_VMEMMAP
517 config ARCH_SPARSEMEM_DEFAULT
520 config ARCH_SELECT_MEMORY_MODEL
523 config ARCH_ENABLE_MEMORY_HOTPLUG
524 def_bool y if SPARSEMEM
526 config ARCH_ENABLE_MEMORY_HOTREMOVE
529 config ARCH_ENABLE_SPLIT_PMD_PTLOCK
532 config FORCE_MAX_ZONEORDER
540 prompt "Pack kernel stack"
542 This option enables the compiler option -mkernel-backchain if it
543 is available. If the option is available the compiler supports
544 the new stack layout which dramatically reduces the minimum stack
545 frame size. With an old compiler a non-leaf function needs a
546 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
547 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
548 and 24 byte on 64 bit.
550 Say Y if you are unsure.
554 prompt "Detect kernel stack overflow"
556 This option enables the compiler option -mstack-guard and
557 -mstack-size if they are available. If the compiler supports them
558 it will emit additional code to each function prolog to trigger
559 an illegal operation if the kernel stack is about to overflow.
561 Say N if you are unsure.
564 int "Size of the guard area (128-1024)"
566 depends on CHECK_STACK
569 This allows you to specify the size of the guard area at the lower
570 end of the kernel stack. If the kernel stack points into the guard
571 area on function entry an illegal operation is triggered. The size
572 needs to be a power of 2. Please keep in mind that the size of an
573 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
574 The minimum size for the stack guard should be 256 for 31 bit and
577 config WARN_DYNAMIC_STACK
579 prompt "Emit compiler warnings for function with dynamic stack usage"
581 This option enables the compiler option -mwarn-dynamicstack. If the
582 compiler supports this options generates warnings for functions
583 that dynamically allocate stack space using alloca.
585 Say N if you are unsure.
593 prompt "QDIO support"
595 This driver provides the Queued Direct I/O base support for
598 To compile this driver as a module, choose M here: the
599 module will be called qdio.
612 config PCI_NR_FUNCTIONS
613 int "Maximum number of PCI functions (1-4096)"
617 This allows you to specify the maximum number of PCI functions which
618 this kernel will support.
620 source "drivers/pci/Kconfig"
633 config NEED_SG_DMA_LENGTH
636 config NEED_DMA_MAP_STATE
641 prompt "Support for CHSC subchannels"
643 This driver allows usage of CHSC subchannels. A CHSC subchannel
644 is usually present on LPAR only.
645 The driver creates a device /dev/chsc, which may be used to
646 obtain I/O configuration information about the machine and
647 to issue asynchronous chsc commands (DANGEROUS).
648 You will usually only want to use this interface on a special
649 LPAR designated for system management.
651 To compile this driver as a module, choose M here: the
652 module will be called chsc_sch.
658 prompt "SCM bus driver"
660 Bus driver for Storage Class Memory.
664 prompt "Support for EADM subchannels"
667 This driver allows usage of EADM subchannels. EADM subchannels act
668 as a communication vehicle for SCM increments.
670 To compile this driver as a module, choose M here: the
671 module will be called eadm_sch.
678 bool "kernel crash dumps"
682 Generate crash dump after being started by kexec.
683 Crash dump kernels are loaded in the main kernel with kexec-tools
684 into a specially reserved region and then later executed after
685 a crash by kdump/kexec.
686 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
687 This option also enables s390 zfcpdump.
688 See also <file:Documentation/s390/zfcpdump.txt>
692 menu "Executable file formats / Emulations"
694 source "fs/Kconfig.binfmt"
698 prompt "Enable seccomp to safely compute untrusted bytecode"
701 This kernel feature is useful for number crunching applications
702 that may need to compute untrusted bytecode during their
703 execution. By using pipes or other transports made available to
704 the process as file descriptors supporting the read/write
705 syscalls, it's possible to isolate those applications in
706 their own address space using seccomp. Once seccomp is
707 enabled via /proc/<pid>/seccomp, it cannot be disabled
708 and the task is only allowed to execute a few safe syscalls
709 defined by each seccomp mode.
715 menu "Power Management"
717 config ARCH_HIBERNATION_POSSIBLE
720 source "kernel/power/Kconfig"
732 source "drivers/Kconfig"
736 source "arch/s390/Kconfig.debug"
738 source "security/Kconfig"
740 source "crypto/Kconfig"
744 menu "Virtualization"
748 prompt "Pseudo page fault support"
750 Select this option, if you want to use PFAULT pseudo page fault
751 handling under VM. If running native or in LPAR, this option
752 has no effect. If your VM does not support PFAULT, PAGEEX
753 pseudo page fault handling will be used.
754 Note that VM 4.2 supports PFAULT but has a bug in its
755 implementation that causes some problems.
756 Everybody who wants to run Linux under VM != VM4.2 should select
760 bool "VM shared kernel support"
761 depends on !JUMP_LABEL
763 Select this option, if you want to share the text segment of the
764 Linux kernel between different VM guests. This reduces memory
765 usage with lots of guests but greatly increases kernel size.
766 Also if a kernel was IPL'ed from a shared segment the kexec system
768 You should only select this option if you know what you are
769 doing and want to exploit this feature.
773 prompt "Cooperative memory management"
775 Select this option, if you want to enable the kernel interface
776 to reduce the memory size of the system. This is accomplished
777 by allocating pages of memory and put them "on hold". This only
778 makes sense for a system running under VM where the unused pages
779 will be reused by VM for other guest systems. The interface
780 allows an external monitor to balance memory of many systems.
781 Everybody who wants to run Linux under VM should select this
786 prompt "IUCV special message interface to cooperative memory management"
787 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
789 Select this option to enable the special message interface to
790 the cooperative memory management.
794 prompt "Linux - VM Monitor Stream, base infrastructure"
797 This provides a kernel interface for creating and updating z/VM APPLDATA
798 monitor records. The monitor records are updated at certain time
799 intervals, once the timer is started.
800 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
801 i.e. enables or disables monitoring on the Linux side.
802 A custom interval value (in seconds) can be written to
803 /proc/appldata/interval.
805 Defaults are 60 seconds interval and timer off.
806 The /proc entries can also be read from, showing the current settings.
810 prompt "Monitor memory management statistics"
811 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
813 This provides memory management related data to the Linux - VM Monitor
814 Stream, like paging/swapping rate, memory utilisation, etc.
815 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
816 APPLDATA monitor record, i.e. enables or disables monitoring this record
820 The /proc entry can also be read from, showing the current settings.
822 This can also be compiled as a module, which will be called
827 prompt "Monitor OS statistics"
828 depends on APPLDATA_BASE
830 This provides OS related data to the Linux - VM Monitor Stream, like
831 CPU utilisation, etc.
832 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
833 APPLDATA monitor record, i.e. enables or disables monitoring this record
837 This can also be compiled as a module, which will be called
840 config APPLDATA_NET_SUM
842 prompt "Monitor overall network statistics"
843 depends on APPLDATA_BASE && NET
845 This provides network related data to the Linux - VM Monitor Stream,
846 currently there is only a total sum of network I/O statistics, no
848 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
849 APPLDATA monitor record, i.e. enables or disables monitoring this record
853 This can also be compiled as a module, which will be called
858 prompt "s390 hypervisor file system support"
859 select SYS_HYPERVISOR
861 This is a virtual file system intended to provide accounting
862 information in an s390 hypervisor environment.
864 source "arch/s390/kvm/Kconfig"
868 prompt "s390 support for virtio devices"
870 select VIRTUALIZATION
872 select VIRTIO_CONSOLE
874 Enabling this option adds support for virtio based paravirtual device
877 Select this option if you want to run the kernel as a guest under
880 config S390_GUEST_OLD_TRANSPORT
882 prompt "Guest support for old s390 virtio transport (DEPRECATED)"
883 depends on S390_GUEST
885 Enable this option to add support for the old s390-virtio
886 transport (i.e. virtio devices NOT based on virtio-ccw). This
887 type of virtio devices is only available on the experimental
888 kuli userspace or with old (< 2.6) qemu. If you are running
889 with a modern version of qemu (which supports virtio-ccw since
890 1.4 and uses it by default since version 2.4), you probably won't