1# 2# For a description of the syntax of this configuration file, 3# see Documentation/kbuild/kconfig-language.txt. 4# 5 6config SCHED_MC 7 def_bool y 8 depends on SMP 9 10config MMU 11 def_bool y 12 13config ZONE_DMA 14 def_bool y 15 depends on 64BIT 16 17config LOCKDEP_SUPPORT 18 def_bool y 19 20config STACKTRACE_SUPPORT 21 def_bool y 22 23config HAVE_LATENCYTOP_SUPPORT 24 def_bool y 25 26config RWSEM_GENERIC_SPINLOCK 27 bool 28 29config RWSEM_XCHGADD_ALGORITHM 30 def_bool y 31 32config ARCH_HAS_ILOG2_U32 33 bool 34 default n 35 36config ARCH_HAS_ILOG2_U64 37 bool 38 default n 39 40config GENERIC_HWEIGHT 41 def_bool y 42 43config GENERIC_TIME 44 def_bool y 45 46config GENERIC_CLOCKEVENTS 47 def_bool y 48 49config GENERIC_BUG 50 bool 51 depends on BUG 52 default y 53 54config NO_IOMEM 55 def_bool y 56 57config NO_DMA 58 def_bool y 59 60config GENERIC_LOCKBREAK 61 bool 62 default y 63 depends on SMP && PREEMPT 64 65config PGSTE 66 bool 67 default y if KVM 68 69mainmenu "Linux Kernel Configuration" 70 71config S390 72 def_bool y 73 select HAVE_OPROFILE 74 select HAVE_KPROBES 75 select HAVE_KRETPROBES 76 select HAVE_KVM if 64BIT 77 78source "init/Kconfig" 79 80menu "Base setup" 81 82comment "Processor type and features" 83 84source "kernel/time/Kconfig" 85 86config 64BIT 87 bool "64 bit kernel" 88 help 89 Select this option if you have a 64 bit IBM zSeries machine 90 and want to use the 64 bit addressing mode. 91 92config 32BIT 93 bool 94 default y if !64BIT 95 96config SMP 97 bool "Symmetric multi-processing support" 98 ---help--- 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. 102 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. 108 109 See also the SMP-HOWTO available at 110 <http://www.tldp.org/docs.html#howto>. 111 112 Even if you don't know what to do here, say Y. 113 114config NR_CPUS 115 int "Maximum number of CPUs (2-64)" 116 range 2 64 117 depends on SMP 118 default "32" if !64BIT 119 default "64" if 64BIT 120 help 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. 124 125 This is purely to save memory - each supported CPU adds 126 approximately sixteen kilobytes to the kernel image. 127 128config HOTPLUG_CPU 129 bool "Support for hot-pluggable CPUs" 130 depends on SMP 131 select HOTPLUG 132 default n 133 help 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. 137 138config MATHEMU 139 bool "IEEE FPU emulation" 140 depends on MARCH_G5 141 help 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 144 need this. 145 146config COMPAT 147 bool "Kernel support for 31 bit emulation" 148 depends on 64BIT 149 select COMPAT_BINFMT_ELF 150 help 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". 155 156config SYSVIPC_COMPAT 157 bool 158 depends on COMPAT && SYSVIPC 159 default y 160 161config AUDIT_ARCH 162 bool 163 default y 164 165config S390_SWITCH_AMODE 166 bool "Switch kernel/user addressing modes" 167 help 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. 172 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. 177 178 179config S390_EXEC_PROTECT 180 bool "Data execute protection" 181 select S390_SWITCH_AMODE 182 help 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. 189 190comment "Code generation options" 191 192choice 193 prompt "Processor type" 194 default MARCH_G5 195 196config MARCH_G5 197 bool "S/390 model G5 and G6" 198 depends on !64BIT 199 help 200 Select this to build a 31 bit kernel that works 201 on all S/390 and zSeries machines. 202 203config MARCH_Z900 204 bool "IBM eServer zSeries model z800 and z900" 205 help 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. 209 210config MARCH_Z990 211 bool "IBM eServer zSeries model z890 and z990" 212 help 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. 216 217config MARCH_Z9_109 218 bool "IBM System z9" 219 help 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. 224 225endchoice 226 227config PACK_STACK 228 bool "Pack kernel stack" 229 help 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. 237 238 Say Y if you are unsure. 239 240config SMALL_STACK 241 bool "Use 4kb/8kb for kernel stack instead of 8kb/16kb" 242 depends on PACK_STACK && !LOCKDEP 243 help 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 249 page allocations. 250 251 Say N if you are unsure. 252 253 254config CHECK_STACK 255 bool "Detect kernel stack overflow" 256 help 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. 261 262 Say N if you are unsure. 263 264config STACK_GUARD 265 int "Size of the guard area (128-1024)" 266 range 128 1024 267 depends on CHECK_STACK 268 default "256" 269 help 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 276 512 for 64 bit. 277 278config WARN_STACK 279 bool "Emit compiler warnings for function with broken stack usage" 280 help 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. 285 286 Say N if you are unsure. 287 288config WARN_STACK_SIZE 289 int "Maximum frame size considered safe (128-2048)" 290 range 128 2048 291 depends on WARN_STACK 292 default "2048" 293 help 294 This allows you to specify the maximum frame size a function may 295 have without the compiler complaining about it. 296 297config ARCH_POPULATES_NODE_MAP 298 def_bool y 299 300comment "Kernel preemption" 301 302source "kernel/Kconfig.preempt" 303 304config ARCH_SPARSEMEM_ENABLE 305 def_bool y 306 select SPARSEMEM_VMEMMAP_ENABLE 307 select SPARSEMEM_VMEMMAP 308 select SPARSEMEM_STATIC if !64BIT 309 310config ARCH_SPARSEMEM_DEFAULT 311 def_bool y 312 313config ARCH_SELECT_MEMORY_MODEL 314 def_bool y 315 316config ARCH_ENABLE_MEMORY_HOTPLUG 317 def_bool y 318 depends on SPARSEMEM 319 320config ARCH_ENABLE_MEMORY_HOTREMOVE 321 def_bool y 322 323source "mm/Kconfig" 324 325comment "I/O subsystem configuration" 326 327config MACHCHK_WARNING 328 bool "Process warning machine checks" 329 help 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). 332 If unsure, say "Y". 333 334config QDIO 335 tristate "QDIO support" 336 ---help--- 337 This driver provides the Queued Direct I/O base support for 338 IBM System z. 339 340 To compile this driver as a module, choose M here: the 341 module will be called qdio. 342 343 If unsure, say Y. 344 345config QDIO_DEBUG 346 bool "Extended debugging information" 347 depends on QDIO 348 help 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. 352 353 If unsure, say N. 354 355config CHSC_SCH 356 tristate "Support for CHSC subchannels" 357 help 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. 365 366 To compile this driver as a module, choose M here: the 367 module will be called chsc_sch. 368 369 If unsure, say N. 370 371comment "Misc" 372 373config IPL 374 bool "Builtin IPL record support" 375 help 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 379 IPL device. 380 381choice 382 prompt "IPL method generated into head.S" 383 depends on IPL 384 default IPL_TAPE 385 help 386 Select "tape" if you want to IPL the image from a Tape. 387 388 Select "vm_reader" if you are running under VM/ESA and want 389 to IPL the image from the emulated card reader. 390 391config IPL_TAPE 392 bool "tape" 393 394config IPL_VM 395 bool "vm_reader" 396 397endchoice 398 399source "fs/Kconfig.binfmt" 400 401config FORCE_MAX_ZONEORDER 402 int 403 default "9" 404 405config PROCESS_DEBUG 406 bool "Show crashed user process info" 407 help 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. 411 412config PFAULT 413 bool "Pseudo page fault support" 414 help 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 422 this option. 423 424config SHARED_KERNEL 425 bool "VM shared kernel support" 426 help 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 431 call will not work. 432 You should only select this option if you know what you are 433 doing and want to exploit this feature. 434 435config CMM 436 tristate "Cooperative memory management" 437 help 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 445 option. 446 447config CMM_PROC 448 bool "/proc interface to cooperative memory management" 449 depends on CMM 450 help 451 Select this option to enable the /proc interface to the 452 cooperative memory management. 453 454config CMM_IUCV 455 bool "IUCV special message interface to cooperative memory management" 456 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV) 457 help 458 Select this option to enable the special message interface to 459 the cooperative memory management. 460 461config PAGE_STATES 462 bool "Unused page notification" 463 help 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. 467 468config VIRT_TIMER 469 bool "Virtual CPU timer support" 470 help 471 This provides a kernel interface for virtual CPU timers. 472 Default is disabled. 473 474config VIRT_CPU_ACCOUNTING 475 bool "Base user process accounting on virtual cpu timer" 476 depends on VIRT_TIMER 477 help 478 Select this option to use CPU timer deltas to do user 479 process accounting. 480 481config APPLDATA_BASE 482 bool "Linux - VM Monitor Stream, base infrastructure" 483 depends on PROC_FS && VIRT_TIMER=y 484 help 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. 492 493 Defaults are 60 seconds interval and timer off. 494 The /proc entries can also be read from, showing the current settings. 495 496config APPLDATA_MEM 497 tristate "Monitor memory management statistics" 498 depends on APPLDATA_BASE && VM_EVENT_COUNTERS 499 help 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 504 on the z/VM side. 505 506 Default is disabled. 507 The /proc entry can also be read from, showing the current settings. 508 509 This can also be compiled as a module, which will be called 510 appldata_mem.o. 511 512config APPLDATA_OS 513 tristate "Monitor OS statistics" 514 depends on APPLDATA_BASE 515 help 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 520 on the z/VM side. 521 522 Default is disabled. 523 This can also be compiled as a module, which will be called 524 appldata_os.o. 525 526config APPLDATA_NET_SUM 527 tristate "Monitor overall network statistics" 528 depends on APPLDATA_BASE 529 help 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 532 per-interface data. 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 535 on the z/VM side. 536 537 Default is disabled. 538 This can also be compiled as a module, which will be called 539 appldata_net_sum.o. 540 541source kernel/Kconfig.hz 542 543config S390_HYPFS_FS 544 bool "s390 hypervisor file system support" 545 select SYS_HYPERVISOR 546 default y 547 help 548 This is a virtual file system intended to provide accounting 549 information in an s390 hypervisor environment. 550 551config KEXEC 552 bool "kexec system call" 553 help 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. 557 558config ZFCPDUMP 559 tristate "zfcpdump support" 560 select SMP 561 default n 562 help 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. 565 566config S390_GUEST 567bool "s390 guest support (EXPERIMENTAL)" 568 depends on 64BIT && EXPERIMENTAL 569 select VIRTIO 570 select VIRTIO_RING 571 select VIRTIO_CONSOLE 572 help 573 Select this option if you want to run the kernel under s390 linux 574endmenu 575 576source "net/Kconfig" 577 578config PCMCIA 579 def_bool n 580 581config CCW 582 def_bool y 583 584source "drivers/Kconfig" 585 586source "fs/Kconfig" 587 588source "arch/s390/Kconfig.debug" 589 590source "security/Kconfig" 591 592source "crypto/Kconfig" 593 594source "lib/Kconfig" 595 596source "arch/s390/kvm/Kconfig" 597