2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
10 config LOCKDEP_SUPPORT
14 config STACKTRACE_SUPPORT
18 config RWSEM_GENERIC_SPINLOCK
21 config RWSEM_XCHGADD_ALGORITHM
25 config ARCH_HAS_ILOG2_U32
29 config ARCH_HAS_ILOG2_U64
33 config GENERIC_HWEIGHT
37 config GENERIC_CALIBRATE_DELAY
44 mainmenu "Linux Kernel Configuration"
54 comment "Processor type and features"
59 Select this option if you have a 64 bit IBM zSeries machine
60 and want to use the 64 bit addressing mode.
67 bool "Symmetric multi-processing support"
69 This enables support for systems with more than one CPU. If you have
70 a system with only one CPU, like most personal computers, say N. If
71 you have a system with more than one CPU, say Y.
73 If you say N here, the kernel will run on single and multiprocessor
74 machines, but will use only one CPU of a multiprocessor machine. If
75 you say Y here, the kernel will run on many, but not all,
76 singleprocessor machines. On a singleprocessor machine, the kernel
77 will run faster if you say N here.
79 See also the <file:Documentation/smp.txt> and the SMP-HOWTO
80 available at <http://www.tldp.org/docs.html#howto>.
82 Even if you don't know what to do here, say Y.
85 int "Maximum number of CPUs (2-64)"
90 This allows you to specify the maximum number of CPUs which this
91 kernel will support. The maximum supported value is 64 and the
92 minimum value which makes sense is 2.
94 This is purely to save memory - each supported CPU adds
95 approximately sixteen kilobytes to the kernel image.
98 bool "Support for hot-pluggable CPUs"
103 Say Y here to be able to turn CPUs off and on. CPUs
104 can be controlled through /sys/devices/system/cpu/cpu#.
105 Say N if you want to disable CPU hotplug.
107 config DEFAULT_MIGRATION_COST
112 bool "IEEE FPU emulation"
115 This option is required for IEEE compliant floating point arithmetic
116 on older S/390 machines. Say Y unless you know your machine doesn't
120 bool "Kernel support for 31 bit emulation"
123 Select this option if you want to enable your system kernel to
124 handle system-calls from ELF binaries for 31 bit ESA. This option
125 (and some other stuff like libraries and such) is needed for
126 executing 31 bit applications. It is safe to say "Y".
128 config SYSVIPC_COMPAT
130 depends on COMPAT && SYSVIPC
137 config S390_SWITCH_AMODE
138 bool "Switch kernel/user addressing modes"
140 This option allows to switch the addressing modes of kernel and user
141 space. The kernel parameter switch_amode=on will enable this feature,
142 default is disabled. Enabling this (via kernel parameter) on machines
143 earlier than IBM System z9-109 EC/BC will reduce system performance.
145 Note that this option will also be selected by selecting the execute
146 protection option below. Enabling the execute protection via the
147 noexec kernel parameter will also switch the addressing modes,
148 independent of the switch_amode kernel parameter.
151 config S390_EXEC_PROTECT
152 bool "Data execute protection"
153 select S390_SWITCH_AMODE
155 This option allows to enable a buffer overflow protection for user
156 space programs and it also selects the addressing mode option above.
157 The kernel parameter noexec=on will enable this feature and also
158 switch the addressing modes, default is disabled. Enabling this (via
159 kernel parameter) on machines earlier than IBM System z9-109 EC/BC
160 will reduce system performance.
162 comment "Code generation options"
165 prompt "Processor type"
169 bool "S/390 model G5 and G6"
172 Select this to build a 31 bit kernel that works
173 on all S/390 and zSeries machines.
176 bool "IBM eServer zSeries model z800 and z900"
178 Select this to optimize for zSeries machines. This
179 will enable some optimizations that are not available
180 on older 31 bit only CPUs.
183 bool "IBM eServer zSeries model z890 and z990"
185 Select this enable optimizations for model z890/z990.
186 This will be slightly faster but does not work on
187 older machines such as the z900.
192 Select this to enable optimizations for IBM System z9-109, IBM
193 System z9 Enterprise Class (z9 EC), and IBM System z9 Business
194 Class (z9 BC). The kernel will be slightly faster but will not
195 work on older machines such as the z990, z890, z900, and z800.
200 bool "Pack kernel stack"
202 This option enables the compiler option -mkernel-backchain if it
203 is available. If the option is available the compiler supports
204 the new stack layout which dramatically reduces the minimum stack
205 frame size. With an old compiler a non-leaf function needs a
206 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
207 -mkernel-backchain the minimum size drops to 16 byte on 31 bit
208 and 24 byte on 64 bit.
210 Say Y if you are unsure.
213 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb"
214 depends on PACK_STACK && !LOCKDEP
216 If you say Y here and the compiler supports the -mkernel-backchain
217 option the kernel will use a smaller kernel stack size. For 31 bit
218 the reduced size is 4kb instead of 8kb and for 64 bit it is 8kb
219 instead of 16kb. This allows to run more thread on a system and
220 reduces the pressure on the memory management for higher order
223 Say N if you are unsure.
227 bool "Detect kernel stack overflow"
229 This option enables the compiler option -mstack-guard and
230 -mstack-size if they are available. If the compiler supports them
231 it will emit additional code to each function prolog to trigger
232 an illegal operation if the kernel stack is about to overflow.
234 Say N if you are unsure.
237 int "Size of the guard area (128-1024)"
239 depends on CHECK_STACK
242 This allows you to specify the size of the guard area at the lower
243 end of the kernel stack. If the kernel stack points into the guard
244 area on function entry an illegal operation is triggered. The size
245 needs to be a power of 2. Please keep in mind that the size of an
246 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
247 The minimum size for the stack guard should be 256 for 31 bit and
251 bool "Emit compiler warnings for function with broken stack usage"
253 This option enables the compiler options -mwarn-framesize and
254 -mwarn-dynamicstack. If the compiler supports these options it
255 will generate warnings for function which either use alloca or
256 create a stack frame bigger then CONFIG_WARN_STACK_SIZE.
258 Say N if you are unsure.
260 config WARN_STACK_SIZE
261 int "Maximum frame size considered safe (128-2048)"
263 depends on WARN_STACK
266 This allows you to specify the maximum frame size a function may
267 have without the compiler complaining about it.
269 config ARCH_POPULATES_NODE_MAP
277 comment "I/O subsystem configuration"
279 config MACHCHK_WARNING
280 bool "Process warning machine checks"
282 Select this option if you want the machine check handler on IBM S/390 or
283 zSeries to process warning machine checks (e.g. on power failures).
287 tristate "QDIO support"
289 This driver provides the Queued Direct I/O base support for
292 For details please refer to the documentation provided by IBM at
293 <http://www10.software.ibm.com/developerworks/opensource/linux390>
295 To compile this driver as a module, choose M here: the
296 module will be called qdio.
301 bool "Extended debugging information"
304 Say Y here to get extended debugging output in
305 /sys/kernel/debug/s390dbf/qdio...
306 Warning: this option reduces the performance of the QDIO module.
313 bool "Preemptible Kernel"
315 This option reduces the latency of the kernel when reacting to
316 real-time or interactive events by allowing a low priority process to
317 be preempted even if it is in kernel mode executing a system call.
318 This allows applications to run more reliably even when the system is
321 Say N if you are unsure.
324 bool "Builtin IPL record support"
326 If you want to use the produced kernel to IPL directly from a
327 device, you have to merge a bootsector specific to the device
328 into the first bytes of the kernel. You will have to select the
332 prompt "IPL method generated into head.S"
336 Select "tape" if you want to IPL the image from a Tape.
338 Select "vm_reader" if you are running under VM/ESA and want
339 to IPL the image from the emulated card reader.
349 source "fs/Kconfig.binfmt"
352 bool "Show crashed user process info"
354 Say Y to print all process fault locations to the console. This is
355 a debugging option; you probably do not want to set it unless you
356 are an S390 port maintainer.
359 bool "Pseudo page fault support"
361 Select this option, if you want to use PFAULT pseudo page fault
362 handling under VM. If running native or in LPAR, this option
363 has no effect. If your VM does not support PFAULT, PAGEEX
364 pseudo page fault handling will be used.
365 Note that VM 4.2 supports PFAULT but has a bug in its
366 implementation that causes some problems.
367 Everybody who wants to run Linux under VM != VM4.2 should select
371 bool "VM shared kernel support"
373 Select this option, if you want to share the text segment of the
374 Linux kernel between different VM guests. This reduces memory
375 usage with lots of guests but greatly increases kernel size.
376 You should only select this option if you know what you are
377 doing and want to exploit this feature.
380 tristate "Cooperative memory management"
382 Select this option, if you want to enable the kernel interface
383 to reduce the memory size of the system. This is accomplished
384 by allocating pages of memory and put them "on hold". This only
385 makes sense for a system running under VM where the unused pages
386 will be reused by VM for other guest systems. The interface
387 allows an external monitor to balance memory of many systems.
388 Everybody who wants to run Linux under VM should select this
392 bool "/proc interface to cooperative memory management"
395 Select this option to enable the /proc interface to the
396 cooperative memory management.
399 bool "IUCV special message interface to cooperative memory management"
400 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
402 Select this option to enable the special message interface to
403 the cooperative memory management.
406 bool "Virtual CPU timer support"
408 This provides a kernel interface for virtual CPU timers.
411 config VIRT_CPU_ACCOUNTING
412 bool "Base user process accounting on virtual cpu timer"
413 depends on VIRT_TIMER
415 Select this option to use CPU timer deltas to do user
419 bool "Linux - VM Monitor Stream, base infrastructure"
420 depends on PROC_FS && VIRT_TIMER=y
422 This provides a kernel interface for creating and updating z/VM APPLDATA
423 monitor records. The monitor records are updated at certain time
424 intervals, once the timer is started.
425 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
426 i.e. enables or disables monitoring on the Linux side.
427 A custom interval value (in seconds) can be written to
428 /proc/appldata/interval.
430 Defaults are 60 seconds interval and timer off.
431 The /proc entries can also be read from, showing the current settings.
434 tristate "Monitor memory management statistics"
435 depends on APPLDATA_BASE && VM_EVENT_COUNTERS
437 This provides memory management related data to the Linux - VM Monitor
438 Stream, like paging/swapping rate, memory utilisation, etc.
439 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
440 APPLDATA monitor record, i.e. enables or disables monitoring this record
444 The /proc entry can also be read from, showing the current settings.
446 This can also be compiled as a module, which will be called
450 tristate "Monitor OS statistics"
451 depends on APPLDATA_BASE
453 This provides OS related data to the Linux - VM Monitor Stream, like
454 CPU utilisation, etc.
455 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
456 APPLDATA monitor record, i.e. enables or disables monitoring this record
460 This can also be compiled as a module, which will be called
463 config APPLDATA_NET_SUM
464 tristate "Monitor overall network statistics"
465 depends on APPLDATA_BASE
467 This provides network related data to the Linux - VM Monitor Stream,
468 currently there is only a total sum of network I/O statistics, no
470 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
471 APPLDATA monitor record, i.e. enables or disables monitoring this record
475 This can also be compiled as a module, which will be called
479 bool "No HZ timer ticks in idle"
481 Switches the regular HZ timer off when the system is going idle.
482 This helps z/VM to detect that the Linux system is idle. VM can
483 then "swap-out" this guest which reduces memory usage. It also
484 reduces the overhead of idle systems.
486 The HZ timer can be switched on/off via /proc/sys/kernel/hz_timer.
487 hz_timer=0 means HZ timer is disabled. hz_timer=1 means HZ
490 config NO_IDLE_HZ_INIT
491 bool "HZ timer in idle off by default"
492 depends on NO_IDLE_HZ
494 The HZ timer is switched off in idle by default. That means the
495 HZ timer is already disabled at boot time.
498 bool "s390 hypervisor file system support"
499 select SYS_HYPERVISOR
502 This is a virtual file system intended to provide accounting
503 information in an s390 hypervisor environment.
506 bool "kexec system call"
508 kexec is a system call that implements the ability to shutdown your
509 current kernel, and to start another kernel. It is like a reboot
510 but is independent of hardware/microcode support.
520 source "drivers/base/Kconfig"
522 source "drivers/connector/Kconfig"
524 source "drivers/scsi/Kconfig"
526 source "drivers/s390/Kconfig"
528 source "drivers/net/Kconfig"
532 menu "Instrumentation Support"
534 source "arch/s390/oprofile/Kconfig"
537 bool "Kprobes (EXPERIMENTAL)"
538 depends on EXPERIMENTAL && MODULES
540 Kprobes allows you to trap at almost any kernel address and
541 execute a callback function. register_kprobe() establishes
542 a probepoint and specifies the callback. Kprobes is useful
543 for kernel debugging, non-intrusive instrumentation and testing.
544 If in doubt, say "N".
548 source "arch/s390/Kconfig.debug"
550 source "security/Kconfig"
552 source "crypto/Kconfig"