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 HAVE_ARCH_JUMP_LABEL if !MARCH_G5
92 select HAVE_RCU_TABLE_FREE if SMP
93 select ARCH_INLINE_SPIN_TRYLOCK
94 select ARCH_INLINE_SPIN_TRYLOCK_BH
95 select ARCH_INLINE_SPIN_LOCK
96 select ARCH_INLINE_SPIN_LOCK_BH
97 select ARCH_INLINE_SPIN_LOCK_IRQ
98 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
99 select ARCH_INLINE_SPIN_UNLOCK
100 select ARCH_INLINE_SPIN_UNLOCK_BH
101 select ARCH_INLINE_SPIN_UNLOCK_IRQ
102 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
103 select ARCH_INLINE_READ_TRYLOCK
104 select ARCH_INLINE_READ_LOCK
105 select ARCH_INLINE_READ_LOCK_BH
106 select ARCH_INLINE_READ_LOCK_IRQ
107 select ARCH_INLINE_READ_LOCK_IRQSAVE
108 select ARCH_INLINE_READ_UNLOCK
109 select ARCH_INLINE_READ_UNLOCK_BH
110 select ARCH_INLINE_READ_UNLOCK_IRQ
111 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
112 select ARCH_INLINE_WRITE_TRYLOCK
113 select ARCH_INLINE_WRITE_LOCK
114 select ARCH_INLINE_WRITE_LOCK_BH
115 select ARCH_INLINE_WRITE_LOCK_IRQ
116 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
117 select ARCH_INLINE_WRITE_UNLOCK
118 select ARCH_INLINE_WRITE_UNLOCK_BH
119 select ARCH_INLINE_WRITE_UNLOCK_IRQ
120 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
122 config SCHED_OMIT_FRAME_POINTER
125 source "init/Kconfig"
127 source "kernel/Kconfig.freezer"
131 comment "Processor type and features"
133 source "kernel/time/Kconfig"
137 prompt "64 bit kernel"
139 Select this option if you have an IBM z/Architecture machine
140 and want to use the 64 bit addressing mode.
150 prompt "Symmetric multi-processing support"
152 This enables support for systems with more than one CPU. If you have
153 a system with only one CPU, like most personal computers, say N. If
154 you have a system with more than one CPU, say Y.
156 If you say N here, the kernel will run on single and multiprocessor
157 machines, but will use only one CPU of a multiprocessor machine. If
158 you say Y here, the kernel will run on many, but not all,
159 singleprocessor machines. On a singleprocessor machine, the kernel
160 will run faster if you say N here.
162 See also the SMP-HOWTO available at
163 <http://www.tldp.org/docs.html#howto>.
165 Even if you don't know what to do here, say Y.
168 int "Maximum number of CPUs (2-64)"
171 default "32" if !64BIT
172 default "64" if 64BIT
174 This allows you to specify the maximum number of CPUs which this
175 kernel will support. The maximum supported value is 64 and the
176 minimum value which makes sense is 2.
178 This is purely to save memory - each supported CPU adds
179 approximately sixteen kilobytes to the kernel image.
183 prompt "Support for hot-pluggable CPUs"
187 Say Y here to be able to turn CPUs off and on. CPUs
188 can be controlled through /sys/devices/system/cpu/cpu#.
189 Say N if you want to disable CPU hotplug.
193 prompt "Multi-core scheduler support"
196 Multi-core scheduler support improves the CPU scheduler's decision
197 making when dealing with multi-core CPU chips at a cost of slightly
198 increased overhead in some places.
202 prompt "Book scheduler support"
203 depends on SMP && SCHED_MC
205 Book scheduler support improves the CPU scheduler's decision making
206 when dealing with machines that have several books.
210 prompt "IEEE FPU emulation"
213 This option is required for IEEE compliant floating point arithmetic
214 on older ESA/390 machines. Say Y unless you know your machine doesn't
219 prompt "Kernel support for 31 bit emulation"
221 select COMPAT_BINFMT_ELF
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
234 comment "Code generation options"
237 prompt "Processor type"
241 bool "System/390 model G5 and G6"
244 Select this to build a 31 bit kernel that works
245 on all ESA/390 and z/Architecture machines.
248 bool "IBM zSeries model z800 and z900"
250 Select this to enable optimizations for model z800/z900 (2064 and
251 2066 series). This will enable some optimizations that are not
252 available on older ESA/390 (31 Bit) only CPUs.
255 bool "IBM zSeries model z890 and z990"
257 Select this to enable optimizations for model z890/z990 (2084 and
258 2086 series). The kernel will be slightly faster but will not work
264 Select this to enable optimizations for IBM System z9 (2094 and
265 2096 series). The kernel will be slightly faster but will not work
269 bool "IBM System z10"
271 Select this to enable optimizations for IBM System z10 (2097 and
272 2098 series). The kernel will be slightly faster but will not work
276 bool "IBM zEnterprise 196"
278 Select this to enable optimizations for IBM zEnterprise 196
279 (2817 series). The kernel will be slightly faster but will not work
286 prompt "Pack kernel stack"
288 This option enables the compiler option -mkernel-backchain if it
289 is available. If the option is available the compiler supports
290 the new stack layout which dramatically reduces the minimum stack
291 frame size. With an old compiler a non-leaf function needs a
292 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
293 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
294 and 24 byte on 64 bit.
296 Say Y if you are unsure.
300 prompt "Use 8kb for kernel stack instead of 16kb"
301 depends on PACK_STACK && 64BIT && !LOCKDEP
303 If you say Y here and the compiler supports the -mkernel-backchain
304 option the kernel will use a smaller kernel stack size. The reduced
305 size is 8kb instead of 16kb. This allows to run more threads on a
306 system and reduces the pressure on the memory management for higher
307 order page allocations.
309 Say N if you are unsure.
313 prompt "Detect kernel stack overflow"
315 This option enables the compiler option -mstack-guard and
316 -mstack-size if they are available. If the compiler supports them
317 it will emit additional code to each function prolog to trigger
318 an illegal operation if the kernel stack is about to overflow.
320 Say N if you are unsure.
323 int "Size of the guard area (128-1024)"
325 depends on CHECK_STACK
328 This allows you to specify the size of the guard area at the lower
329 end of the kernel stack. If the kernel stack points into the guard
330 area on function entry an illegal operation is triggered. The size
331 needs to be a power of 2. Please keep in mind that the size of an
332 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
333 The minimum size for the stack guard should be 256 for 31 bit and
336 config WARN_DYNAMIC_STACK
338 prompt "Emit compiler warnings for function with dynamic stack usage"
340 This option enables the compiler option -mwarn-dynamicstack. If the
341 compiler supports this options generates warnings for functions
342 that dynamically allocate stack space using alloca.
344 Say N if you are unsure.
346 config ARCH_POPULATES_NODE_MAP
349 comment "Kernel preemption"
351 source "kernel/Kconfig.preempt"
353 config ARCH_SPARSEMEM_ENABLE
355 select SPARSEMEM_VMEMMAP_ENABLE
356 select SPARSEMEM_VMEMMAP
357 select SPARSEMEM_STATIC if !64BIT
359 config ARCH_SPARSEMEM_DEFAULT
362 config ARCH_SELECT_MEMORY_MODEL
365 config ARCH_ENABLE_MEMORY_HOTPLUG
366 def_bool y if SPARSEMEM
368 config ARCH_ENABLE_MEMORY_HOTREMOVE
371 config ARCH_HIBERNATION_POSSIBLE
376 comment "I/O subsystem configuration"
380 prompt "QDIO support"
382 This driver provides the Queued Direct I/O base support for
385 To compile this driver as a module, choose M here: the
386 module will be called qdio.
392 prompt "Support for CHSC subchannels"
394 This driver allows usage of CHSC subchannels. A CHSC subchannel
395 is usually present on LPAR only.
396 The driver creates a device /dev/chsc, which may be used to
397 obtain I/O configuration information about the machine and
398 to issue asynchronous chsc commands (DANGEROUS).
399 You will usually only want to use this interface on a special
400 LPAR designated for system management.
402 To compile this driver as a module, choose M here: the
403 module will be called chsc_sch.
411 prompt "Builtin IPL record support"
413 If you want to use the produced kernel to IPL directly from a
414 device, you have to merge a bootsector specific to the device
415 into the first bytes of the kernel. You will have to select the
419 prompt "IPL method generated into head.S"
423 Select "tape" if you want to IPL the image from a Tape.
425 Select "vm_reader" if you are running under VM/ESA and want
426 to IPL the image from the emulated card reader.
436 source "fs/Kconfig.binfmt"
438 config FORCE_MAX_ZONEORDER
444 prompt "Pseudo page fault support"
446 Select this option, if you want to use PFAULT pseudo page fault
447 handling under VM. If running native or in LPAR, this option
448 has no effect. If your VM does not support PFAULT, PAGEEX
449 pseudo page fault handling will be used.
450 Note that VM 4.2 supports PFAULT but has a bug in its
451 implementation that causes some problems.
452 Everybody who wants to run Linux under VM != VM4.2 should select
457 prompt "VM shared kernel support"
459 Select this option, if you want to share the text segment of the
460 Linux kernel between different VM guests. This reduces memory
461 usage with lots of guests but greatly increases kernel size.
462 Also if a kernel was IPL'ed from a shared segment the kexec system
464 You should only select this option if you know what you are
465 doing and want to exploit this feature.
469 prompt "Cooperative memory management"
471 Select this option, if you want to enable the kernel interface
472 to reduce the memory size of the system. This is accomplished
473 by allocating pages of memory and put them "on hold". This only
474 makes sense for a system running under VM where the unused pages
475 will be reused by VM for other guest systems. The interface
476 allows an external monitor to balance memory of many systems.
477 Everybody who wants to run Linux under VM should select this
482 prompt "IUCV special message interface to cooperative memory management"
483 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
485 Select this option to enable the special message interface to
486 the cooperative memory management.
490 prompt "Linux - VM Monitor Stream, base infrastructure"
493 This provides a kernel interface for creating and updating z/VM APPLDATA
494 monitor records. The monitor records are updated at certain time
495 intervals, once the timer is started.
496 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
497 i.e. enables or disables monitoring on the Linux side.
498 A custom interval value (in seconds) can be written to
499 /proc/appldata/interval.
501 Defaults are 60 seconds interval and timer off.
502 The /proc entries can also be read from, showing the current settings.
506 prompt "Monitor memory management statistics"
507 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
509 This provides memory management related data to the Linux - VM Monitor
510 Stream, like paging/swapping rate, memory utilisation, etc.
511 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
512 APPLDATA monitor record, i.e. enables or disables monitoring this record
516 The /proc entry can also be read from, showing the current settings.
518 This can also be compiled as a module, which will be called
523 prompt "Monitor OS statistics"
524 depends on APPLDATA_BASE
526 This provides OS related data to the Linux - VM Monitor Stream, like
527 CPU utilisation, etc.
528 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
529 APPLDATA monitor record, i.e. enables or disables monitoring this record
533 This can also be compiled as a module, which will be called
536 config APPLDATA_NET_SUM
538 prompt "Monitor overall network statistics"
539 depends on APPLDATA_BASE && NET
541 This provides network related data to the Linux - VM Monitor Stream,
542 currently there is only a total sum of network I/O statistics, no
544 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
545 APPLDATA monitor record, i.e. enables or disables monitoring this record
549 This can also be compiled as a module, which will be called
552 source kernel/Kconfig.hz
556 prompt "s390 hypervisor file system support"
557 select SYS_HYPERVISOR
559 This is a virtual file system intended to provide accounting
560 information in an s390 hypervisor environment.
564 prompt "kexec system call"
566 kexec is a system call that implements the ability to shutdown your
567 current kernel, and to start another kernel. It is like a reboot
568 but is independent of hardware/microcode support.
572 prompt "zfcpdump support"
575 Select this option if you want to build an zfcpdump enabled kernel.
576 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
580 prompt "s390 guest support for KVM (EXPERIMENTAL)"
581 depends on 64BIT && EXPERIMENTAL
582 select VIRTUALIZATION
585 select VIRTIO_CONSOLE
587 Select this option if you want to run the kernel as a guest under
588 the KVM hypervisor. This will add detection for KVM as well as a
589 virtio transport. If KVM is detected, the virtio console will be
594 prompt "Enable seccomp to safely compute untrusted bytecode"
597 This kernel feature is useful for number crunching applications
598 that may need to compute untrusted bytecode during their
599 execution. By using pipes or other transports made available to
600 the process as file descriptors supporting the read/write
601 syscalls, it's possible to isolate those applications in
602 their own address space using seccomp. Once seccomp is
603 enabled via /proc/<pid>/seccomp, it cannot be disabled
604 and the task is only allowed to execute a few safe syscalls
605 defined by each seccomp mode.
611 menu "Power Management"
613 source "kernel/power/Kconfig"
625 source "drivers/Kconfig"
629 source "arch/s390/Kconfig.debug"
631 source "security/Kconfig"
633 source "crypto/Kconfig"
637 source "arch/s390/kvm/Kconfig"