1config MMU 2 def_bool y 3 4config ZONE_DMA 5 def_bool y 6 7config CPU_BIG_ENDIAN 8 def_bool y 9 10config LOCKDEP_SUPPORT 11 def_bool y 12 13config STACKTRACE_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 ARCH_DMA_ADDR_T_64BIT 38 def_bool y 39 40config GENERIC_LOCKBREAK 41 def_bool y if SMP && PREEMPT 42 43config PGSTE 44 def_bool y if KVM 45 46config ARCH_SUPPORTS_DEBUG_PAGEALLOC 47 def_bool y 48 49config KEXEC 50 def_bool y 51 select KEXEC_CORE 52 53config AUDIT_ARCH 54 def_bool y 55 56config NO_IOPORT_MAP 57 def_bool y 58 59config PCI_QUIRKS 60 def_bool n 61 62config ARCH_SUPPORTS_UPROBES 63 def_bool y 64 65config DEBUG_RODATA 66 def_bool y 67 68config S390 69 def_bool y 70 select ARCH_HAS_DEVMEM_IS_ALLOWED 71 select ARCH_HAS_ELF_RANDOMIZE 72 select ARCH_HAS_GCOV_PROFILE_ALL 73 select ARCH_HAS_GIGANTIC_PAGE 74 select ARCH_HAS_KCOV 75 select ARCH_HAS_SG_CHAIN 76 select ARCH_HAS_UBSAN_SANITIZE_ALL 77 select ARCH_HAVE_NMI_SAFE_CMPXCHG 78 select ARCH_INLINE_READ_LOCK 79 select ARCH_INLINE_READ_LOCK_BH 80 select ARCH_INLINE_READ_LOCK_IRQ 81 select ARCH_INLINE_READ_LOCK_IRQSAVE 82 select ARCH_INLINE_READ_TRYLOCK 83 select ARCH_INLINE_READ_UNLOCK 84 select ARCH_INLINE_READ_UNLOCK_BH 85 select ARCH_INLINE_READ_UNLOCK_IRQ 86 select ARCH_INLINE_READ_UNLOCK_IRQRESTORE 87 select ARCH_INLINE_SPIN_LOCK 88 select ARCH_INLINE_SPIN_LOCK_BH 89 select ARCH_INLINE_SPIN_LOCK_IRQ 90 select ARCH_INLINE_SPIN_LOCK_IRQSAVE 91 select ARCH_INLINE_SPIN_TRYLOCK 92 select ARCH_INLINE_SPIN_TRYLOCK_BH 93 select ARCH_INLINE_SPIN_UNLOCK 94 select ARCH_INLINE_SPIN_UNLOCK_BH 95 select ARCH_INLINE_SPIN_UNLOCK_IRQ 96 select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE 97 select ARCH_INLINE_WRITE_LOCK 98 select ARCH_INLINE_WRITE_LOCK_BH 99 select ARCH_INLINE_WRITE_LOCK_IRQ 100 select ARCH_INLINE_WRITE_LOCK_IRQSAVE 101 select ARCH_INLINE_WRITE_TRYLOCK 102 select ARCH_INLINE_WRITE_UNLOCK 103 select ARCH_INLINE_WRITE_UNLOCK_BH 104 select ARCH_INLINE_WRITE_UNLOCK_IRQ 105 select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE 106 select ARCH_SAVE_PAGE_KEYS if HIBERNATION 107 select ARCH_SUPPORTS_ATOMIC_RMW 108 select ARCH_SUPPORTS_NUMA_BALANCING 109 select ARCH_USE_BUILTIN_BSWAP 110 select ARCH_USE_CMPXCHG_LOCKREF 111 select ARCH_WANTS_DYNAMIC_TASK_STRUCT 112 select ARCH_WANTS_PROT_NUMA_PROT_NONE 113 select ARCH_WANTS_UBSAN_NO_NULL 114 select ARCH_WANT_IPC_PARSE_VERSION 115 select BUILDTIME_EXTABLE_SORT 116 select CLONE_BACKWARDS2 117 select DYNAMIC_FTRACE if FUNCTION_TRACER 118 select GENERIC_CLOCKEVENTS 119 select GENERIC_CPU_AUTOPROBE 120 select GENERIC_CPU_DEVICES if !SMP 121 select GENERIC_CPU_VULNERABILITIES 122 select GENERIC_FIND_FIRST_BIT 123 select GENERIC_SMP_IDLE_THREAD 124 select GENERIC_TIME_VSYSCALL 125 select HAVE_ALIGNED_STRUCT_PAGE if SLUB 126 select HAVE_ARCH_AUDITSYSCALL 127 select HAVE_ARCH_EARLY_PFN_TO_NID 128 select HAVE_ARCH_HARDENED_USERCOPY 129 select HAVE_ARCH_JUMP_LABEL 130 select CPU_NO_EFFICIENT_FFS if !HAVE_MARCH_Z9_109_FEATURES 131 select HAVE_ARCH_SECCOMP_FILTER 132 select HAVE_ARCH_SOFT_DIRTY 133 select HAVE_ARCH_TRACEHOOK 134 select HAVE_ARCH_TRANSPARENT_HUGEPAGE 135 select HAVE_EBPF_JIT if PACK_STACK && HAVE_MARCH_Z196_FEATURES 136 select HAVE_CMPXCHG_DOUBLE 137 select HAVE_CMPXCHG_LOCAL 138 select HAVE_DEBUG_KMEMLEAK 139 select HAVE_DMA_API_DEBUG 140 select HAVE_DYNAMIC_FTRACE 141 select HAVE_DYNAMIC_FTRACE_WITH_REGS 142 select HAVE_EFFICIENT_UNALIGNED_ACCESS 143 select HAVE_EXIT_THREAD 144 select HAVE_FTRACE_MCOUNT_RECORD 145 select HAVE_FUNCTION_GRAPH_TRACER 146 select HAVE_FUNCTION_TRACER 147 select HAVE_FUTEX_CMPXCHG if FUTEX 148 select HAVE_KERNEL_BZIP2 149 select HAVE_KERNEL_GZIP 150 select HAVE_KERNEL_LZ4 151 select HAVE_KERNEL_LZMA 152 select HAVE_KERNEL_LZO 153 select HAVE_KERNEL_XZ 154 select HAVE_KPROBES 155 select HAVE_KRETPROBES 156 select HAVE_KVM 157 select HAVE_LIVEPATCH 158 select HAVE_MEMBLOCK 159 select HAVE_MEMBLOCK_NODE_MAP 160 select HAVE_MEMBLOCK_PHYS_MAP 161 select HAVE_MOD_ARCH_SPECIFIC 162 select HAVE_OPROFILE 163 select HAVE_PERF_EVENTS 164 select HAVE_REGS_AND_STACK_ACCESS_API 165 select HAVE_SYSCALL_TRACEPOINTS 166 select HAVE_VIRT_CPU_ACCOUNTING 167 select MODULES_USE_ELF_RELA 168 select NO_BOOTMEM 169 select OLD_SIGACTION 170 select OLD_SIGSUSPEND3 171 select SPARSE_IRQ 172 select SYSCTL_EXCEPTION_TRACE 173 select TTY 174 select VIRT_CPU_ACCOUNTING 175 select VIRT_TO_BUS 176 select HAVE_NMI 177 178 179config SCHED_OMIT_FRAME_POINTER 180 def_bool y 181 182config PGTABLE_LEVELS 183 int 184 default 4 185 186source "init/Kconfig" 187 188source "kernel/Kconfig.freezer" 189 190source "kernel/livepatch/Kconfig" 191 192menu "Processor type and features" 193 194config HAVE_MARCH_Z900_FEATURES 195 def_bool n 196 197config HAVE_MARCH_Z990_FEATURES 198 def_bool n 199 select HAVE_MARCH_Z900_FEATURES 200 201config HAVE_MARCH_Z9_109_FEATURES 202 def_bool n 203 select HAVE_MARCH_Z990_FEATURES 204 205config HAVE_MARCH_Z10_FEATURES 206 def_bool n 207 select HAVE_MARCH_Z9_109_FEATURES 208 209config HAVE_MARCH_Z196_FEATURES 210 def_bool n 211 select HAVE_MARCH_Z10_FEATURES 212 213config HAVE_MARCH_ZEC12_FEATURES 214 def_bool n 215 select HAVE_MARCH_Z196_FEATURES 216 217config HAVE_MARCH_Z13_FEATURES 218 def_bool n 219 select HAVE_MARCH_ZEC12_FEATURES 220 221choice 222 prompt "Processor type" 223 default MARCH_Z196 224 225config MARCH_Z900 226 bool "IBM zSeries model z800 and z900" 227 select HAVE_MARCH_Z900_FEATURES 228 help 229 Select this to enable optimizations for model z800/z900 (2064 and 230 2066 series). This will enable some optimizations that are not 231 available on older ESA/390 (31 Bit) only CPUs. 232 233config MARCH_Z990 234 bool "IBM zSeries model z890 and z990" 235 select HAVE_MARCH_Z990_FEATURES 236 help 237 Select this to enable optimizations for model z890/z990 (2084 and 238 2086 series). The kernel will be slightly faster but will not work 239 on older machines. 240 241config MARCH_Z9_109 242 bool "IBM System z9" 243 select HAVE_MARCH_Z9_109_FEATURES 244 help 245 Select this to enable optimizations for IBM System z9 (2094 and 246 2096 series). The kernel will be slightly faster but will not work 247 on older machines. 248 249config MARCH_Z10 250 bool "IBM System z10" 251 select HAVE_MARCH_Z10_FEATURES 252 help 253 Select this to enable optimizations for IBM System z10 (2097 and 254 2098 series). The kernel will be slightly faster but will not work 255 on older machines. 256 257config MARCH_Z196 258 bool "IBM zEnterprise 114 and 196" 259 select HAVE_MARCH_Z196_FEATURES 260 help 261 Select this to enable optimizations for IBM zEnterprise 114 and 196 262 (2818 and 2817 series). The kernel will be slightly faster but will 263 not work on older machines. 264 265config MARCH_ZEC12 266 bool "IBM zBC12 and zEC12" 267 select HAVE_MARCH_ZEC12_FEATURES 268 help 269 Select this to enable optimizations for IBM zBC12 and zEC12 (2828 and 270 2827 series). The kernel will be slightly faster but will not work on 271 older machines. 272 273config MARCH_Z13 274 bool "IBM z13s and z13" 275 select HAVE_MARCH_Z13_FEATURES 276 help 277 Select this to enable optimizations for IBM z13s and z13 (2965 and 278 2964 series). The kernel will be slightly faster but will not work on 279 older machines. 280 281endchoice 282 283config MARCH_Z900_TUNE 284 def_bool TUNE_Z900 || MARCH_Z900 && TUNE_DEFAULT 285 286config MARCH_Z990_TUNE 287 def_bool TUNE_Z990 || MARCH_Z990 && TUNE_DEFAULT 288 289config MARCH_Z9_109_TUNE 290 def_bool TUNE_Z9_109 || MARCH_Z9_109 && TUNE_DEFAULT 291 292config MARCH_Z10_TUNE 293 def_bool TUNE_Z10 || MARCH_Z10 && TUNE_DEFAULT 294 295config MARCH_Z196_TUNE 296 def_bool TUNE_Z196 || MARCH_Z196 && TUNE_DEFAULT 297 298config MARCH_ZEC12_TUNE 299 def_bool TUNE_ZEC12 || MARCH_ZEC12 && TUNE_DEFAULT 300 301config MARCH_Z13_TUNE 302 def_bool TUNE_Z13 || MARCH_Z13 && TUNE_DEFAULT 303 304choice 305 prompt "Tune code generation" 306 default TUNE_DEFAULT 307 help 308 Cause the compiler to tune (-mtune) the generated code for a machine. 309 This will make the code run faster on the selected machine but 310 somewhat slower on other machines. 311 This option only changes how the compiler emits instructions, not the 312 selection of instructions itself, so the resulting kernel will run on 313 all other machines. 314 315config TUNE_DEFAULT 316 bool "Default" 317 help 318 Tune the generated code for the target processor for which the kernel 319 will be compiled. 320 321config TUNE_Z900 322 bool "IBM zSeries model z800 and z900" 323 324config TUNE_Z990 325 bool "IBM zSeries model z890 and z990" 326 327config TUNE_Z9_109 328 bool "IBM System z9" 329 330config TUNE_Z10 331 bool "IBM System z10" 332 333config TUNE_Z196 334 bool "IBM zEnterprise 114 and 196" 335 336config TUNE_ZEC12 337 bool "IBM zBC12 and zEC12" 338 339config TUNE_Z13 340 bool "IBM z13" 341 342endchoice 343 344config 64BIT 345 def_bool y 346 347config COMPAT 348 def_bool y 349 prompt "Kernel support for 31 bit emulation" 350 select COMPAT_BINFMT_ELF if BINFMT_ELF 351 select ARCH_WANT_OLD_COMPAT_IPC 352 select COMPAT_OLD_SIGACTION 353 depends on MULTIUSER 354 help 355 Select this option if you want to enable your system kernel to 356 handle system-calls from ELF binaries for 31 bit ESA. This option 357 (and some other stuff like libraries and such) is needed for 358 executing 31 bit applications. It is safe to say "Y". 359 360config SYSVIPC_COMPAT 361 def_bool y if COMPAT && SYSVIPC 362 363config SMP 364 def_bool y 365 prompt "Symmetric multi-processing support" 366 ---help--- 367 This enables support for systems with more than one CPU. If you have 368 a system with only one CPU, like most personal computers, say N. If 369 you have a system with more than one CPU, say Y. 370 371 If you say N here, the kernel will run on uni- and multiprocessor 372 machines, but will use only one CPU of a multiprocessor machine. If 373 you say Y here, the kernel will run on many, but not all, 374 uniprocessor machines. On a uniprocessor machine, the kernel 375 will run faster if you say N here. 376 377 See also the SMP-HOWTO available at 378 <http://www.tldp.org/docs.html#howto>. 379 380 Even if you don't know what to do here, say Y. 381 382config NR_CPUS 383 int "Maximum number of CPUs (2-512)" 384 range 2 512 385 depends on SMP 386 default "64" 387 help 388 This allows you to specify the maximum number of CPUs which this 389 kernel will support. The maximum supported value is 512 and the 390 minimum value which makes sense is 2. 391 392 This is purely to save memory - each supported CPU adds 393 approximately sixteen kilobytes to the kernel image. 394 395config HOTPLUG_CPU 396 def_bool y 397 prompt "Support for hot-pluggable CPUs" 398 depends on SMP 399 help 400 Say Y here to be able to turn CPUs off and on. CPUs 401 can be controlled through /sys/devices/system/cpu/cpu#. 402 Say N if you want to disable CPU hotplug. 403 404# Some NUMA nodes have memory ranges that span 405# other nodes. Even though a pfn is valid and 406# between a node's start and end pfns, it may not 407# reside on that node. See memmap_init_zone() 408# for details. <- They meant memory holes! 409config NODES_SPAN_OTHER_NODES 410 def_bool NUMA 411 412config NUMA 413 bool "NUMA support" 414 depends on SMP && SCHED_TOPOLOGY 415 default n 416 help 417 Enable NUMA support 418 419 This option adds NUMA support to the kernel. 420 421 An operation mode can be selected by appending 422 numa=<method> to the kernel command line. 423 424 The default behaviour is identical to appending numa=plain to 425 the command line. This will create just one node with all 426 available memory and all CPUs in it. 427 428config NODES_SHIFT 429 int "Maximum NUMA nodes (as a power of 2)" 430 range 1 10 431 depends on NUMA 432 default "4" 433 help 434 Specify the maximum number of NUMA nodes available on the target 435 system. Increases memory reserved to accommodate various tables. 436 437menu "Select NUMA modes" 438 depends on NUMA 439 440config NUMA_EMU 441 bool "NUMA emulation" 442 default y 443 help 444 Numa emulation mode will split the available system memory into 445 equal chunks which then are distributed over the configured number 446 of nodes in a round-robin manner. 447 448 The number of fake nodes is limited by the number of available memory 449 chunks (i.e. memory size / fake size) and the number of supported 450 nodes in the kernel. 451 452 The CPUs are assigned to the nodes in a way that partially respects 453 the original machine topology (if supported by the machine). 454 Fair distribution of the CPUs is not guaranteed. 455 456config EMU_SIZE 457 hex "NUMA emulation memory chunk size" 458 default 0x10000000 459 range 0x400000 0x100000000 460 depends on NUMA_EMU 461 help 462 Select the default size by which the memory is chopped and then 463 assigned to emulated NUMA nodes. 464 465 This can be overridden by specifying 466 467 emu_size=<n> 468 469 on the kernel command line where also suffixes K, M, G, and T are 470 supported. 471 472endmenu 473 474config SCHED_SMT 475 def_bool n 476 477config SCHED_MC 478 def_bool n 479 480config SCHED_BOOK 481 def_bool n 482 483config SCHED_DRAWER 484 def_bool n 485 486config SCHED_TOPOLOGY 487 def_bool y 488 prompt "Topology scheduler support" 489 depends on SMP 490 select SCHED_SMT 491 select SCHED_MC 492 select SCHED_BOOK 493 select SCHED_DRAWER 494 help 495 Topology scheduler support improves the CPU scheduler's decision 496 making when dealing with machines that have multi-threading, 497 multiple cores or multiple books. 498 499source kernel/Kconfig.preempt 500 501source kernel/Kconfig.hz 502 503endmenu 504 505menu "Memory setup" 506 507config ARCH_SPARSEMEM_ENABLE 508 def_bool y 509 select SPARSEMEM_VMEMMAP_ENABLE 510 select SPARSEMEM_VMEMMAP 511 512config ARCH_SPARSEMEM_DEFAULT 513 def_bool y 514 515config ARCH_SELECT_MEMORY_MODEL 516 def_bool y 517 518config ARCH_ENABLE_MEMORY_HOTPLUG 519 def_bool y if SPARSEMEM 520 521config ARCH_ENABLE_MEMORY_HOTREMOVE 522 def_bool y 523 524config ARCH_ENABLE_SPLIT_PMD_PTLOCK 525 def_bool y 526 527config FORCE_MAX_ZONEORDER 528 int 529 default "9" 530 531source "mm/Kconfig" 532 533config PACK_STACK 534 def_bool y 535 prompt "Pack kernel stack" 536 help 537 This option enables the compiler option -mkernel-backchain if it 538 is available. If the option is available the compiler supports 539 the new stack layout which dramatically reduces the minimum stack 540 frame size. With an old compiler a non-leaf function needs a 541 minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With 542 -mkernel-backchain the minimum size drops to 16 byte on 31 bit 543 and 24 byte on 64 bit. 544 545 Say Y if you are unsure. 546 547config CHECK_STACK 548 def_bool y 549 prompt "Detect kernel stack overflow" 550 help 551 This option enables the compiler option -mstack-guard and 552 -mstack-size if they are available. If the compiler supports them 553 it will emit additional code to each function prolog to trigger 554 an illegal operation if the kernel stack is about to overflow. 555 556 Say N if you are unsure. 557 558config STACK_GUARD 559 int "Size of the guard area (128-1024)" 560 range 128 1024 561 depends on CHECK_STACK 562 default "256" 563 help 564 This allows you to specify the size of the guard area at the lower 565 end of the kernel stack. If the kernel stack points into the guard 566 area on function entry an illegal operation is triggered. The size 567 needs to be a power of 2. Please keep in mind that the size of an 568 interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit. 569 The minimum size for the stack guard should be 256 for 31 bit and 570 512 for 64 bit. 571 572config WARN_DYNAMIC_STACK 573 def_bool n 574 prompt "Emit compiler warnings for function with dynamic stack usage" 575 help 576 This option enables the compiler option -mwarn-dynamicstack. If the 577 compiler supports this options generates warnings for functions 578 that dynamically allocate stack space using alloca. 579 580 Say N if you are unsure. 581 582endmenu 583 584menu "I/O subsystem" 585 586config QDIO 587 def_tristate y 588 prompt "QDIO support" 589 ---help--- 590 This driver provides the Queued Direct I/O base support for 591 IBM System z. 592 593 To compile this driver as a module, choose M here: the 594 module will be called qdio. 595 596 If unsure, say Y. 597 598menuconfig PCI 599 bool "PCI support" 600 select PCI_MSI 601 select IOMMU_SUPPORT 602 help 603 Enable PCI support. 604 605if PCI 606 607config PCI_NR_FUNCTIONS 608 int "Maximum number of PCI functions (1-4096)" 609 range 1 4096 610 default "64" 611 help 612 This allows you to specify the maximum number of PCI functions which 613 this kernel will support. 614 615source "drivers/pci/Kconfig" 616 617endif # PCI 618 619config PCI_DOMAINS 620 def_bool PCI 621 622config HAS_IOMEM 623 def_bool PCI 624 625config IOMMU_HELPER 626 def_bool PCI 627 628config NEED_SG_DMA_LENGTH 629 def_bool PCI 630 631config NEED_DMA_MAP_STATE 632 def_bool PCI 633 634config CHSC_SCH 635 def_tristate m 636 prompt "Support for CHSC subchannels" 637 help 638 This driver allows usage of CHSC subchannels. A CHSC subchannel 639 is usually present on LPAR only. 640 The driver creates a device /dev/chsc, which may be used to 641 obtain I/O configuration information about the machine and 642 to issue asynchronous chsc commands (DANGEROUS). 643 You will usually only want to use this interface on a special 644 LPAR designated for system management. 645 646 To compile this driver as a module, choose M here: the 647 module will be called chsc_sch. 648 649 If unsure, say N. 650 651config SCM_BUS 652 def_bool y 653 prompt "SCM bus driver" 654 help 655 Bus driver for Storage Class Memory. 656 657config EADM_SCH 658 def_tristate m 659 prompt "Support for EADM subchannels" 660 depends on SCM_BUS 661 help 662 This driver allows usage of EADM subchannels. EADM subchannels act 663 as a communication vehicle for SCM increments. 664 665 To compile this driver as a module, choose M here: the 666 module will be called eadm_sch. 667 668endmenu 669 670menu "Dump support" 671 672config CRASH_DUMP 673 bool "kernel crash dumps" 674 depends on SMP 675 select KEXEC 676 help 677 Generate crash dump after being started by kexec. 678 Crash dump kernels are loaded in the main kernel with kexec-tools 679 into a specially reserved region and then later executed after 680 a crash by kdump/kexec. 681 Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this. 682 This option also enables s390 zfcpdump. 683 See also <file:Documentation/s390/zfcpdump.txt> 684 685endmenu 686 687menu "Executable file formats / Emulations" 688 689source "fs/Kconfig.binfmt" 690 691config SECCOMP 692 def_bool y 693 prompt "Enable seccomp to safely compute untrusted bytecode" 694 depends on PROC_FS 695 help 696 This kernel feature is useful for number crunching applications 697 that may need to compute untrusted bytecode during their 698 execution. By using pipes or other transports made available to 699 the process as file descriptors supporting the read/write 700 syscalls, it's possible to isolate those applications in 701 their own address space using seccomp. Once seccomp is 702 enabled via /proc/<pid>/seccomp, it cannot be disabled 703 and the task is only allowed to execute a few safe syscalls 704 defined by each seccomp mode. 705 706 If unsure, say Y. 707 708config KERNEL_NOBP 709 def_bool n 710 prompt "Enable modified branch prediction for the kernel by default" 711 help 712 If this option is selected the kernel will switch to a modified 713 branch prediction mode if the firmware interface is available. 714 The modified branch prediction mode improves the behaviour in 715 regard to speculative execution. 716 717 With the option enabled the kernel parameter "nobp=0" or "nospec" 718 can be used to run the kernel in the normal branch prediction mode. 719 720 With the option disabled the modified branch prediction mode is 721 enabled with the "nobp=1" kernel parameter. 722 723 If unsure, say N. 724 725config EXPOLINE 726 def_bool n 727 prompt "Avoid speculative indirect branches in the kernel" 728 help 729 Compile the kernel with the expoline compiler options to guard 730 against kernel-to-user data leaks by avoiding speculative indirect 731 branches. 732 Requires a compiler with -mindirect-branch=thunk support for full 733 protection. The kernel may run slower. 734 735 If unsure, say N. 736 737choice 738 prompt "Expoline default" 739 depends on EXPOLINE 740 default EXPOLINE_FULL 741 742config EXPOLINE_OFF 743 bool "spectre_v2=off" 744 745config EXPOLINE_AUTO 746 bool "spectre_v2=auto" 747 748config EXPOLINE_FULL 749 bool "spectre_v2=on" 750 751endchoice 752 753endmenu 754 755menu "Power Management" 756 757config ARCH_HIBERNATION_POSSIBLE 758 def_bool y 759 760source "kernel/power/Kconfig" 761 762endmenu 763 764source "net/Kconfig" 765 766config PCMCIA 767 def_bool n 768 769config CCW 770 def_bool y 771 772source "drivers/Kconfig" 773 774source "fs/Kconfig" 775 776source "arch/s390/Kconfig.debug" 777 778source "security/Kconfig" 779 780source "crypto/Kconfig" 781 782source "lib/Kconfig" 783 784menu "Virtualization" 785 786config PFAULT 787 def_bool y 788 prompt "Pseudo page fault support" 789 help 790 Select this option, if you want to use PFAULT pseudo page fault 791 handling under VM. If running native or in LPAR, this option 792 has no effect. If your VM does not support PFAULT, PAGEEX 793 pseudo page fault handling will be used. 794 Note that VM 4.2 supports PFAULT but has a bug in its 795 implementation that causes some problems. 796 Everybody who wants to run Linux under VM != VM4.2 should select 797 this option. 798 799config SHARED_KERNEL 800 bool "VM shared kernel support" 801 depends on !JUMP_LABEL 802 depends on !ALTERNATIVES 803 help 804 Select this option, if you want to share the text segment of the 805 Linux kernel between different VM guests. This reduces memory 806 usage with lots of guests but greatly increases kernel size. 807 Also if a kernel was IPL'ed from a shared segment the kexec system 808 call will not work. 809 You should only select this option if you know what you are 810 doing and want to exploit this feature. 811 812config CMM 813 def_tristate n 814 prompt "Cooperative memory management" 815 help 816 Select this option, if you want to enable the kernel interface 817 to reduce the memory size of the system. This is accomplished 818 by allocating pages of memory and put them "on hold". This only 819 makes sense for a system running under VM where the unused pages 820 will be reused by VM for other guest systems. The interface 821 allows an external monitor to balance memory of many systems. 822 Everybody who wants to run Linux under VM should select this 823 option. 824 825config CMM_IUCV 826 def_bool y 827 prompt "IUCV special message interface to cooperative memory management" 828 depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV) 829 help 830 Select this option to enable the special message interface to 831 the cooperative memory management. 832 833config APPLDATA_BASE 834 def_bool n 835 prompt "Linux - VM Monitor Stream, base infrastructure" 836 depends on PROC_FS 837 help 838 This provides a kernel interface for creating and updating z/VM APPLDATA 839 monitor records. The monitor records are updated at certain time 840 intervals, once the timer is started. 841 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer, 842 i.e. enables or disables monitoring on the Linux side. 843 A custom interval value (in seconds) can be written to 844 /proc/appldata/interval. 845 846 Defaults are 60 seconds interval and timer off. 847 The /proc entries can also be read from, showing the current settings. 848 849config APPLDATA_MEM 850 def_tristate m 851 prompt "Monitor memory management statistics" 852 depends on APPLDATA_BASE && VM_EVENT_COUNTERS 853 help 854 This provides memory management related data to the Linux - VM Monitor 855 Stream, like paging/swapping rate, memory utilisation, etc. 856 Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM 857 APPLDATA monitor record, i.e. enables or disables monitoring this record 858 on the z/VM side. 859 860 Default is disabled. 861 The /proc entry can also be read from, showing the current settings. 862 863 This can also be compiled as a module, which will be called 864 appldata_mem.o. 865 866config APPLDATA_OS 867 def_tristate m 868 prompt "Monitor OS statistics" 869 depends on APPLDATA_BASE 870 help 871 This provides OS related data to the Linux - VM Monitor Stream, like 872 CPU utilisation, etc. 873 Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM 874 APPLDATA monitor record, i.e. enables or disables monitoring this record 875 on the z/VM side. 876 877 Default is disabled. 878 This can also be compiled as a module, which will be called 879 appldata_os.o. 880 881config APPLDATA_NET_SUM 882 def_tristate m 883 prompt "Monitor overall network statistics" 884 depends on APPLDATA_BASE && NET 885 help 886 This provides network related data to the Linux - VM Monitor Stream, 887 currently there is only a total sum of network I/O statistics, no 888 per-interface data. 889 Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM 890 APPLDATA monitor record, i.e. enables or disables monitoring this record 891 on the z/VM side. 892 893 Default is disabled. 894 This can also be compiled as a module, which will be called 895 appldata_net_sum.o. 896 897config S390_HYPFS_FS 898 def_bool y 899 prompt "s390 hypervisor file system support" 900 select SYS_HYPERVISOR 901 help 902 This is a virtual file system intended to provide accounting 903 information in an s390 hypervisor environment. 904 905source "arch/s390/kvm/Kconfig" 906 907config S390_GUEST 908 def_bool y 909 prompt "s390 support for virtio devices" 910 select TTY 911 select VIRTUALIZATION 912 select VIRTIO 913 select VIRTIO_CONSOLE 914 help 915 Enabling this option adds support for virtio based paravirtual device 916 drivers on s390. 917 918 Select this option if you want to run the kernel as a guest under 919 the KVM hypervisor. 920 921config S390_GUEST_OLD_TRANSPORT 922 def_bool y 923 prompt "Guest support for old s390 virtio transport (DEPRECATED)" 924 depends on S390_GUEST 925 help 926 Enable this option to add support for the old s390-virtio 927 transport (i.e. virtio devices NOT based on virtio-ccw). This 928 type of virtio devices is only available on the experimental 929 kuli userspace or with old (< 2.6) qemu. If you are running 930 with a modern version of qemu (which supports virtio-ccw since 931 1.4 and uses it by default since version 2.4), you probably won't 932 need this. 933 934endmenu 935