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