1config MMU 2 def_bool y 3 4config ZONE_DMA 5 def_bool y 6 7config LOCKDEP_SUPPORT 8 def_bool y 9 10config STACKTRACE_SUPPORT 11 def_bool y 12 13config HAVE_LATENCYTOP_SUPPORT 14 def_bool y 15 16config RWSEM_GENERIC_SPINLOCK 17 bool 18 19config RWSEM_XCHGADD_ALGORITHM 20 def_bool y 21 22config ARCH_HAS_ILOG2_U32 23 def_bool n 24 25config ARCH_HAS_ILOG2_U64 26 def_bool n 27 28config GENERIC_HWEIGHT 29 def_bool y 30 31config GENERIC_TIME_VSYSCALL 32 def_bool y 33 34config GENERIC_CLOCKEVENTS 35 def_bool y 36 37config GENERIC_BUG 38 def_bool y if BUG 39 40config GENERIC_BUG_RELATIVE_POINTERS 41 def_bool y 42 43config NO_IOMEM 44 def_bool y 45 46config NO_DMA 47 def_bool y 48 49config ARCH_DMA_ADDR_T_64BIT 50 def_bool 64BIT 51 52config GENERIC_LOCKBREAK 53 def_bool y if SMP && PREEMPT 54 55config PGSTE 56 def_bool y if KVM 57 58config VIRT_CPU_ACCOUNTING 59 def_bool y 60 61config ARCH_SUPPORTS_DEBUG_PAGEALLOC 62 def_bool y 63 64config S390 65 def_bool y 66 select USE_GENERIC_SMP_HELPERS if SMP 67 select HAVE_SYSCALL_WRAPPERS 68 select HAVE_FUNCTION_TRACER 69 select HAVE_FUNCTION_TRACE_MCOUNT_TEST 70 select HAVE_FTRACE_MCOUNT_RECORD 71 select HAVE_C_RECORDMCOUNT 72 select HAVE_SYSCALL_TRACEPOINTS 73 select HAVE_DYNAMIC_FTRACE 74 select HAVE_FUNCTION_GRAPH_TRACER 75 select HAVE_REGS_AND_STACK_ACCESS_API 76 select HAVE_OPROFILE 77 select HAVE_KPROBES 78 select HAVE_KRETPROBES 79 select HAVE_KVM if 64BIT 80 select HAVE_ARCH_TRACEHOOK 81 select INIT_ALL_POSSIBLE 82 select HAVE_IRQ_WORK 83 select HAVE_PERF_EVENTS 84 select ARCH_HAVE_NMI_SAFE_CMPXCHG 85 select HAVE_KERNEL_GZIP 86 select HAVE_KERNEL_BZIP2 87 select HAVE_KERNEL_LZMA 88 select HAVE_KERNEL_LZO 89 select HAVE_KERNEL_XZ 90 select HAVE_ARCH_MUTEX_CPU_RELAX 91 select HAVE_ARCH_JUMP_LABEL if !MARCH_G5 92 select HAVE_RCU_TABLE_FREE if SMP 93 select ARCH_SAVE_PAGE_KEYS if HIBERNATION 94 select HAVE_MEMBLOCK 95 select HAVE_MEMBLOCK_NODE_MAP 96 select ARCH_DISCARD_MEMBLOCK 97 select ARCH_INLINE_SPIN_TRYLOCK 98 select ARCH_INLINE_SPIN_TRYLOCK_BH 99 select ARCH_INLINE_SPIN_LOCK 100 select ARCH_INLINE_SPIN_LOCK_BH 101 select ARCH_INLINE_SPIN_LOCK_IRQ 102 select ARCH_INLINE_SPIN_LOCK_IRQSAVE 103 select ARCH_INLINE_SPIN_UNLOCK 104 select ARCH_INLINE_SPIN_UNLOCK_BH 105 select ARCH_INLINE_SPIN_UNLOCK_IRQ 106 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE 107 select ARCH_INLINE_READ_TRYLOCK 108 select ARCH_INLINE_READ_LOCK 109 select ARCH_INLINE_READ_LOCK_BH 110 select ARCH_INLINE_READ_LOCK_IRQ 111 select ARCH_INLINE_READ_LOCK_IRQSAVE 112 select ARCH_INLINE_READ_UNLOCK 113 select ARCH_INLINE_READ_UNLOCK_BH 114 select ARCH_INLINE_READ_UNLOCK_IRQ 115 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE 116 select ARCH_INLINE_WRITE_TRYLOCK 117 select ARCH_INLINE_WRITE_LOCK 118 select ARCH_INLINE_WRITE_LOCK_BH 119 select ARCH_INLINE_WRITE_LOCK_IRQ 120 select ARCH_INLINE_WRITE_LOCK_IRQSAVE 121 select ARCH_INLINE_WRITE_UNLOCK 122 select ARCH_INLINE_WRITE_UNLOCK_BH 123 select ARCH_INLINE_WRITE_UNLOCK_IRQ 124 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE 125 126config SCHED_OMIT_FRAME_POINTER 127 def_bool y 128 129source "init/Kconfig" 130 131source "kernel/Kconfig.freezer" 132 133menu "Base setup" 134 135comment "Processor type and features" 136 137source "kernel/time/Kconfig" 138 139config 64BIT 140 def_bool y 141 prompt "64 bit kernel" 142 help 143 Select this option if you have an IBM z/Architecture machine 144 and want to use the 64 bit addressing mode. 145 146config 32BIT 147 def_bool y if !64BIT 148 149config KTIME_SCALAR 150 def_bool 32BIT 151 152config SMP 153 def_bool y 154 prompt "Symmetric multi-processing support" 155 ---help--- 156 This enables support for systems with more than one CPU. If you have 157 a system with only one CPU, like most personal computers, say N. If 158 you have a system with more than one CPU, say Y. 159 160 If you say N here, the kernel will run on single and multiprocessor 161 machines, but will use only one CPU of a multiprocessor machine. If 162 you say Y here, the kernel will run on many, but not all, 163 singleprocessor machines. On a singleprocessor machine, the kernel 164 will run faster if you say N here. 165 166 See also the SMP-HOWTO available at 167 <http://www.tldp.org/docs.html#howto>. 168 169 Even if you don't know what to do here, say Y. 170 171config NR_CPUS 172 int "Maximum number of CPUs (2-64)" 173 range 2 64 174 depends on SMP 175 default "32" if !64BIT 176 default "64" if 64BIT 177 help 178 This allows you to specify the maximum number of CPUs which this 179 kernel will support. The maximum supported value is 64 and the 180 minimum value which makes sense is 2. 181 182 This is purely to save memory - each supported CPU adds 183 approximately sixteen kilobytes to the kernel image. 184 185config HOTPLUG_CPU 186 def_bool y 187 prompt "Support for hot-pluggable CPUs" 188 depends on SMP 189 select HOTPLUG 190 help 191 Say Y here to be able to turn CPUs off and on. CPUs 192 can be controlled through /sys/devices/system/cpu/cpu#. 193 Say N if you want to disable CPU hotplug. 194 195config SCHED_MC 196 def_bool n 197 198config SCHED_BOOK 199 def_bool y 200 prompt "Book scheduler support" 201 depends on SMP 202 select SCHED_MC 203 help 204 Book scheduler support improves the CPU scheduler's decision making 205 when dealing with machines that have several books. 206 207config MATHEMU 208 def_bool y 209 prompt "IEEE FPU emulation" 210 depends on MARCH_G5 211 help 212 This option is required for IEEE compliant floating point arithmetic 213 on older ESA/390 machines. Say Y unless you know your machine doesn't 214 need this. 215 216config COMPAT 217 def_bool y 218 prompt "Kernel support for 31 bit emulation" 219 depends on 64BIT 220 select COMPAT_BINFMT_ELF 221 help 222 Select this option if you want to enable your system kernel to 223 handle system-calls from ELF binaries for 31 bit ESA. This option 224 (and some other stuff like libraries and such) is needed for 225 executing 31 bit applications. It is safe to say "Y". 226 227config SYSVIPC_COMPAT 228 def_bool y if COMPAT && SYSVIPC 229 230config AUDIT_ARCH 231 def_bool y 232 233comment "Code generation options" 234 235choice 236 prompt "Processor type" 237 default MARCH_G5 238 239config MARCH_G5 240 bool "System/390 model G5 and G6" 241 depends on !64BIT 242 help 243 Select this to build a 31 bit kernel that works 244 on all ESA/390 and z/Architecture machines. 245 246config MARCH_Z900 247 bool "IBM zSeries model z800 and z900" 248 help 249 Select this to enable optimizations for model z800/z900 (2064 and 250 2066 series). This will enable some optimizations that are not 251 available on older ESA/390 (31 Bit) only CPUs. 252 253config MARCH_Z990 254 bool "IBM zSeries model z890 and z990" 255 help 256 Select this to enable optimizations for model z890/z990 (2084 and 257 2086 series). The kernel will be slightly faster but will not work 258 on older machines. 259 260config MARCH_Z9_109 261 bool "IBM System z9" 262 help 263 Select this to enable optimizations for IBM System z9 (2094 and 264 2096 series). The kernel will be slightly faster but will not work 265 on older machines. 266 267config MARCH_Z10 268 bool "IBM System z10" 269 help 270 Select this to enable optimizations for IBM System z10 (2097 and 271 2098 series). The kernel will be slightly faster but will not work 272 on older machines. 273 274config MARCH_Z196 275 bool "IBM zEnterprise 114 and 196" 276 help 277 Select this to enable optimizations for IBM zEnterprise 114 and 196 278 (2818 and 2817 series). The kernel will be slightly faster but will 279 not work on older machines. 280 281endchoice 282 283config PACK_STACK 284 def_bool y 285 prompt "Pack kernel stack" 286 help 287 This option enables the compiler option -mkernel-backchain if it 288 is available. If the option is available the compiler supports 289 the new stack layout which dramatically reduces the minimum stack 290 frame size. With an old compiler a non-leaf function needs a 291 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With 292 -mkernel-backchain the minimum size drops to 16 byte on 31 bit 293 and 24 byte on 64 bit. 294 295 Say Y if you are unsure. 296 297config SMALL_STACK 298 def_bool n 299 prompt "Use 8kb for kernel stack instead of 16kb" 300 depends on PACK_STACK && 64BIT && !LOCKDEP 301 help 302 If you say Y here and the compiler supports the -mkernel-backchain 303 option the kernel will use a smaller kernel stack size. The reduced 304 size is 8kb instead of 16kb. This allows to run more threads on a 305 system and reduces the pressure on the memory management for higher 306 order page allocations. 307 308 Say N if you are unsure. 309 310config CHECK_STACK 311 def_bool y 312 prompt "Detect kernel stack overflow" 313 help 314 This option enables the compiler option -mstack-guard and 315 -mstack-size if they are available. If the compiler supports them 316 it will emit additional code to each function prolog to trigger 317 an illegal operation if the kernel stack is about to overflow. 318 319 Say N if you are unsure. 320 321config STACK_GUARD 322 int "Size of the guard area (128-1024)" 323 range 128 1024 324 depends on CHECK_STACK 325 default "256" 326 help 327 This allows you to specify the size of the guard area at the lower 328 end of the kernel stack. If the kernel stack points into the guard 329 area on function entry an illegal operation is triggered. The size 330 needs to be a power of 2. Please keep in mind that the size of an 331 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit. 332 The minimum size for the stack guard should be 256 for 31 bit and 333 512 for 64 bit. 334 335config WARN_DYNAMIC_STACK 336 def_bool n 337 prompt "Emit compiler warnings for function with dynamic stack usage" 338 help 339 This option enables the compiler option -mwarn-dynamicstack. If the 340 compiler supports this options generates warnings for functions 341 that dynamically allocate stack space using alloca. 342 343 Say N if you are unsure. 344 345comment "Kernel preemption" 346 347source "kernel/Kconfig.preempt" 348 349config ARCH_SPARSEMEM_ENABLE 350 def_bool y 351 select SPARSEMEM_VMEMMAP_ENABLE 352 select SPARSEMEM_VMEMMAP 353 select SPARSEMEM_STATIC if !64BIT 354 355config ARCH_SPARSEMEM_DEFAULT 356 def_bool y 357 358config ARCH_SELECT_MEMORY_MODEL 359 def_bool y 360 361config ARCH_ENABLE_MEMORY_HOTPLUG 362 def_bool y if SPARSEMEM 363 364config ARCH_ENABLE_MEMORY_HOTREMOVE 365 def_bool y 366 367config ARCH_HIBERNATION_POSSIBLE 368 def_bool y if 64BIT 369 370source "mm/Kconfig" 371 372comment "I/O subsystem configuration" 373 374config QDIO 375 def_tristate y 376 prompt "QDIO support" 377 ---help--- 378 This driver provides the Queued Direct I/O base support for 379 IBM System z. 380 381 To compile this driver as a module, choose M here: the 382 module will be called qdio. 383 384 If unsure, say Y. 385 386config CHSC_SCH 387 def_tristate m 388 prompt "Support for CHSC subchannels" 389 help 390 This driver allows usage of CHSC subchannels. A CHSC subchannel 391 is usually present on LPAR only. 392 The driver creates a device /dev/chsc, which may be used to 393 obtain I/O configuration information about the machine and 394 to issue asynchronous chsc commands (DANGEROUS). 395 You will usually only want to use this interface on a special 396 LPAR designated for system management. 397 398 To compile this driver as a module, choose M here: the 399 module will be called chsc_sch. 400 401 If unsure, say N. 402 403comment "Misc" 404 405config IPL 406 def_bool y 407 prompt "Builtin IPL record support" 408 help 409 If you want to use the produced kernel to IPL directly from a 410 device, you have to merge a bootsector specific to the device 411 into the first bytes of the kernel. You will have to select the 412 IPL device. 413 414choice 415 prompt "IPL method generated into head.S" 416 depends on IPL 417 default IPL_VM 418 help 419 Select "tape" if you want to IPL the image from a Tape. 420 421 Select "vm_reader" if you are running under VM/ESA and want 422 to IPL the image from the emulated card reader. 423 424config IPL_TAPE 425 bool "tape" 426 427config IPL_VM 428 bool "vm_reader" 429 430endchoice 431 432source "fs/Kconfig.binfmt" 433 434config FORCE_MAX_ZONEORDER 435 int 436 default "9" 437 438config PFAULT 439 def_bool y 440 prompt "Pseudo page fault support" 441 help 442 Select this option, if you want to use PFAULT pseudo page fault 443 handling under VM. If running native or in LPAR, this option 444 has no effect. If your VM does not support PFAULT, PAGEEX 445 pseudo page fault handling will be used. 446 Note that VM 4.2 supports PFAULT but has a bug in its 447 implementation that causes some problems. 448 Everybody who wants to run Linux under VM != VM4.2 should select 449 this option. 450 451config SHARED_KERNEL 452 def_bool y 453 prompt "VM shared kernel support" 454 help 455 Select this option, if you want to share the text segment of the 456 Linux kernel between different VM guests. This reduces memory 457 usage with lots of guests but greatly increases kernel size. 458 Also if a kernel was IPL'ed from a shared segment the kexec system 459 call will not work. 460 You should only select this option if you know what you are 461 doing and want to exploit this feature. 462 463config CMM 464 def_tristate n 465 prompt "Cooperative memory management" 466 help 467 Select this option, if you want to enable the kernel interface 468 to reduce the memory size of the system. This is accomplished 469 by allocating pages of memory and put them "on hold". This only 470 makes sense for a system running under VM where the unused pages 471 will be reused by VM for other guest systems. The interface 472 allows an external monitor to balance memory of many systems. 473 Everybody who wants to run Linux under VM should select this 474 option. 475 476config CMM_IUCV 477 def_bool y 478 prompt "IUCV special message interface to cooperative memory management" 479 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV) 480 help 481 Select this option to enable the special message interface to 482 the cooperative memory management. 483 484config APPLDATA_BASE 485 def_bool n 486 prompt "Linux - VM Monitor Stream, base infrastructure" 487 depends on PROC_FS 488 help 489 This provides a kernel interface for creating and updating z/VM APPLDATA 490 monitor records. The monitor records are updated at certain time 491 intervals, once the timer is started. 492 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer, 493 i.e. enables or disables monitoring on the Linux side. 494 A custom interval value (in seconds) can be written to 495 /proc/appldata/interval. 496 497 Defaults are 60 seconds interval and timer off. 498 The /proc entries can also be read from, showing the current settings. 499 500config APPLDATA_MEM 501 def_tristate m 502 prompt "Monitor memory management statistics" 503 depends on APPLDATA_BASE && VM_EVENT_COUNTERS 504 help 505 This provides memory management related data to the Linux - VM Monitor 506 Stream, like paging/swapping rate, memory utilisation, etc. 507 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM 508 APPLDATA monitor record, i.e. enables or disables monitoring this record 509 on the z/VM side. 510 511 Default is disabled. 512 The /proc entry can also be read from, showing the current settings. 513 514 This can also be compiled as a module, which will be called 515 appldata_mem.o. 516 517config APPLDATA_OS 518 def_tristate m 519 prompt "Monitor OS statistics" 520 depends on APPLDATA_BASE 521 help 522 This provides OS related data to the Linux - VM Monitor Stream, like 523 CPU utilisation, etc. 524 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM 525 APPLDATA monitor record, i.e. enables or disables monitoring this record 526 on the z/VM side. 527 528 Default is disabled. 529 This can also be compiled as a module, which will be called 530 appldata_os.o. 531 532config APPLDATA_NET_SUM 533 def_tristate m 534 prompt "Monitor overall network statistics" 535 depends on APPLDATA_BASE && NET 536 help 537 This provides network related data to the Linux - VM Monitor Stream, 538 currently there is only a total sum of network I/O statistics, no 539 per-interface data. 540 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM 541 APPLDATA monitor record, i.e. enables or disables monitoring this record 542 on the z/VM side. 543 544 Default is disabled. 545 This can also be compiled as a module, which will be called 546 appldata_net_sum.o. 547 548source kernel/Kconfig.hz 549 550config S390_HYPFS_FS 551 def_bool y 552 prompt "s390 hypervisor file system support" 553 select SYS_HYPERVISOR 554 help 555 This is a virtual file system intended to provide accounting 556 information in an s390 hypervisor environment. 557 558config KEXEC 559 def_bool n 560 prompt "kexec system call" 561 help 562 kexec is a system call that implements the ability to shutdown your 563 current kernel, and to start another kernel. It is like a reboot 564 but is independent of hardware/microcode support. 565 566config CRASH_DUMP 567 bool "kernel crash dumps" 568 depends on 64BIT 569 select KEXEC 570 help 571 Generate crash dump after being started by kexec. 572 Crash dump kernels are loaded in the main kernel with kexec-tools 573 into a specially reserved region and then later executed after 574 a crash by kdump/kexec. 575 For more details see Documentation/kdump/kdump.txt 576 577config ZFCPDUMP 578 def_bool n 579 prompt "zfcpdump support" 580 select SMP 581 help 582 Select this option if you want to build an zfcpdump enabled kernel. 583 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this. 584 585config S390_GUEST 586 def_bool y 587 prompt "s390 guest support for KVM (EXPERIMENTAL)" 588 depends on 64BIT && EXPERIMENTAL 589 select VIRTUALIZATION 590 select VIRTIO 591 select VIRTIO_RING 592 select VIRTIO_CONSOLE 593 help 594 Select this option if you want to run the kernel as a guest under 595 the KVM hypervisor. This will add detection for KVM as well as a 596 virtio transport. If KVM is detected, the virtio console will be 597 the default console. 598 599config SECCOMP 600 def_bool y 601 prompt "Enable seccomp to safely compute untrusted bytecode" 602 depends on PROC_FS 603 help 604 This kernel feature is useful for number crunching applications 605 that may need to compute untrusted bytecode during their 606 execution. By using pipes or other transports made available to 607 the process as file descriptors supporting the read/write 608 syscalls, it's possible to isolate those applications in 609 their own address space using seccomp. Once seccomp is 610 enabled via /proc/<pid>/seccomp, it cannot be disabled 611 and the task is only allowed to execute a few safe syscalls 612 defined by each seccomp mode. 613 614 If unsure, say Y. 615 616endmenu 617 618menu "Power Management" 619 620source "kernel/power/Kconfig" 621 622endmenu 623 624source "net/Kconfig" 625 626config PCMCIA 627 def_bool n 628 629config CCW 630 def_bool y 631 632source "drivers/Kconfig" 633 634source "fs/Kconfig" 635 636source "arch/s390/Kconfig.debug" 637 638source "security/Kconfig" 639 640source "crypto/Kconfig" 641 642source "lib/Kconfig" 643 644source "arch/s390/kvm/Kconfig" 645