12 config LOCKDEP_SUPPORT
15 config STACKTRACE_SUPPORT
18 config HAVE_LATENCYTOP_SUPPORT
21 config RWSEM_GENERIC_SPINLOCK
24 config RWSEM_XCHGADD_ALGORITHM
27 config ARCH_HAS_ILOG2_U32
31 config ARCH_HAS_ILOG2_U64
35 config GENERIC_HWEIGHT
38 config GENERIC_TIME_VSYSCALL
41 config GENERIC_CLOCKEVENTS
49 config GENERIC_BUG_RELATIVE_POINTERS
58 config GENERIC_LOCKBREAK
61 depends on SMP && PREEMPT
67 config VIRT_CPU_ACCOUNTING
70 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
75 select USE_GENERIC_SMP_HELPERS if SMP
76 select HAVE_SYSCALL_WRAPPERS
77 select HAVE_FUNCTION_TRACER
78 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
79 select HAVE_FTRACE_MCOUNT_RECORD
80 select HAVE_SYSCALL_TRACEPOINTS
81 select HAVE_DYNAMIC_FTRACE
82 select HAVE_FUNCTION_GRAPH_TRACER
83 select HAVE_REGS_AND_STACK_ACCESS_API
84 select HAVE_DEFAULT_NO_SPIN_MUTEXES
87 select HAVE_KRETPROBES
88 select HAVE_KVM if 64BIT
89 select HAVE_ARCH_TRACEHOOK
90 select INIT_ALL_POSSIBLE
91 select HAVE_PERF_EVENTS
92 select HAVE_KERNEL_GZIP
93 select HAVE_KERNEL_BZIP2
94 select HAVE_KERNEL_LZMA
95 select HAVE_KERNEL_LZO
96 select ARCH_INLINE_SPIN_TRYLOCK
97 select ARCH_INLINE_SPIN_TRYLOCK_BH
98 select ARCH_INLINE_SPIN_LOCK
99 select ARCH_INLINE_SPIN_LOCK_BH
100 select ARCH_INLINE_SPIN_LOCK_IRQ
101 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
102 select ARCH_INLINE_SPIN_UNLOCK
103 select ARCH_INLINE_SPIN_UNLOCK_BH
104 select ARCH_INLINE_SPIN_UNLOCK_IRQ
105 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
106 select ARCH_INLINE_READ_TRYLOCK
107 select ARCH_INLINE_READ_LOCK
108 select ARCH_INLINE_READ_LOCK_BH
109 select ARCH_INLINE_READ_LOCK_IRQ
110 select ARCH_INLINE_READ_LOCK_IRQSAVE
111 select ARCH_INLINE_READ_UNLOCK
112 select ARCH_INLINE_READ_UNLOCK_BH
113 select ARCH_INLINE_READ_UNLOCK_IRQ
114 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
115 select ARCH_INLINE_WRITE_TRYLOCK
116 select ARCH_INLINE_WRITE_LOCK
117 select ARCH_INLINE_WRITE_LOCK_BH
118 select ARCH_INLINE_WRITE_LOCK_IRQ
119 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
120 select ARCH_INLINE_WRITE_UNLOCK
121 select ARCH_INLINE_WRITE_UNLOCK_BH
122 select ARCH_INLINE_WRITE_UNLOCK_IRQ
123 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
125 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"
142 Select this option if you have a 64 bit IBM zSeries machine
143 and want to use the 64 bit addressing mode.
153 bool "Symmetric multi-processing support"
155 This enables support for systems with more than one CPU. If you have
156 a system with only one CPU, like most personal computers, say N. If
157 you have a system with more than one CPU, say Y.
159 If you say N here, the kernel will run on single and multiprocessor
160 machines, but will use only one CPU of a multiprocessor machine. If
161 you say Y here, the kernel will run on many, but not all,
162 singleprocessor machines. On a singleprocessor machine, the kernel
163 will run faster if you say N here.
165 See also the SMP-HOWTO available at
166 <http://www.tldp.org/docs.html#howto>.
168 Even if you don't know what to do here, say Y.
171 int "Maximum number of CPUs (2-64)"
174 default "32" if !64BIT
175 default "64" if 64BIT
177 This allows you to specify the maximum number of CPUs which this
178 kernel will support. The maximum supported value is 64 and the
179 minimum value which makes sense is 2.
181 This is purely to save memory - each supported CPU adds
182 approximately sixteen kilobytes to the kernel image.
185 bool "Support for hot-pluggable CPUs"
190 Say Y here to be able to turn CPUs off and on. CPUs
191 can be controlled through /sys/devices/system/cpu/cpu#.
192 Say N if you want to disable CPU hotplug.
195 bool "IEEE FPU emulation"
198 This option is required for IEEE compliant floating point arithmetic
199 on older S/390 machines. Say Y unless you know your machine doesn't
203 bool "Kernel support for 31 bit emulation"
205 select COMPAT_BINFMT_ELF
207 Select this option if you want to enable your system kernel to
208 handle system-calls from ELF binaries for 31 bit ESA. This option
209 (and some other stuff like libraries and such) is needed for
210 executing 31 bit applications. It is safe to say "Y".
212 config SYSVIPC_COMPAT
214 depends on COMPAT && SYSVIPC
221 config S390_EXEC_PROTECT
222 bool "Data execute protection"
224 This option allows to enable a buffer overflow protection for user
225 space programs and it also selects the addressing mode option above.
226 The kernel parameter noexec=on will enable this feature and also
227 switch the addressing modes, default is disabled. Enabling this (via
228 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
229 will reduce system performance.
231 comment "Code generation options"
234 prompt "Processor type"
238 bool "S/390 model G5 and G6"
241 Select this to build a 31 bit kernel that works
242 on all S/390 and zSeries machines.
245 bool "IBM eServer zSeries model z800 and z900"
247 Select this to optimize for zSeries machines. This
248 will enable some optimizations that are not available
249 on older 31 bit only CPUs.
252 bool "IBM eServer zSeries model z890 and z990"
254 Select this enable optimizations for model z890/z990.
255 This will be slightly faster but does not work on
256 older machines such as the z900.
261 Select this to enable optimizations for IBM System z9-109, IBM
262 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
263 Class (z9 BC). The kernel will be slightly faster but will not
264 work on older machines such as the z990, z890, z900, and z800.
267 bool "IBM System z10"
269 Select this to enable optimizations for IBM System z10. The
270 kernel will be slightly faster but will not work on older
271 machines such as the z990, z890, z900, z800, z9-109, z9-ec
277 bool "Pack kernel stack"
279 This option enables the compiler option -mkernel-backchain if it
280 is available. If the option is available the compiler supports
281 the new stack layout which dramatically reduces the minimum stack
282 frame size. With an old compiler a non-leaf function needs a
283 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
284 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
285 and 24 byte on 64 bit.
287 Say Y if you are unsure.
290 bool "Use 8kb for kernel stack instead of 16kb"
291 depends on PACK_STACK && 64BIT && !LOCKDEP
293 If you say Y here and the compiler supports the -mkernel-backchain
294 option the kernel will use a smaller kernel stack size. The reduced
295 size is 8kb instead of 16kb. This allows to run more threads on a
296 system and reduces the pressure on the memory management for higher
297 order page allocations.
299 Say N if you are unsure.
302 bool "Detect kernel stack overflow"
304 This option enables the compiler option -mstack-guard and
305 -mstack-size if they are available. If the compiler supports them
306 it will emit additional code to each function prolog to trigger
307 an illegal operation if the kernel stack is about to overflow.
309 Say N if you are unsure.
312 int "Size of the guard area (128-1024)"
314 depends on CHECK_STACK
317 This allows you to specify the size of the guard area at the lower
318 end of the kernel stack. If the kernel stack points into the guard
319 area on function entry an illegal operation is triggered. The size
320 needs to be a power of 2. Please keep in mind that the size of an
321 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
322 The minimum size for the stack guard should be 256 for 31 bit and
326 bool "Emit compiler warnings for function with broken stack usage"
328 This option enables the compiler options -mwarn-framesize and
329 -mwarn-dynamicstack. If the compiler supports these options it
330 will generate warnings for function which either use alloca or
331 create a stack frame bigger than CONFIG_WARN_STACK_SIZE.
333 Say N if you are unsure.
335 config WARN_STACK_SIZE
336 int "Maximum frame size considered safe (128-2048)"
338 depends on WARN_STACK
341 This allows you to specify the maximum frame size a function may
342 have without the compiler complaining about it.
344 config ARCH_POPULATES_NODE_MAP
347 comment "Kernel preemption"
349 source "kernel/Kconfig.preempt"
351 config ARCH_SPARSEMEM_ENABLE
353 select SPARSEMEM_VMEMMAP_ENABLE
354 select SPARSEMEM_VMEMMAP
355 select SPARSEMEM_STATIC if !64BIT
357 config ARCH_SPARSEMEM_DEFAULT
360 config ARCH_SELECT_MEMORY_MODEL
363 config ARCH_ENABLE_MEMORY_HOTPLUG
367 config ARCH_ENABLE_MEMORY_HOTREMOVE
370 config ARCH_HIBERNATION_POSSIBLE
375 comment "I/O subsystem configuration"
378 tristate "QDIO support"
380 This driver provides the Queued Direct I/O base support for
383 To compile this driver as a module, choose M here: the
384 module will be called qdio.
389 tristate "Support for CHSC subchannels"
391 This driver allows usage of CHSC subchannels. A CHSC subchannel
392 is usually present on LPAR only.
393 The driver creates a device /dev/chsc, which may be used to
394 obtain I/O configuration information about the machine and
395 to issue asynchronous chsc commands (DANGEROUS).
396 You will usually only want to use this interface on a special
397 LPAR designated for system management.
399 To compile this driver as a module, choose M here: the
400 module will be called chsc_sch.
407 bool "Builtin IPL record support"
409 If you want to use the produced kernel to IPL directly from a
410 device, you have to merge a bootsector specific to the device
411 into the first bytes of the kernel. You will have to select the
415 prompt "IPL method generated into head.S"
419 Select "tape" if you want to IPL the image from a Tape.
421 Select "vm_reader" if you are running under VM/ESA and want
422 to IPL the image from the emulated card reader.
432 source "fs/Kconfig.binfmt"
434 config FORCE_MAX_ZONEORDER
439 bool "Pseudo page fault support"
441 Select this option, if you want to use PFAULT pseudo page fault
442 handling under VM. If running native or in LPAR, this option
443 has no effect. If your VM does not support PFAULT, PAGEEX
444 pseudo page fault handling will be used.
445 Note that VM 4.2 supports PFAULT but has a bug in its
446 implementation that causes some problems.
447 Everybody who wants to run Linux under VM != VM4.2 should select
451 bool "VM shared kernel support"
453 Select this option, if you want to share the text segment of the
454 Linux kernel between different VM guests. This reduces memory
455 usage with lots of guests but greatly increases kernel size.
456 Also if a kernel was IPL'ed from a shared segment the kexec system
458 You should only select this option if you know what you are
459 doing and want to exploit this feature.
462 tristate "Cooperative memory management"
464 Select this option, if you want to enable the kernel interface
465 to reduce the memory size of the system. This is accomplished
466 by allocating pages of memory and put them "on hold". This only
467 makes sense for a system running under VM where the unused pages
468 will be reused by VM for other guest systems. The interface
469 allows an external monitor to balance memory of many systems.
470 Everybody who wants to run Linux under VM should select this
474 bool "IUCV special message interface to cooperative memory management"
475 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
477 Select this option to enable the special message interface to
478 the cooperative memory management.
481 bool "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.
496 tristate "Monitor memory management statistics"
497 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
499 This provides memory management related data to the Linux - VM Monitor
500 Stream, like paging/swapping rate, memory utilisation, etc.
501 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
502 APPLDATA monitor record, i.e. enables or disables monitoring this record
506 The /proc entry can also be read from, showing the current settings.
508 This can also be compiled as a module, which will be called
512 tristate "Monitor OS statistics"
513 depends on APPLDATA_BASE
515 This provides OS related data to the Linux - VM Monitor Stream, like
516 CPU utilisation, etc.
517 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
518 APPLDATA monitor record, i.e. enables or disables monitoring this record
522 This can also be compiled as a module, which will be called
525 config APPLDATA_NET_SUM
526 tristate "Monitor overall network statistics"
527 depends on APPLDATA_BASE && NET
529 This provides network related data to the Linux - VM Monitor Stream,
530 currently there is only a total sum of network I/O statistics, no
532 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
533 APPLDATA monitor record, i.e. enables or disables monitoring this record
537 This can also be compiled as a module, which will be called
540 source kernel/Kconfig.hz
543 bool "s390 hypervisor file system support"
544 select SYS_HYPERVISOR
547 This is a virtual file system intended to provide accounting
548 information in an s390 hypervisor environment.
551 bool "kexec system call"
553 kexec is a system call that implements the ability to shutdown your
554 current kernel, and to start another kernel. It is like a reboot
555 but is independent of hardware/microcode support.
558 bool "zfcpdump support"
562 Select this option if you want to build an zfcpdump enabled kernel.
563 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
566 bool "s390 guest support for KVM (EXPERIMENTAL)"
567 depends on 64BIT && EXPERIMENTAL
570 select VIRTIO_CONSOLE
572 Select this option if you want to run the kernel as a guest under
573 the KVM hypervisor. This will add detection for KVM as well as a
574 virtio transport. If KVM is detected, the virtio console will be
578 bool "Enable seccomp to safely compute untrusted bytecode"
582 This kernel feature is useful for number crunching applications
583 that may need to compute untrusted bytecode during their
584 execution. By using pipes or other transports made available to
585 the process as file descriptors supporting the read/write
586 syscalls, it's possible to isolate those applications in
587 their own address space using seccomp. Once seccomp is
588 enabled via /proc/<pid>/seccomp, it cannot be disabled
589 and the task is only allowed to execute a few safe syscalls
590 defined by each seccomp mode.
596 menu "Power Management"
598 source "kernel/power/Kconfig"
610 source "drivers/Kconfig"
614 source "arch/s390/Kconfig.debug"
616 source "security/Kconfig"
618 source "crypto/Kconfig"
622 source "arch/s390/kvm/Kconfig"