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 GENERIC_CPU_DEVICES if !SMP 68 select HAVE_SYSCALL_WRAPPERS 69 select HAVE_FUNCTION_TRACER 70 select HAVE_FUNCTION_TRACE_MCOUNT_TEST 71 select HAVE_FTRACE_MCOUNT_RECORD 72 select HAVE_C_RECORDMCOUNT 73 select HAVE_SYSCALL_TRACEPOINTS 74 select HAVE_DYNAMIC_FTRACE 75 select HAVE_FUNCTION_GRAPH_TRACER 76 select HAVE_REGS_AND_STACK_ACCESS_API 77 select HAVE_OPROFILE 78 select HAVE_KPROBES 79 select HAVE_KRETPROBES 80 select HAVE_KVM if 64BIT 81 select HAVE_ARCH_TRACEHOOK 82 select INIT_ALL_POSSIBLE 83 select HAVE_IRQ_WORK 84 select HAVE_PERF_EVENTS 85 select ARCH_HAVE_NMI_SAFE_CMPXCHG 86 select HAVE_KERNEL_GZIP 87 select HAVE_KERNEL_BZIP2 88 select HAVE_KERNEL_LZMA 89 select HAVE_KERNEL_LZO 90 select HAVE_KERNEL_XZ 91 select HAVE_ARCH_MUTEX_CPU_RELAX 92 select HAVE_ARCH_JUMP_LABEL if !MARCH_G5 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 select ARCH_WANT_OLD_COMPAT_IPC 222 help 223 Select this option if you want to enable your system kernel to 224 handle system-calls from ELF binaries for 31 bit ESA. This option 225 (and some other stuff like libraries and such) is needed for 226 executing 31 bit applications. It is safe to say "Y". 227 228config SYSVIPC_COMPAT 229 def_bool y if COMPAT && SYSVIPC 230 231config KEYS_COMPAT 232 def_bool y if COMPAT && KEYS 233 234config AUDIT_ARCH 235 def_bool y 236 237comment "Code generation options" 238 239choice 240 prompt "Processor type" 241 default MARCH_G5 242 243config MARCH_G5 244 bool "System/390 model G5 and G6" 245 depends on !64BIT 246 help 247 Select this to build a 31 bit kernel that works 248 on all ESA/390 and z/Architecture machines. 249 250config MARCH_Z900 251 bool "IBM zSeries model z800 and z900" 252 help 253 Select this to enable optimizations for model z800/z900 (2064 and 254 2066 series). This will enable some optimizations that are not 255 available on older ESA/390 (31 Bit) only CPUs. 256 257config MARCH_Z990 258 bool "IBM zSeries model z890 and z990" 259 help 260 Select this to enable optimizations for model z890/z990 (2084 and 261 2086 series). The kernel will be slightly faster but will not work 262 on older machines. 263 264config MARCH_Z9_109 265 bool "IBM System z9" 266 help 267 Select this to enable optimizations for IBM System z9 (2094 and 268 2096 series). The kernel will be slightly faster but will not work 269 on older machines. 270 271config MARCH_Z10 272 bool "IBM System z10" 273 help 274 Select this to enable optimizations for IBM System z10 (2097 and 275 2098 series). The kernel will be slightly faster but will not work 276 on older machines. 277 278config MARCH_Z196 279 bool "IBM zEnterprise 114 and 196" 280 help 281 Select this to enable optimizations for IBM zEnterprise 114 and 196 282 (2818 and 2817 series). The kernel will be slightly faster but will 283 not work on older machines. 284 285endchoice 286 287config PACK_STACK 288 def_bool y 289 prompt "Pack kernel stack" 290 help 291 This option enables the compiler option -mkernel-backchain if it 292 is available. If the option is available the compiler supports 293 the new stack layout which dramatically reduces the minimum stack 294 frame size. With an old compiler a non-leaf function needs a 295 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With 296 -mkernel-backchain the minimum size drops to 16 byte on 31 bit 297 and 24 byte on 64 bit. 298 299 Say Y if you are unsure. 300 301config SMALL_STACK 302 def_bool n 303 prompt "Use 8kb for kernel stack instead of 16kb" 304 depends on PACK_STACK && 64BIT && !LOCKDEP 305 help 306 If you say Y here and the compiler supports the -mkernel-backchain 307 option the kernel will use a smaller kernel stack size. The reduced 308 size is 8kb instead of 16kb. This allows to run more threads on a 309 system and reduces the pressure on the memory management for higher 310 order page allocations. 311 312 Say N if you are unsure. 313 314config CHECK_STACK 315 def_bool y 316 prompt "Detect kernel stack overflow" 317 help 318 This option enables the compiler option -mstack-guard and 319 -mstack-size if they are available. If the compiler supports them 320 it will emit additional code to each function prolog to trigger 321 an illegal operation if the kernel stack is about to overflow. 322 323 Say N if you are unsure. 324 325config STACK_GUARD 326 int "Size of the guard area (128-1024)" 327 range 128 1024 328 depends on CHECK_STACK 329 default "256" 330 help 331 This allows you to specify the size of the guard area at the lower 332 end of the kernel stack. If the kernel stack points into the guard 333 area on function entry an illegal operation is triggered. The size 334 needs to be a power of 2. Please keep in mind that the size of an 335 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit. 336 The minimum size for the stack guard should be 256 for 31 bit and 337 512 for 64 bit. 338 339config WARN_DYNAMIC_STACK 340 def_bool n 341 prompt "Emit compiler warnings for function with dynamic stack usage" 342 help 343 This option enables the compiler option -mwarn-dynamicstack. If the 344 compiler supports this options generates warnings for functions 345 that dynamically allocate stack space using alloca. 346 347 Say N if you are unsure. 348 349comment "Kernel preemption" 350 351source "kernel/Kconfig.preempt" 352 353config ARCH_SPARSEMEM_ENABLE 354 def_bool y 355 select SPARSEMEM_VMEMMAP_ENABLE 356 select SPARSEMEM_VMEMMAP 357 select SPARSEMEM_STATIC if !64BIT 358 359config ARCH_SPARSEMEM_DEFAULT 360 def_bool y 361 362config ARCH_SELECT_MEMORY_MODEL 363 def_bool y 364 365config ARCH_ENABLE_MEMORY_HOTPLUG 366 def_bool y if SPARSEMEM 367 368config ARCH_ENABLE_MEMORY_HOTREMOVE 369 def_bool y 370 371config ARCH_HIBERNATION_POSSIBLE 372 def_bool y if 64BIT 373 374source "mm/Kconfig" 375 376comment "I/O subsystem configuration" 377 378config QDIO 379 def_tristate y 380 prompt "QDIO support" 381 ---help--- 382 This driver provides the Queued Direct I/O base support for 383 IBM System z. 384 385 To compile this driver as a module, choose M here: the 386 module will be called qdio. 387 388 If unsure, say Y. 389 390config CHSC_SCH 391 def_tristate m 392 prompt "Support for CHSC subchannels" 393 help 394 This driver allows usage of CHSC subchannels. A CHSC subchannel 395 is usually present on LPAR only. 396 The driver creates a device /dev/chsc, which may be used to 397 obtain I/O configuration information about the machine and 398 to issue asynchronous chsc commands (DANGEROUS). 399 You will usually only want to use this interface on a special 400 LPAR designated for system management. 401 402 To compile this driver as a module, choose M here: the 403 module will be called chsc_sch. 404 405 If unsure, say N. 406 407comment "Misc" 408 409config IPL 410 def_bool y 411 prompt "Builtin IPL record support" 412 help 413 If you want to use the produced kernel to IPL directly from a 414 device, you have to merge a bootsector specific to the device 415 into the first bytes of the kernel. You will have to select the 416 IPL device. 417 418choice 419 prompt "IPL method generated into head.S" 420 depends on IPL 421 default IPL_VM 422 help 423 Select "tape" if you want to IPL the image from a Tape. 424 425 Select "vm_reader" if you are running under VM/ESA and want 426 to IPL the image from the emulated card reader. 427 428config IPL_TAPE 429 bool "tape" 430 431config IPL_VM 432 bool "vm_reader" 433 434endchoice 435 436source "fs/Kconfig.binfmt" 437 438config FORCE_MAX_ZONEORDER 439 int 440 default "9" 441 442config PFAULT 443 def_bool y 444 prompt "Pseudo page fault support" 445 help 446 Select this option, if you want to use PFAULT pseudo page fault 447 handling under VM. If running native or in LPAR, this option 448 has no effect. If your VM does not support PFAULT, PAGEEX 449 pseudo page fault handling will be used. 450 Note that VM 4.2 supports PFAULT but has a bug in its 451 implementation that causes some problems. 452 Everybody who wants to run Linux under VM != VM4.2 should select 453 this option. 454 455config SHARED_KERNEL 456 def_bool y 457 prompt "VM shared kernel support" 458 help 459 Select this option, if you want to share the text segment of the 460 Linux kernel between different VM guests. This reduces memory 461 usage with lots of guests but greatly increases kernel size. 462 Also if a kernel was IPL'ed from a shared segment the kexec system 463 call will not work. 464 You should only select this option if you know what you are 465 doing and want to exploit this feature. 466 467config CMM 468 def_tristate n 469 prompt "Cooperative memory management" 470 help 471 Select this option, if you want to enable the kernel interface 472 to reduce the memory size of the system. This is accomplished 473 by allocating pages of memory and put them "on hold". This only 474 makes sense for a system running under VM where the unused pages 475 will be reused by VM for other guest systems. The interface 476 allows an external monitor to balance memory of many systems. 477 Everybody who wants to run Linux under VM should select this 478 option. 479 480config CMM_IUCV 481 def_bool y 482 prompt "IUCV special message interface to cooperative memory management" 483 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV) 484 help 485 Select this option to enable the special message interface to 486 the cooperative memory management. 487 488config APPLDATA_BASE 489 def_bool n 490 prompt "Linux - VM Monitor Stream, base infrastructure" 491 depends on PROC_FS 492 help 493 This provides a kernel interface for creating and updating z/VM APPLDATA 494 monitor records. The monitor records are updated at certain time 495 intervals, once the timer is started. 496 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer, 497 i.e. enables or disables monitoring on the Linux side. 498 A custom interval value (in seconds) can be written to 499 /proc/appldata/interval. 500 501 Defaults are 60 seconds interval and timer off. 502 The /proc entries can also be read from, showing the current settings. 503 504config APPLDATA_MEM 505 def_tristate m 506 prompt "Monitor memory management statistics" 507 depends on APPLDATA_BASE && VM_EVENT_COUNTERS 508 help 509 This provides memory management related data to the Linux - VM Monitor 510 Stream, like paging/swapping rate, memory utilisation, etc. 511 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM 512 APPLDATA monitor record, i.e. enables or disables monitoring this record 513 on the z/VM side. 514 515 Default is disabled. 516 The /proc entry can also be read from, showing the current settings. 517 518 This can also be compiled as a module, which will be called 519 appldata_mem.o. 520 521config APPLDATA_OS 522 def_tristate m 523 prompt "Monitor OS statistics" 524 depends on APPLDATA_BASE 525 help 526 This provides OS related data to the Linux - VM Monitor Stream, like 527 CPU utilisation, etc. 528 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM 529 APPLDATA monitor record, i.e. enables or disables monitoring this record 530 on the z/VM side. 531 532 Default is disabled. 533 This can also be compiled as a module, which will be called 534 appldata_os.o. 535 536config APPLDATA_NET_SUM 537 def_tristate m 538 prompt "Monitor overall network statistics" 539 depends on APPLDATA_BASE && NET 540 help 541 This provides network related data to the Linux - VM Monitor Stream, 542 currently there is only a total sum of network I/O statistics, no 543 per-interface data. 544 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM 545 APPLDATA monitor record, i.e. enables or disables monitoring this record 546 on the z/VM side. 547 548 Default is disabled. 549 This can also be compiled as a module, which will be called 550 appldata_net_sum.o. 551 552source kernel/Kconfig.hz 553 554config S390_HYPFS_FS 555 def_bool y 556 prompt "s390 hypervisor file system support" 557 select SYS_HYPERVISOR 558 help 559 This is a virtual file system intended to provide accounting 560 information in an s390 hypervisor environment. 561 562config KEXEC 563 def_bool n 564 prompt "kexec system call" 565 help 566 kexec is a system call that implements the ability to shutdown your 567 current kernel, and to start another kernel. It is like a reboot 568 but is independent of hardware/microcode support. 569 570config CRASH_DUMP 571 bool "kernel crash dumps" 572 depends on 64BIT 573 select KEXEC 574 help 575 Generate crash dump after being started by kexec. 576 Crash dump kernels are loaded in the main kernel with kexec-tools 577 into a specially reserved region and then later executed after 578 a crash by kdump/kexec. 579 For more details see Documentation/kdump/kdump.txt 580 581config ZFCPDUMP 582 def_bool n 583 prompt "zfcpdump support" 584 select SMP 585 help 586 Select this option if you want to build an zfcpdump enabled kernel. 587 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this. 588 589config S390_GUEST 590 def_bool y 591 prompt "s390 guest support for KVM (EXPERIMENTAL)" 592 depends on 64BIT && EXPERIMENTAL 593 select VIRTUALIZATION 594 select VIRTIO 595 select VIRTIO_RING 596 select VIRTIO_CONSOLE 597 help 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 601 the default console. 602 603config SECCOMP 604 def_bool y 605 prompt "Enable seccomp to safely compute untrusted bytecode" 606 depends on PROC_FS 607 help 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. 617 618 If unsure, say Y. 619 620endmenu 621 622menu "Power Management" 623 624source "kernel/power/Kconfig" 625 626endmenu 627 628source "net/Kconfig" 629 630config PCMCIA 631 def_bool n 632 633config CCW 634 def_bool y 635 636source "drivers/Kconfig" 637 638source "fs/Kconfig" 639 640source "arch/s390/Kconfig.debug" 641 642source "security/Kconfig" 643 644source "crypto/Kconfig" 645 646source "lib/Kconfig" 647 648source "arch/s390/kvm/Kconfig" 649