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