2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
17 config LOCKDEP_SUPPORT
20 config STACKTRACE_SUPPORT
23 config HAVE_LATENCYTOP_SUPPORT
26 config RWSEM_GENERIC_SPINLOCK
29 config RWSEM_XCHGADD_ALGORITHM
32 config ARCH_HAS_ILOG2_U32
36 config ARCH_HAS_ILOG2_U64
40 config GENERIC_HWEIGHT
46 config GENERIC_CLOCKEVENTS
60 config GENERIC_LOCKBREAK
63 depends on SMP && PREEMPT
69 mainmenu "Linux Kernel Configuration"
75 select HAVE_KRETPROBES
76 select HAVE_KVM if 64BIT
82 comment "Processor type and features"
84 source "kernel/time/Kconfig"
89 Select this option if you have a 64 bit IBM zSeries machine
90 and want to use the 64 bit addressing mode.
97 bool "Symmetric multi-processing support"
99 This enables support for systems with more than one CPU. If you have
100 a system with only one CPU, like most personal computers, say N. If
101 you have a system with more than one CPU, say Y.
103 If you say N here, the kernel will run on single and multiprocessor
104 machines, but will use only one CPU of a multiprocessor machine. If
105 you say Y here, the kernel will run on many, but not all,
106 singleprocessor machines. On a singleprocessor machine, the kernel
107 will run faster if you say N here.
109 See also the SMP-HOWTO available at
110 <http://www.tldp.org/docs.html#howto>.
112 Even if you don't know what to do here, say Y.
115 int "Maximum number of CPUs (2-64)"
118 default "32" if !64BIT
119 default "64" if 64BIT
121 This allows you to specify the maximum number of CPUs which this
122 kernel will support. The maximum supported value is 64 and the
123 minimum value which makes sense is 2.
125 This is purely to save memory - each supported CPU adds
126 approximately sixteen kilobytes to the kernel image.
129 bool "Support for hot-pluggable CPUs"
134 Say Y here to be able to turn CPUs off and on. CPUs
135 can be controlled through /sys/devices/system/cpu/cpu#.
136 Say N if you want to disable CPU hotplug.
139 bool "IEEE FPU emulation"
142 This option is required for IEEE compliant floating point arithmetic
143 on older S/390 machines. Say Y unless you know your machine doesn't
147 bool "Kernel support for 31 bit emulation"
149 select COMPAT_BINFMT_ELF
151 Select this option if you want to enable your system kernel to
152 handle system-calls from ELF binaries for 31 bit ESA. This option
153 (and some other stuff like libraries and such) is needed for
154 executing 31 bit applications. It is safe to say "Y".
156 config SYSVIPC_COMPAT
158 depends on COMPAT && SYSVIPC
165 config S390_SWITCH_AMODE
166 bool "Switch kernel/user addressing modes"
168 This option allows to switch the addressing modes of kernel and user
169 space. The kernel parameter switch_amode=on will enable this feature,
170 default is disabled. Enabling this (via kernel parameter) on machines
171 earlier than IBM System z9-109 EC/BC will reduce system performance.
173 Note that this option will also be selected by selecting the execute
174 protection option below. Enabling the execute protection via the
175 noexec kernel parameter will also switch the addressing modes,
176 independent of the switch_amode kernel parameter.
179 config S390_EXEC_PROTECT
180 bool "Data execute protection"
181 select S390_SWITCH_AMODE
183 This option allows to enable a buffer overflow protection for user
184 space programs and it also selects the addressing mode option above.
185 The kernel parameter noexec=on will enable this feature and also
186 switch the addressing modes, default is disabled. Enabling this (via
187 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
188 will reduce system performance.
190 comment "Code generation options"
193 prompt "Processor type"
197 bool "S/390 model G5 and G6"
200 Select this to build a 31 bit kernel that works
201 on all S/390 and zSeries machines.
204 bool "IBM eServer zSeries model z800 and z900"
206 Select this to optimize for zSeries machines. This
207 will enable some optimizations that are not available
208 on older 31 bit only CPUs.
211 bool "IBM eServer zSeries model z890 and z990"
213 Select this enable optimizations for model z890/z990.
214 This will be slightly faster but does not work on
215 older machines such as the z900.
220 Select this to enable optimizations for IBM System z9-109, IBM
221 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
222 Class (z9 BC). The kernel will be slightly faster but will not
223 work on older machines such as the z990, z890, z900, and z800.
228 bool "Pack kernel stack"
230 This option enables the compiler option -mkernel-backchain if it
231 is available. If the option is available the compiler supports
232 the new stack layout which dramatically reduces the minimum stack
233 frame size. With an old compiler a non-leaf function needs a
234 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
235 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
236 and 24 byte on 64 bit.
238 Say Y if you are unsure.
241 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
242 depends on PACK_STACK && !LOCKDEP
244 If you say Y here and the compiler supports the -mkernel-backchain
245 option the kernel will use a smaller kernel stack size. For 31 bit
246 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
247 instead of 16kb. This allows to run more thread on a system and
248 reduces the pressure on the memory management for higher order
251 Say N if you are unsure.
255 bool "Detect kernel stack overflow"
257 This option enables the compiler option -mstack-guard and
258 -mstack-size if they are available. If the compiler supports them
259 it will emit additional code to each function prolog to trigger
260 an illegal operation if the kernel stack is about to overflow.
262 Say N if you are unsure.
265 int "Size of the guard area (128-1024)"
267 depends on CHECK_STACK
270 This allows you to specify the size of the guard area at the lower
271 end of the kernel stack. If the kernel stack points into the guard
272 area on function entry an illegal operation is triggered. The size
273 needs to be a power of 2. Please keep in mind that the size of an
274 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
275 The minimum size for the stack guard should be 256 for 31 bit and
279 bool "Emit compiler warnings for function with broken stack usage"
281 This option enables the compiler options -mwarn-framesize and
282 -mwarn-dynamicstack. If the compiler supports these options it
283 will generate warnings for function which either use alloca or
284 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
286 Say N if you are unsure.
288 config WARN_STACK_SIZE
289 int "Maximum frame size considered safe (128-2048)"
291 depends on WARN_STACK
294 This allows you to specify the maximum frame size a function may
295 have without the compiler complaining about it.
297 config ARCH_POPULATES_NODE_MAP
300 comment "Kernel preemption"
302 source "kernel/Kconfig.preempt"
304 config ARCH_SPARSEMEM_ENABLE
306 select SPARSEMEM_VMEMMAP_ENABLE
307 select SPARSEMEM_VMEMMAP
308 select SPARSEMEM_STATIC if !64BIT
310 config ARCH_SPARSEMEM_DEFAULT
313 config ARCH_SELECT_MEMORY_MODEL
316 config ARCH_ENABLE_MEMORY_HOTPLUG
320 config ARCH_ENABLE_MEMORY_HOTREMOVE
325 comment "I/O subsystem configuration"
327 config MACHCHK_WARNING
328 bool "Process warning machine checks"
330 Select this option if you want the machine check handler on IBM S/390 or
331 zSeries to process warning machine checks (e.g. on power failures).
335 tristate "QDIO support"
337 This driver provides the Queued Direct I/O base support for
340 To compile this driver as a module, choose M here: the
341 module will be called qdio.
346 bool "Extended debugging information"
349 Say Y here to get extended debugging output in
350 /sys/kernel/debug/s390dbf/qdio...
351 Warning: this option reduces the performance of the QDIO module.
356 tristate "Support for CHSC subchannels"
358 This driver allows usage of CHSC subchannels. A CHSC subchannel
359 is usually present on LPAR only.
360 The driver creates a device /dev/chsc, which may be used to
361 obtain I/O configuration information about the machine and
362 to issue asynchronous chsc commands (DANGEROUS).
363 You will usually only want to use this interface on a special
364 LPAR designated for system management.
366 To compile this driver as a module, choose M here: the
367 module will be called chsc_sch.
374 bool "Builtin IPL record support"
376 If you want to use the produced kernel to IPL directly from a
377 device, you have to merge a bootsector specific to the device
378 into the first bytes of the kernel. You will have to select the
382 prompt "IPL method generated into head.S"
386 Select "tape" if you want to IPL the image from a Tape.
388 Select "vm_reader" if you are running under VM/ESA and want
389 to IPL the image from the emulated card reader.
399 source "fs/Kconfig.binfmt"
401 config FORCE_MAX_ZONEORDER
406 bool "Show crashed user process info"
408 Say Y to print all process fault locations to the console. This is
409 a debugging option; you probably do not want to set it unless you
410 are an S390 port maintainer.
413 bool "Pseudo page fault support"
415 Select this option, if you want to use PFAULT pseudo page fault
416 handling under VM. If running native or in LPAR, this option
417 has no effect. If your VM does not support PFAULT, PAGEEX
418 pseudo page fault handling will be used.
419 Note that VM 4.2 supports PFAULT but has a bug in its
420 implementation that causes some problems.
421 Everybody who wants to run Linux under VM != VM4.2 should select
425 bool "VM shared kernel support"
427 Select this option, if you want to share the text segment of the
428 Linux kernel between different VM guests. This reduces memory
429 usage with lots of guests but greatly increases kernel size.
430 Also if a kernel was IPL'ed from a shared segment the kexec system
432 You should only select this option if you know what you are
433 doing and want to exploit this feature.
436 tristate "Cooperative memory management"
438 Select this option, if you want to enable the kernel interface
439 to reduce the memory size of the system. This is accomplished
440 by allocating pages of memory and put them "on hold". This only
441 makes sense for a system running under VM where the unused pages
442 will be reused by VM for other guest systems. The interface
443 allows an external monitor to balance memory of many systems.
444 Everybody who wants to run Linux under VM should select this
448 bool "/proc interface to cooperative memory management"
451 Select this option to enable the /proc interface to the
452 cooperative memory management.
455 bool "IUCV special message interface to cooperative memory management"
456 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
458 Select this option to enable the special message interface to
459 the cooperative memory management.
462 bool "Unused page notification"
464 This enables the notification of unused pages to the
465 hypervisor. The ESSA instruction is used to do the states
466 changes between a page that has content and the unused state.
469 bool "Virtual CPU timer support"
471 This provides a kernel interface for virtual CPU timers.
474 config VIRT_CPU_ACCOUNTING
475 bool "Base user process accounting on virtual cpu timer"
476 depends on VIRT_TIMER
478 Select this option to use CPU timer deltas to do user
482 bool "Linux - VM Monitor Stream, base infrastructure"
483 depends on PROC_FS && VIRT_TIMER=y
485 This provides a kernel interface for creating and updating z/VM APPLDATA
486 monitor records. The monitor records are updated at certain time
487 intervals, once the timer is started.
488 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
489 i.e. enables or disables monitoring on the Linux side.
490 A custom interval value (in seconds) can be written to
491 /proc/appldata/interval.
493 Defaults are 60 seconds interval and timer off.
494 The /proc entries can also be read from, showing the current settings.
497 tristate "Monitor memory management statistics"
498 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
500 This provides memory management related data to the Linux - VM Monitor
501 Stream, like paging/swapping rate, memory utilisation, etc.
502 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
503 APPLDATA monitor record, i.e. enables or disables monitoring this record
507 The /proc entry can also be read from, showing the current settings.
509 This can also be compiled as a module, which will be called
513 tristate "Monitor OS statistics"
514 depends on APPLDATA_BASE
516 This provides OS related data to the Linux - VM Monitor Stream, like
517 CPU utilisation, etc.
518 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
519 APPLDATA monitor record, i.e. enables or disables monitoring this record
523 This can also be compiled as a module, which will be called
526 config APPLDATA_NET_SUM
527 tristate "Monitor overall network statistics"
528 depends on APPLDATA_BASE
530 This provides network related data to the Linux - VM Monitor Stream,
531 currently there is only a total sum of network I/O statistics, no
533 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
534 APPLDATA monitor record, i.e. enables or disables monitoring this record
538 This can also be compiled as a module, which will be called
541 source kernel/Kconfig.hz
544 bool "s390 hypervisor file system support"
545 select SYS_HYPERVISOR
548 This is a virtual file system intended to provide accounting
549 information in an s390 hypervisor environment.
552 bool "kexec system call"
554 kexec is a system call that implements the ability to shutdown your
555 current kernel, and to start another kernel. It is like a reboot
556 but is independent of hardware/microcode support.
559 tristate "zfcpdump support"
563 Select this option if you want to build an zfcpdump enabled kernel.
564 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
567 bool "s390 guest support (EXPERIMENTAL)"
568 depends on 64BIT && EXPERIMENTAL
571 select VIRTIO_CONSOLE
573 Select this option if you want to run the kernel under s390 linux
584 source "drivers/Kconfig"
588 source "arch/s390/Kconfig.debug"
590 source "security/Kconfig"
592 source "crypto/Kconfig"
596 source "arch/s390/kvm/Kconfig"