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 HAVE_KERNEL_GZIP
85 select HAVE_KERNEL_BZIP2
86 select HAVE_KERNEL_LZMA
87 select HAVE_KERNEL_LZO
89 select HAVE_GET_USER_PAGES_FAST
90 select HAVE_ARCH_MUTEX_CPU_RELAX
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
120 config SCHED_OMIT_FRAME_POINTER
123 source "init/Kconfig"
125 source "kernel/Kconfig.freezer"
129 comment "Processor type and features"
131 source "kernel/time/Kconfig"
135 prompt "64 bit kernel"
137 Select this option if you have an IBM z/Architecture machine
138 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.
191 prompt "Multi-core scheduler support"
194 Multi-core scheduler support improves the CPU scheduler's decision
195 making when dealing with multi-core CPU chips at a cost of slightly
196 increased overhead in some places.
200 prompt "Book scheduler support"
201 depends on SMP && SCHED_MC
203 Book scheduler support improves the CPU scheduler's decision making
204 when dealing with machines that have several books.
208 prompt "IEEE FPU emulation"
211 This option is required for IEEE compliant floating point arithmetic
212 on older ESA/390 machines. Say Y unless you know your machine doesn't
217 prompt "Kernel support for 31 bit emulation"
219 select COMPAT_BINFMT_ELF
221 Select this option if you want to enable your system kernel to
222 handle system-calls from ELF binaries for 31 bit ESA. This option
223 (and some other stuff like libraries and such) is needed for
224 executing 31 bit applications. It is safe to say "Y".
226 config SYSVIPC_COMPAT
227 def_bool y if COMPAT && SYSVIPC
232 config S390_EXEC_PROTECT
234 prompt "Data execute protection"
236 This option allows to enable a buffer overflow protection for user
237 space programs and it also selects the addressing mode option above.
238 The kernel parameter noexec=on will enable this feature and also
239 switch the addressing modes, default is disabled. Enabling this (via
240 kernel parameter) on machines earlier than IBM System z9 this will
241 reduce system performance.
243 comment "Code generation options"
246 prompt "Processor type"
250 bool "System/390 model G5 and G6"
253 Select this to build a 31 bit kernel that works
254 on all ESA/390 and z/Architecture machines.
257 bool "IBM zSeries model z800 and z900"
259 Select this to enable optimizations for model z800/z900 (2064 and
260 2066 series). This will enable some optimizations that are not
261 available on older ESA/390 (31 Bit) only CPUs.
264 bool "IBM zSeries model z890 and z990"
266 Select this to enable optimizations for model z890/z990 (2084 and
267 2086 series). The kernel will be slightly faster but will not work
273 Select this to enable optimizations for IBM System z9 (2094 and
274 2096 series). The kernel will be slightly faster but will not work
278 bool "IBM System z10"
280 Select this to enable optimizations for IBM System z10 (2097 and
281 2098 series). The kernel will be slightly faster but will not work
285 bool "IBM zEnterprise 196"
287 Select this to enable optimizations for IBM zEnterprise 196
288 (2817 series). The kernel will be slightly faster but will not work
295 prompt "Pack kernel stack"
297 This option enables the compiler option -mkernel-backchain if it
298 is available. If the option is available the compiler supports
299 the new stack layout which dramatically reduces the minimum stack
300 frame size. With an old compiler a non-leaf function needs a
301 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
302 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
303 and 24 byte on 64 bit.
305 Say Y if you are unsure.
309 prompt "Use 8kb for kernel stack instead of 16kb"
310 depends on PACK_STACK && 64BIT && !LOCKDEP
312 If you say Y here and the compiler supports the -mkernel-backchain
313 option the kernel will use a smaller kernel stack size. The reduced
314 size is 8kb instead of 16kb. This allows to run more threads on a
315 system and reduces the pressure on the memory management for higher
316 order page allocations.
318 Say N if you are unsure.
322 prompt "Detect kernel stack overflow"
324 This option enables the compiler option -mstack-guard and
325 -mstack-size if they are available. If the compiler supports them
326 it will emit additional code to each function prolog to trigger
327 an illegal operation if the kernel stack is about to overflow.
329 Say N if you are unsure.
332 int "Size of the guard area (128-1024)"
334 depends on CHECK_STACK
337 This allows you to specify the size of the guard area at the lower
338 end of the kernel stack. If the kernel stack points into the guard
339 area on function entry an illegal operation is triggered. The size
340 needs to be a power of 2. Please keep in mind that the size of an
341 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
342 The minimum size for the stack guard should be 256 for 31 bit and
345 config WARN_DYNAMIC_STACK
347 prompt "Emit compiler warnings for function with dynamic stack usage"
349 This option enables the compiler option -mwarn-dynamicstack. If the
350 compiler supports this options generates warnings for functions
351 that dynamically allocate stack space using alloca.
353 Say N if you are unsure.
355 config ARCH_POPULATES_NODE_MAP
358 comment "Kernel preemption"
360 source "kernel/Kconfig.preempt"
362 config ARCH_SPARSEMEM_ENABLE
364 select SPARSEMEM_VMEMMAP_ENABLE
365 select SPARSEMEM_VMEMMAP
366 select SPARSEMEM_STATIC if !64BIT
368 config ARCH_SPARSEMEM_DEFAULT
371 config ARCH_SELECT_MEMORY_MODEL
374 config ARCH_ENABLE_MEMORY_HOTPLUG
375 def_bool y if SPARSEMEM
377 config ARCH_ENABLE_MEMORY_HOTREMOVE
380 config ARCH_HIBERNATION_POSSIBLE
385 comment "I/O subsystem configuration"
389 prompt "QDIO support"
391 This driver provides the Queued Direct I/O base support for
394 To compile this driver as a module, choose M here: the
395 module will be called qdio.
401 prompt "Support for CHSC subchannels"
403 This driver allows usage of CHSC subchannels. A CHSC subchannel
404 is usually present on LPAR only.
405 The driver creates a device /dev/chsc, which may be used to
406 obtain I/O configuration information about the machine and
407 to issue asynchronous chsc commands (DANGEROUS).
408 You will usually only want to use this interface on a special
409 LPAR designated for system management.
411 To compile this driver as a module, choose M here: the
412 module will be called chsc_sch.
420 prompt "Builtin IPL record support"
422 If you want to use the produced kernel to IPL directly from a
423 device, you have to merge a bootsector specific to the device
424 into the first bytes of the kernel. You will have to select the
428 prompt "IPL method generated into head.S"
432 Select "tape" if you want to IPL the image from a Tape.
434 Select "vm_reader" if you are running under VM/ESA and want
435 to IPL the image from the emulated card reader.
445 source "fs/Kconfig.binfmt"
447 config FORCE_MAX_ZONEORDER
453 prompt "Pseudo page fault support"
455 Select this option, if you want to use PFAULT pseudo page fault
456 handling under VM. If running native or in LPAR, this option
457 has no effect. If your VM does not support PFAULT, PAGEEX
458 pseudo page fault handling will be used.
459 Note that VM 4.2 supports PFAULT but has a bug in its
460 implementation that causes some problems.
461 Everybody who wants to run Linux under VM != VM4.2 should select
466 prompt "VM shared kernel support"
468 Select this option, if you want to share the text segment of the
469 Linux kernel between different VM guests. This reduces memory
470 usage with lots of guests but greatly increases kernel size.
471 Also if a kernel was IPL'ed from a shared segment the kexec system
473 You should only select this option if you know what you are
474 doing and want to exploit this feature.
478 prompt "Cooperative memory management"
480 Select this option, if you want to enable the kernel interface
481 to reduce the memory size of the system. This is accomplished
482 by allocating pages of memory and put them "on hold". This only
483 makes sense for a system running under VM where the unused pages
484 will be reused by VM for other guest systems. The interface
485 allows an external monitor to balance memory of many systems.
486 Everybody who wants to run Linux under VM should select this
491 prompt "IUCV special message interface to cooperative memory management"
492 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
494 Select this option to enable the special message interface to
495 the cooperative memory management.
499 prompt "Linux - VM Monitor Stream, base infrastructure"
502 This provides a kernel interface for creating and updating z/VM APPLDATA
503 monitor records. The monitor records are updated at certain time
504 intervals, once the timer is started.
505 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
506 i.e. enables or disables monitoring on the Linux side.
507 A custom interval value (in seconds) can be written to
508 /proc/appldata/interval.
510 Defaults are 60 seconds interval and timer off.
511 The /proc entries can also be read from, showing the current settings.
515 prompt "Monitor memory management statistics"
516 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
518 This provides memory management related data to the Linux - VM Monitor
519 Stream, like paging/swapping rate, memory utilisation, etc.
520 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
521 APPLDATA monitor record, i.e. enables or disables monitoring this record
525 The /proc entry can also be read from, showing the current settings.
527 This can also be compiled as a module, which will be called
532 prompt "Monitor OS statistics"
533 depends on APPLDATA_BASE
535 This provides OS related data to the Linux - VM Monitor Stream, like
536 CPU utilisation, etc.
537 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
538 APPLDATA monitor record, i.e. enables or disables monitoring this record
542 This can also be compiled as a module, which will be called
545 config APPLDATA_NET_SUM
547 prompt "Monitor overall network statistics"
548 depends on APPLDATA_BASE && NET
550 This provides network related data to the Linux - VM Monitor Stream,
551 currently there is only a total sum of network I/O statistics, no
553 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
554 APPLDATA monitor record, i.e. enables or disables monitoring this record
558 This can also be compiled as a module, which will be called
561 source kernel/Kconfig.hz
565 prompt "s390 hypervisor file system support"
566 select SYS_HYPERVISOR
568 This is a virtual file system intended to provide accounting
569 information in an s390 hypervisor environment.
573 prompt "kexec system call"
575 kexec is a system call that implements the ability to shutdown your
576 current kernel, and to start another kernel. It is like a reboot
577 but is independent of hardware/microcode support.
581 prompt "zfcpdump support"
584 Select this option if you want to build an zfcpdump enabled kernel.
585 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
589 prompt "s390 guest support for KVM (EXPERIMENTAL)"
590 depends on 64BIT && EXPERIMENTAL
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"