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 ARCH_DMA_ADDR_T_64BIT
61 config GENERIC_LOCKBREAK
64 depends on SMP && PREEMPT
70 config VIRT_CPU_ACCOUNTING
73 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
78 select USE_GENERIC_SMP_HELPERS if SMP
79 select HAVE_SYSCALL_WRAPPERS
80 select HAVE_FUNCTION_TRACER
81 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
82 select HAVE_FTRACE_MCOUNT_RECORD
83 select HAVE_SYSCALL_TRACEPOINTS
84 select HAVE_DYNAMIC_FTRACE
85 select HAVE_FUNCTION_GRAPH_TRACER
86 select HAVE_REGS_AND_STACK_ACCESS_API
87 select HAVE_DEFAULT_NO_SPIN_MUTEXES
90 select HAVE_KRETPROBES
91 select HAVE_KVM if 64BIT
92 select HAVE_ARCH_TRACEHOOK
93 select INIT_ALL_POSSIBLE
95 select HAVE_PERF_EVENTS
96 select HAVE_KERNEL_GZIP
97 select HAVE_KERNEL_BZIP2
98 select HAVE_KERNEL_LZMA
99 select HAVE_KERNEL_LZO
100 select HAVE_GET_USER_PAGES_FAST
101 select ARCH_INLINE_SPIN_TRYLOCK
102 select ARCH_INLINE_SPIN_TRYLOCK_BH
103 select ARCH_INLINE_SPIN_LOCK
104 select ARCH_INLINE_SPIN_LOCK_BH
105 select ARCH_INLINE_SPIN_LOCK_IRQ
106 select ARCH_INLINE_SPIN_LOCK_IRQSAVE
107 select ARCH_INLINE_SPIN_UNLOCK
108 select ARCH_INLINE_SPIN_UNLOCK_BH
109 select ARCH_INLINE_SPIN_UNLOCK_IRQ
110 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
111 select ARCH_INLINE_READ_TRYLOCK
112 select ARCH_INLINE_READ_LOCK
113 select ARCH_INLINE_READ_LOCK_BH
114 select ARCH_INLINE_READ_LOCK_IRQ
115 select ARCH_INLINE_READ_LOCK_IRQSAVE
116 select ARCH_INLINE_READ_UNLOCK
117 select ARCH_INLINE_READ_UNLOCK_BH
118 select ARCH_INLINE_READ_UNLOCK_IRQ
119 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
120 select ARCH_INLINE_WRITE_TRYLOCK
121 select ARCH_INLINE_WRITE_LOCK
122 select ARCH_INLINE_WRITE_LOCK_BH
123 select ARCH_INLINE_WRITE_LOCK_IRQ
124 select ARCH_INLINE_WRITE_LOCK_IRQSAVE
125 select ARCH_INLINE_WRITE_UNLOCK
126 select ARCH_INLINE_WRITE_UNLOCK_BH
127 select ARCH_INLINE_WRITE_UNLOCK_IRQ
128 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
130 config SCHED_OMIT_FRAME_POINTER
134 source "init/Kconfig"
136 source "kernel/Kconfig.freezer"
140 comment "Processor type and features"
142 source "kernel/time/Kconfig"
147 Select this option if you have an IBM z/Architecture machine
148 and want to use the 64 bit addressing mode.
158 bool "Symmetric multi-processing support"
160 This enables support for systems with more than one CPU. If you have
161 a system with only one CPU, like most personal computers, say N. If
162 you have a system with more than one CPU, say Y.
164 If you say N here, the kernel will run on single and multiprocessor
165 machines, but will use only one CPU of a multiprocessor machine. If
166 you say Y here, the kernel will run on many, but not all,
167 singleprocessor machines. On a singleprocessor machine, the kernel
168 will run faster if you say N here.
170 See also the SMP-HOWTO available at
171 <http://www.tldp.org/docs.html#howto>.
173 Even if you don't know what to do here, say Y.
176 int "Maximum number of CPUs (2-64)"
179 default "32" if !64BIT
180 default "64" if 64BIT
182 This allows you to specify the maximum number of CPUs which this
183 kernel will support. The maximum supported value is 64 and the
184 minimum value which makes sense is 2.
186 This is purely to save memory - each supported CPU adds
187 approximately sixteen kilobytes to the kernel image.
190 bool "Support for hot-pluggable CPUs"
195 Say Y here to be able to turn CPUs off and on. CPUs
196 can be controlled through /sys/devices/system/cpu/cpu#.
197 Say N if you want to disable CPU hotplug.
200 bool "Book scheduler support"
203 Book scheduler support improves the CPU scheduler's decision making
204 when dealing with machines that have several books.
207 bool "IEEE FPU emulation"
210 This option is required for IEEE compliant floating point arithmetic
211 on older ESA/390 machines. Say Y unless you know your machine doesn't
215 bool "Kernel support for 31 bit emulation"
217 select COMPAT_BINFMT_ELF
219 Select this option if you want to enable your system kernel to
220 handle system-calls from ELF binaries for 31 bit ESA. This option
221 (and some other stuff like libraries and such) is needed for
222 executing 31 bit applications. It is safe to say "Y".
224 config SYSVIPC_COMPAT
226 depends on COMPAT && SYSVIPC
233 config S390_EXEC_PROTECT
234 bool "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
294 bool "Pack kernel stack"
296 This option enables the compiler option -mkernel-backchain if it
297 is available. If the option is available the compiler supports
298 the new stack layout which dramatically reduces the minimum stack
299 frame size. With an old compiler a non-leaf function needs a
300 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
301 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
302 and 24 byte on 64 bit.
304 Say Y if you are unsure.
307 bool "Use 8kb for kernel stack instead of 16kb"
308 depends on PACK_STACK && 64BIT && !LOCKDEP
310 If you say Y here and the compiler supports the -mkernel-backchain
311 option the kernel will use a smaller kernel stack size. The reduced
312 size is 8kb instead of 16kb. This allows to run more threads on a
313 system and reduces the pressure on the memory management for higher
314 order page allocations.
316 Say N if you are unsure.
319 bool "Detect kernel stack overflow"
321 This option enables the compiler option -mstack-guard and
322 -mstack-size if they are available. If the compiler supports them
323 it will emit additional code to each function prolog to trigger
324 an illegal operation if the kernel stack is about to overflow.
326 Say N if you are unsure.
329 int "Size of the guard area (128-1024)"
331 depends on CHECK_STACK
334 This allows you to specify the size of the guard area at the lower
335 end of the kernel stack. If the kernel stack points into the guard
336 area on function entry an illegal operation is triggered. The size
337 needs to be a power of 2. Please keep in mind that the size of an
338 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
339 The minimum size for the stack guard should be 256 for 31 bit and
343 bool "Emit compiler warnings for function with broken stack usage"
345 This option enables the compiler options -mwarn-framesize and
346 -mwarn-dynamicstack. If the compiler supports these options it
347 will generate warnings for function which either use alloca or
348 create a stack frame bigger than CONFIG_WARN_STACK_SIZE.
350 Say N if you are unsure.
352 config WARN_STACK_SIZE
353 int "Maximum frame size considered safe (128-2048)"
355 depends on WARN_STACK
358 This allows you to specify the maximum frame size a function may
359 have without the compiler complaining about it.
361 config ARCH_POPULATES_NODE_MAP
364 comment "Kernel preemption"
366 source "kernel/Kconfig.preempt"
368 config ARCH_SPARSEMEM_ENABLE
370 select SPARSEMEM_VMEMMAP_ENABLE
371 select SPARSEMEM_VMEMMAP
372 select SPARSEMEM_STATIC if !64BIT
374 config ARCH_SPARSEMEM_DEFAULT
377 config ARCH_SELECT_MEMORY_MODEL
380 config ARCH_ENABLE_MEMORY_HOTPLUG
384 config ARCH_ENABLE_MEMORY_HOTREMOVE
387 config ARCH_HIBERNATION_POSSIBLE
392 comment "I/O subsystem configuration"
395 tristate "QDIO support"
397 This driver provides the Queued Direct I/O base support for
400 To compile this driver as a module, choose M here: the
401 module will be called qdio.
406 tristate "Support for CHSC subchannels"
408 This driver allows usage of CHSC subchannels. A CHSC subchannel
409 is usually present on LPAR only.
410 The driver creates a device /dev/chsc, which may be used to
411 obtain I/O configuration information about the machine and
412 to issue asynchronous chsc commands (DANGEROUS).
413 You will usually only want to use this interface on a special
414 LPAR designated for system management.
416 To compile this driver as a module, choose M here: the
417 module will be called chsc_sch.
424 bool "Builtin IPL record support"
426 If you want to use the produced kernel to IPL directly from a
427 device, you have to merge a bootsector specific to the device
428 into the first bytes of the kernel. You will have to select the
432 prompt "IPL method generated into head.S"
436 Select "tape" if you want to IPL the image from a Tape.
438 Select "vm_reader" if you are running under VM/ESA and want
439 to IPL the image from the emulated card reader.
449 source "fs/Kconfig.binfmt"
451 config FORCE_MAX_ZONEORDER
456 bool "Pseudo page fault support"
458 Select this option, if you want to use PFAULT pseudo page fault
459 handling under VM. If running native or in LPAR, this option
460 has no effect. If your VM does not support PFAULT, PAGEEX
461 pseudo page fault handling will be used.
462 Note that VM 4.2 supports PFAULT but has a bug in its
463 implementation that causes some problems.
464 Everybody who wants to run Linux under VM != VM4.2 should select
468 bool "VM shared kernel support"
470 Select this option, if you want to share the text segment of the
471 Linux kernel between different VM guests. This reduces memory
472 usage with lots of guests but greatly increases kernel size.
473 Also if a kernel was IPL'ed from a shared segment the kexec system
475 You should only select this option if you know what you are
476 doing and want to exploit this feature.
479 tristate "Cooperative memory management"
481 Select this option, if you want to enable the kernel interface
482 to reduce the memory size of the system. This is accomplished
483 by allocating pages of memory and put them "on hold". This only
484 makes sense for a system running under VM where the unused pages
485 will be reused by VM for other guest systems. The interface
486 allows an external monitor to balance memory of many systems.
487 Everybody who wants to run Linux under VM should select this
491 bool "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.
498 bool "Linux - VM Monitor Stream, base infrastructure"
501 This provides a kernel interface for creating and updating z/VM APPLDATA
502 monitor records. The monitor records are updated at certain time
503 intervals, once the timer is started.
504 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
505 i.e. enables or disables monitoring on the Linux side.
506 A custom interval value (in seconds) can be written to
507 /proc/appldata/interval.
509 Defaults are 60 seconds interval and timer off.
510 The /proc entries can also be read from, showing the current settings.
513 tristate "Monitor memory management statistics"
514 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
516 This provides memory management related data to the Linux - VM Monitor
517 Stream, like paging/swapping rate, memory utilisation, etc.
518 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
519 APPLDATA monitor record, i.e. enables or disables monitoring this record
523 The /proc entry can also be read from, showing the current settings.
525 This can also be compiled as a module, which will be called
529 tristate "Monitor OS statistics"
530 depends on APPLDATA_BASE
532 This provides OS related data to the Linux - VM Monitor Stream, like
533 CPU utilisation, etc.
534 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
535 APPLDATA monitor record, i.e. enables or disables monitoring this record
539 This can also be compiled as a module, which will be called
542 config APPLDATA_NET_SUM
543 tristate "Monitor overall network statistics"
544 depends on APPLDATA_BASE && NET
546 This provides network related data to the Linux - VM Monitor Stream,
547 currently there is only a total sum of network I/O statistics, no
549 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
550 APPLDATA monitor record, i.e. enables or disables monitoring this record
554 This can also be compiled as a module, which will be called
557 source kernel/Kconfig.hz
560 bool "s390 hypervisor file system support"
561 select SYS_HYPERVISOR
564 This is a virtual file system intended to provide accounting
565 information in an s390 hypervisor environment.
568 bool "kexec system call"
570 kexec is a system call that implements the ability to shutdown your
571 current kernel, and to start another kernel. It is like a reboot
572 but is independent of hardware/microcode support.
575 bool "zfcpdump support"
579 Select this option if you want to build an zfcpdump enabled kernel.
580 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
583 bool "s390 guest support for KVM (EXPERIMENTAL)"
584 depends on 64BIT && EXPERIMENTAL
587 select VIRTIO_CONSOLE
589 Select this option if you want to run the kernel as a guest under
590 the KVM hypervisor. This will add detection for KVM as well as a
591 virtio transport. If KVM is detected, the virtio console will be
595 bool "Enable seccomp to safely compute untrusted bytecode"
599 This kernel feature is useful for number crunching applications
600 that may need to compute untrusted bytecode during their
601 execution. By using pipes or other transports made available to
602 the process as file descriptors supporting the read/write
603 syscalls, it's possible to isolate those applications in
604 their own address space using seccomp. Once seccomp is
605 enabled via /proc/<pid>/seccomp, it cannot be disabled
606 and the task is only allowed to execute a few safe syscalls
607 defined by each seccomp mode.
613 menu "Power Management"
615 source "kernel/power/Kconfig"
627 source "drivers/Kconfig"
631 source "arch/s390/Kconfig.debug"
633 source "security/Kconfig"
635 source "crypto/Kconfig"
639 source "arch/s390/kvm/Kconfig"