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.
201 prompt "Multi-core scheduler support"
204 Multi-core scheduler support improves the CPU scheduler's decision
205 making when dealing with multi-core CPU chips at a cost of slightly
206 increased overhead in some places.
209 bool "Book scheduler support"
210 depends on SMP && SCHED_MC
212 Book scheduler support improves the CPU scheduler's decision making
213 when dealing with machines that have several books.
216 bool "IEEE FPU emulation"
219 This option is required for IEEE compliant floating point arithmetic
220 on older ESA/390 machines. Say Y unless you know your machine doesn't
224 bool "Kernel support for 31 bit emulation"
226 select COMPAT_BINFMT_ELF
228 Select this option if you want to enable your system kernel to
229 handle system-calls from ELF binaries for 31 bit ESA. This option
230 (and some other stuff like libraries and such) is needed for
231 executing 31 bit applications. It is safe to say "Y".
233 config SYSVIPC_COMPAT
235 depends on COMPAT && SYSVIPC
242 config S390_EXEC_PROTECT
243 bool "Data execute protection"
245 This option allows to enable a buffer overflow protection for user
246 space programs and it also selects the addressing mode option above.
247 The kernel parameter noexec=on will enable this feature and also
248 switch the addressing modes, default is disabled. Enabling this (via
249 kernel parameter) on machines earlier than IBM System z9 this will
250 reduce system performance.
252 comment "Code generation options"
255 prompt "Processor type"
259 bool "System/390 model G5 and G6"
262 Select this to build a 31 bit kernel that works
263 on all ESA/390 and z/Architecture machines.
266 bool "IBM zSeries model z800 and z900"
268 Select this to enable optimizations for model z800/z900 (2064 and
269 2066 series). This will enable some optimizations that are not
270 available on older ESA/390 (31 Bit) only CPUs.
273 bool "IBM zSeries model z890 and z990"
275 Select this to enable optimizations for model z890/z990 (2084 and
276 2086 series). The kernel will be slightly faster but will not work
282 Select this to enable optimizations for IBM System z9 (2094 and
283 2096 series). The kernel will be slightly faster but will not work
287 bool "IBM System z10"
289 Select this to enable optimizations for IBM System z10 (2097 and
290 2098 series). The kernel will be slightly faster but will not work
294 bool "IBM zEnterprise 196"
296 Select this to enable optimizations for IBM zEnterprise 196
297 (2817 series). The kernel will be slightly faster but will not work
303 bool "Pack kernel stack"
305 This option enables the compiler option -mkernel-backchain if it
306 is available. If the option is available the compiler supports
307 the new stack layout which dramatically reduces the minimum stack
308 frame size. With an old compiler a non-leaf function needs a
309 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
310 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
311 and 24 byte on 64 bit.
313 Say Y if you are unsure.
316 bool "Use 8kb for kernel stack instead of 16kb"
317 depends on PACK_STACK && 64BIT && !LOCKDEP
319 If you say Y here and the compiler supports the -mkernel-backchain
320 option the kernel will use a smaller kernel stack size. The reduced
321 size is 8kb instead of 16kb. This allows to run more threads on a
322 system and reduces the pressure on the memory management for higher
323 order page allocations.
325 Say N if you are unsure.
328 bool "Detect kernel stack overflow"
330 This option enables the compiler option -mstack-guard and
331 -mstack-size if they are available. If the compiler supports them
332 it will emit additional code to each function prolog to trigger
333 an illegal operation if the kernel stack is about to overflow.
335 Say N if you are unsure.
338 int "Size of the guard area (128-1024)"
340 depends on CHECK_STACK
343 This allows you to specify the size of the guard area at the lower
344 end of the kernel stack. If the kernel stack points into the guard
345 area on function entry an illegal operation is triggered. The size
346 needs to be a power of 2. Please keep in mind that the size of an
347 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
348 The minimum size for the stack guard should be 256 for 31 bit and
352 bool "Emit compiler warnings for function with broken stack usage"
354 This option enables the compiler options -mwarn-framesize and
355 -mwarn-dynamicstack. If the compiler supports these options it
356 will generate warnings for function which either use alloca or
357 create a stack frame bigger than CONFIG_WARN_STACK_SIZE.
359 Say N if you are unsure.
361 config WARN_STACK_SIZE
362 int "Maximum frame size considered safe (128-2048)"
364 depends on WARN_STACK
367 This allows you to specify the maximum frame size a function may
368 have without the compiler complaining about it.
370 config ARCH_POPULATES_NODE_MAP
373 comment "Kernel preemption"
375 source "kernel/Kconfig.preempt"
377 config ARCH_SPARSEMEM_ENABLE
379 select SPARSEMEM_VMEMMAP_ENABLE
380 select SPARSEMEM_VMEMMAP
381 select SPARSEMEM_STATIC if !64BIT
383 config ARCH_SPARSEMEM_DEFAULT
386 config ARCH_SELECT_MEMORY_MODEL
389 config ARCH_ENABLE_MEMORY_HOTPLUG
393 config ARCH_ENABLE_MEMORY_HOTREMOVE
396 config ARCH_HIBERNATION_POSSIBLE
401 comment "I/O subsystem configuration"
404 tristate "QDIO support"
406 This driver provides the Queued Direct I/O base support for
409 To compile this driver as a module, choose M here: the
410 module will be called qdio.
415 tristate "Support for CHSC subchannels"
417 This driver allows usage of CHSC subchannels. A CHSC subchannel
418 is usually present on LPAR only.
419 The driver creates a device /dev/chsc, which may be used to
420 obtain I/O configuration information about the machine and
421 to issue asynchronous chsc commands (DANGEROUS).
422 You will usually only want to use this interface on a special
423 LPAR designated for system management.
425 To compile this driver as a module, choose M here: the
426 module will be called chsc_sch.
433 bool "Builtin IPL record support"
435 If you want to use the produced kernel to IPL directly from a
436 device, you have to merge a bootsector specific to the device
437 into the first bytes of the kernel. You will have to select the
441 prompt "IPL method generated into head.S"
445 Select "tape" if you want to IPL the image from a Tape.
447 Select "vm_reader" if you are running under VM/ESA and want
448 to IPL the image from the emulated card reader.
458 source "fs/Kconfig.binfmt"
460 config FORCE_MAX_ZONEORDER
465 bool "Pseudo page fault support"
467 Select this option, if you want to use PFAULT pseudo page fault
468 handling under VM. If running native or in LPAR, this option
469 has no effect. If your VM does not support PFAULT, PAGEEX
470 pseudo page fault handling will be used.
471 Note that VM 4.2 supports PFAULT but has a bug in its
472 implementation that causes some problems.
473 Everybody who wants to run Linux under VM != VM4.2 should select
477 bool "VM shared kernel support"
479 Select this option, if you want to share the text segment of the
480 Linux kernel between different VM guests. This reduces memory
481 usage with lots of guests but greatly increases kernel size.
482 Also if a kernel was IPL'ed from a shared segment the kexec system
484 You should only select this option if you know what you are
485 doing and want to exploit this feature.
488 tristate "Cooperative memory management"
490 Select this option, if you want to enable the kernel interface
491 to reduce the memory size of the system. This is accomplished
492 by allocating pages of memory and put them "on hold". This only
493 makes sense for a system running under VM where the unused pages
494 will be reused by VM for other guest systems. The interface
495 allows an external monitor to balance memory of many systems.
496 Everybody who wants to run Linux under VM should select this
500 bool "IUCV special message interface to cooperative memory management"
501 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
503 Select this option to enable the special message interface to
504 the cooperative memory management.
507 bool "Linux - VM Monitor Stream, base infrastructure"
510 This provides a kernel interface for creating and updating z/VM APPLDATA
511 monitor records. The monitor records are updated at certain time
512 intervals, once the timer is started.
513 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
514 i.e. enables or disables monitoring on the Linux side.
515 A custom interval value (in seconds) can be written to
516 /proc/appldata/interval.
518 Defaults are 60 seconds interval and timer off.
519 The /proc entries can also be read from, showing the current settings.
522 tristate "Monitor memory management statistics"
523 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
525 This provides memory management related data to the Linux - VM Monitor
526 Stream, like paging/swapping rate, memory utilisation, etc.
527 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
528 APPLDATA monitor record, i.e. enables or disables monitoring this record
532 The /proc entry can also be read from, showing the current settings.
534 This can also be compiled as a module, which will be called
538 tristate "Monitor OS statistics"
539 depends on APPLDATA_BASE
541 This provides OS related data to the Linux - VM Monitor Stream, like
542 CPU utilisation, etc.
543 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
544 APPLDATA monitor record, i.e. enables or disables monitoring this record
548 This can also be compiled as a module, which will be called
551 config APPLDATA_NET_SUM
552 tristate "Monitor overall network statistics"
553 depends on APPLDATA_BASE && NET
555 This provides network related data to the Linux - VM Monitor Stream,
556 currently there is only a total sum of network I/O statistics, no
558 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
559 APPLDATA monitor record, i.e. enables or disables monitoring this record
563 This can also be compiled as a module, which will be called
566 source kernel/Kconfig.hz
569 bool "s390 hypervisor file system support"
570 select SYS_HYPERVISOR
573 This is a virtual file system intended to provide accounting
574 information in an s390 hypervisor environment.
577 bool "kexec system call"
579 kexec is a system call that implements the ability to shutdown your
580 current kernel, and to start another kernel. It is like a reboot
581 but is independent of hardware/microcode support.
584 bool "zfcpdump support"
588 Select this option if you want to build an zfcpdump enabled kernel.
589 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
592 bool "s390 guest support for KVM (EXPERIMENTAL)"
593 depends on 64BIT && EXPERIMENTAL
596 select VIRTIO_CONSOLE
598 Select this option if you want to run the kernel as a guest under
599 the KVM hypervisor. This will add detection for KVM as well as a
600 virtio transport. If KVM is detected, the virtio console will be
604 bool "Enable seccomp to safely compute untrusted bytecode"
608 This kernel feature is useful for number crunching applications
609 that may need to compute untrusted bytecode during their
610 execution. By using pipes or other transports made available to
611 the process as file descriptors supporting the read/write
612 syscalls, it's possible to isolate those applications in
613 their own address space using seccomp. Once seccomp is
614 enabled via /proc/<pid>/seccomp, it cannot be disabled
615 and the task is only allowed to execute a few safe syscalls
616 defined by each seccomp mode.
622 menu "Power Management"
624 source "kernel/power/Kconfig"
636 source "drivers/Kconfig"
640 source "arch/s390/Kconfig.debug"
642 source "security/Kconfig"
644 source "crypto/Kconfig"
648 source "arch/s390/kvm/Kconfig"