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