1# Select 32 or 64 bit 2config 64BIT 3 bool "64-bit kernel" if ARCH = "x86" 4 default ARCH != "i386" 5 ---help--- 6 Say yes to build a 64-bit kernel - formerly known as x86_64 7 Say no to build a 32-bit kernel - formerly known as i386 8 9config X86_32 10 def_bool y 11 depends on !64BIT 12 13config X86_64 14 def_bool y 15 depends on 64BIT 16 17### Arch settings 18config X86 19 def_bool y 20 select ACPI_LEGACY_TABLES_LOOKUP if ACPI 21 select ACPI_SYSTEM_POWER_STATES_SUPPORT if ACPI 22 select ANON_INODES 23 select ARCH_CLOCKSOURCE_DATA 24 select ARCH_DISCARD_MEMBLOCK 25 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE 26 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS 27 select ARCH_HAS_DEVMEM_IS_ALLOWED 28 select ARCH_HAS_ELF_RANDOMIZE 29 select ARCH_HAS_FAST_MULTIPLIER 30 select ARCH_HAS_GCOV_PROFILE_ALL 31 select ARCH_HAS_PMEM_API if X86_64 32 select ARCH_HAS_MMIO_FLUSH 33 select ARCH_HAS_SG_CHAIN 34 select ARCH_HAS_UBSAN_SANITIZE_ALL 35 select ARCH_HAVE_NMI_SAFE_CMPXCHG 36 select ARCH_MIGHT_HAVE_ACPI_PDC if ACPI 37 select ARCH_MIGHT_HAVE_PC_PARPORT 38 select ARCH_MIGHT_HAVE_PC_SERIO 39 select ARCH_SUPPORTS_ATOMIC_RMW 40 select ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT 41 select ARCH_SUPPORTS_INT128 if X86_64 42 select ARCH_SUPPORTS_NUMA_BALANCING if X86_64 43 select ARCH_USE_BUILTIN_BSWAP 44 select ARCH_USE_CMPXCHG_LOCKREF if X86_64 45 select ARCH_USE_QUEUED_RWLOCKS 46 select ARCH_USE_QUEUED_SPINLOCKS 47 select ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH if SMP 48 select ARCH_WANTS_DYNAMIC_TASK_STRUCT 49 select ARCH_WANT_FRAME_POINTERS 50 select ARCH_WANT_IPC_PARSE_VERSION if X86_32 51 select ARCH_WANT_OPTIONAL_GPIOLIB 52 select BUILDTIME_EXTABLE_SORT 53 select CLKEVT_I8253 54 select CLKSRC_I8253 if X86_32 55 select CLOCKSOURCE_VALIDATE_LAST_CYCLE 56 select CLOCKSOURCE_WATCHDOG 57 select CLONE_BACKWARDS if X86_32 58 select COMPAT_OLD_SIGACTION if IA32_EMULATION 59 select DCACHE_WORD_ACCESS 60 select EDAC_ATOMIC_SCRUB 61 select EDAC_SUPPORT 62 select GENERIC_CLOCKEVENTS 63 select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC) 64 select GENERIC_CLOCKEVENTS_MIN_ADJUST 65 select GENERIC_CMOS_UPDATE 66 select GENERIC_CPU_AUTOPROBE 67 select GENERIC_EARLY_IOREMAP 68 select GENERIC_FIND_FIRST_BIT 69 select GENERIC_IOMAP 70 select GENERIC_IRQ_PROBE 71 select GENERIC_IRQ_SHOW 72 select GENERIC_PENDING_IRQ if SMP 73 select GENERIC_SMP_IDLE_THREAD 74 select GENERIC_STRNCPY_FROM_USER 75 select GENERIC_STRNLEN_USER 76 select GENERIC_TIME_VSYSCALL 77 select HAVE_ACPI_APEI if ACPI 78 select HAVE_ACPI_APEI_NMI if ACPI 79 select HAVE_ALIGNED_STRUCT_PAGE if SLUB 80 select HAVE_AOUT if X86_32 81 select HAVE_ARCH_AUDITSYSCALL 82 select HAVE_ARCH_HUGE_VMAP if X86_64 || X86_PAE 83 select HAVE_ARCH_JUMP_LABEL 84 select HAVE_ARCH_KASAN if X86_64 && SPARSEMEM_VMEMMAP 85 select HAVE_ARCH_KGDB 86 select HAVE_ARCH_KMEMCHECK 87 select HAVE_ARCH_MMAP_RND_BITS if MMU 88 select HAVE_ARCH_MMAP_RND_COMPAT_BITS if MMU && COMPAT 89 select HAVE_ARCH_SECCOMP_FILTER 90 select HAVE_ARCH_SOFT_DIRTY if X86_64 91 select HAVE_ARCH_TRACEHOOK 92 select HAVE_ARCH_TRANSPARENT_HUGEPAGE 93 select HAVE_BPF_JIT if X86_64 94 select HAVE_CC_STACKPROTECTOR 95 select HAVE_CMPXCHG_DOUBLE 96 select HAVE_CMPXCHG_LOCAL 97 select HAVE_CONTEXT_TRACKING if X86_64 98 select HAVE_COPY_THREAD_TLS 99 select HAVE_C_RECORDMCOUNT 100 select HAVE_DEBUG_KMEMLEAK 101 select HAVE_DEBUG_STACKOVERFLOW 102 select HAVE_DMA_API_DEBUG 103 select HAVE_DMA_CONTIGUOUS 104 select HAVE_DYNAMIC_FTRACE 105 select HAVE_DYNAMIC_FTRACE_WITH_REGS 106 select HAVE_EFFICIENT_UNALIGNED_ACCESS 107 select HAVE_FENTRY if X86_64 108 select HAVE_FTRACE_MCOUNT_RECORD 109 select HAVE_FUNCTION_GRAPH_FP_TEST 110 select HAVE_FUNCTION_GRAPH_TRACER 111 select HAVE_FUNCTION_TRACER 112 select HAVE_GENERIC_DMA_COHERENT if X86_32 113 select HAVE_HW_BREAKPOINT 114 select HAVE_IDE 115 select HAVE_IOREMAP_PROT 116 select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64 117 select HAVE_IRQ_TIME_ACCOUNTING 118 select HAVE_KERNEL_BZIP2 119 select HAVE_KERNEL_GZIP 120 select HAVE_KERNEL_LZ4 121 select HAVE_KERNEL_LZMA 122 select HAVE_KERNEL_LZO 123 select HAVE_KERNEL_XZ 124 select HAVE_KPROBES 125 select HAVE_KPROBES_ON_FTRACE 126 select HAVE_KRETPROBES 127 select HAVE_KVM 128 select HAVE_LIVEPATCH if X86_64 129 select HAVE_MEMBLOCK 130 select HAVE_MEMBLOCK_NODE_MAP 131 select HAVE_MIXED_BREAKPOINTS_REGS 132 select HAVE_OPROFILE 133 select HAVE_OPTPROBES 134 select HAVE_PCSPKR_PLATFORM 135 select HAVE_PERF_EVENTS 136 select HAVE_PERF_EVENTS_NMI 137 select HAVE_PERF_REGS 138 select HAVE_PERF_USER_STACK_DUMP 139 select HAVE_REGS_AND_STACK_ACCESS_API 140 select HAVE_SYSCALL_TRACEPOINTS 141 select HAVE_UID16 if X86_32 || IA32_EMULATION 142 select HAVE_UNSTABLE_SCHED_CLOCK 143 select HAVE_USER_RETURN_NOTIFIER 144 select IRQ_FORCED_THREADING 145 select MODULES_USE_ELF_RELA if X86_64 146 select MODULES_USE_ELF_REL if X86_32 147 select OLD_SIGACTION if X86_32 148 select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION 149 select PERF_EVENTS 150 select RTC_LIB 151 select SPARSE_IRQ 152 select SRCU 153 select SYSCTL_EXCEPTION_TRACE 154 select USER_STACKTRACE_SUPPORT 155 select VIRT_TO_BUS 156 select X86_DEV_DMA_OPS if X86_64 157 select X86_FEATURE_NAMES if PROC_FS 158 159config INSTRUCTION_DECODER 160 def_bool y 161 depends on KPROBES || PERF_EVENTS || UPROBES 162 163config PERF_EVENTS_INTEL_UNCORE 164 def_bool y 165 depends on PERF_EVENTS && CPU_SUP_INTEL && PCI 166 167config OUTPUT_FORMAT 168 string 169 default "elf32-i386" if X86_32 170 default "elf64-x86-64" if X86_64 171 172config ARCH_DEFCONFIG 173 string 174 default "arch/x86/configs/i386_defconfig" if X86_32 175 default "arch/x86/configs/x86_64_defconfig" if X86_64 176 177config LOCKDEP_SUPPORT 178 def_bool y 179 180config STACKTRACE_SUPPORT 181 def_bool y 182 183config MMU 184 def_bool y 185 186config ARCH_MMAP_RND_BITS_MIN 187 default 28 if 64BIT 188 default 8 189 190config ARCH_MMAP_RND_BITS_MAX 191 default 32 if 64BIT 192 default 16 193 194config ARCH_MMAP_RND_COMPAT_BITS_MIN 195 default 8 196 197config ARCH_MMAP_RND_COMPAT_BITS_MAX 198 default 16 199 200config SBUS 201 bool 202 203config NEED_DMA_MAP_STATE 204 def_bool y 205 depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG || SWIOTLB 206 207config NEED_SG_DMA_LENGTH 208 def_bool y 209 210config GENERIC_ISA_DMA 211 def_bool y 212 depends on ISA_DMA_API 213 214config GENERIC_BUG 215 def_bool y 216 depends on BUG 217 select GENERIC_BUG_RELATIVE_POINTERS if X86_64 218 219config GENERIC_BUG_RELATIVE_POINTERS 220 bool 221 222config GENERIC_HWEIGHT 223 def_bool y 224 225config ARCH_MAY_HAVE_PC_FDC 226 def_bool y 227 depends on ISA_DMA_API 228 229config RWSEM_XCHGADD_ALGORITHM 230 def_bool y 231 232config GENERIC_CALIBRATE_DELAY 233 def_bool y 234 235config ARCH_HAS_CPU_RELAX 236 def_bool y 237 238config ARCH_HAS_CACHE_LINE_SIZE 239 def_bool y 240 241config HAVE_SETUP_PER_CPU_AREA 242 def_bool y 243 244config NEED_PER_CPU_EMBED_FIRST_CHUNK 245 def_bool y 246 247config NEED_PER_CPU_PAGE_FIRST_CHUNK 248 def_bool y 249 250config ARCH_HIBERNATION_POSSIBLE 251 def_bool y 252 253config ARCH_SUSPEND_POSSIBLE 254 def_bool y 255 256config ARCH_WANT_HUGE_PMD_SHARE 257 def_bool y 258 259config ARCH_WANT_GENERAL_HUGETLB 260 def_bool y 261 262config ZONE_DMA32 263 def_bool y if X86_64 264 265config AUDIT_ARCH 266 def_bool y if X86_64 267 268config ARCH_SUPPORTS_OPTIMIZED_INLINING 269 def_bool y 270 271config ARCH_SUPPORTS_DEBUG_PAGEALLOC 272 def_bool y 273 274config KASAN_SHADOW_OFFSET 275 hex 276 depends on KASAN 277 default 0xdffffc0000000000 278 279config HAVE_INTEL_TXT 280 def_bool y 281 depends on INTEL_IOMMU && ACPI 282 283config X86_32_SMP 284 def_bool y 285 depends on X86_32 && SMP 286 287config X86_64_SMP 288 def_bool y 289 depends on X86_64 && SMP 290 291config X86_32_LAZY_GS 292 def_bool y 293 depends on X86_32 && !CC_STACKPROTECTOR 294 295config ARCH_HWEIGHT_CFLAGS 296 string 297 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32 298 default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64 299 300config ARCH_SUPPORTS_UPROBES 301 def_bool y 302 303config FIX_EARLYCON_MEM 304 def_bool y 305 306config DEBUG_RODATA 307 def_bool y 308 309config PGTABLE_LEVELS 310 int 311 default 4 if X86_64 312 default 3 if X86_PAE 313 default 2 314 315source "init/Kconfig" 316source "kernel/Kconfig.freezer" 317 318menu "Processor type and features" 319 320config ZONE_DMA 321 bool "DMA memory allocation support" if EXPERT 322 default y 323 help 324 DMA memory allocation support allows devices with less than 32-bit 325 addressing to allocate within the first 16MB of address space. 326 Disable if no such devices will be used. 327 328 If unsure, say Y. 329 330config SMP 331 bool "Symmetric multi-processing support" 332 ---help--- 333 This enables support for systems with more than one CPU. If you have 334 a system with only one CPU, say N. If you have a system with more 335 than one CPU, say Y. 336 337 If you say N here, the kernel will run on uni- and multiprocessor 338 machines, but will use only one CPU of a multiprocessor machine. If 339 you say Y here, the kernel will run on many, but not all, 340 uniprocessor machines. On a uniprocessor machine, the kernel 341 will run faster if you say N here. 342 343 Note that if you say Y here and choose architecture "586" or 344 "Pentium" under "Processor family", the kernel will not work on 486 345 architectures. Similarly, multiprocessor kernels for the "PPro" 346 architecture may not work on all Pentium based boards. 347 348 People using multiprocessor machines who say Y here should also say 349 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power 350 Management" code will be disabled if you say Y here. 351 352 See also <file:Documentation/x86/i386/IO-APIC.txt>, 353 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at 354 <http://www.tldp.org/docs.html#howto>. 355 356 If you don't know what to do here, say N. 357 358config X86_FEATURE_NAMES 359 bool "Processor feature human-readable names" if EMBEDDED 360 default y 361 ---help--- 362 This option compiles in a table of x86 feature bits and corresponding 363 names. This is required to support /proc/cpuinfo and a few kernel 364 messages. You can disable this to save space, at the expense of 365 making those few kernel messages show numeric feature bits instead. 366 367 If in doubt, say Y. 368 369config X86_FAST_FEATURE_TESTS 370 bool "Fast CPU feature tests" if EMBEDDED 371 default y 372 ---help--- 373 Some fast-paths in the kernel depend on the capabilities of the CPU. 374 Say Y here for the kernel to patch in the appropriate code at runtime 375 based on the capabilities of the CPU. The infrastructure for patching 376 code at runtime takes up some additional space; space-constrained 377 embedded systems may wish to say N here to produce smaller, slightly 378 slower code. 379 380config X86_X2APIC 381 bool "Support x2apic" 382 depends on X86_LOCAL_APIC && X86_64 && (IRQ_REMAP || HYPERVISOR_GUEST) 383 ---help--- 384 This enables x2apic support on CPUs that have this feature. 385 386 This allows 32-bit apic IDs (so it can support very large systems), 387 and accesses the local apic via MSRs not via mmio. 388 389 If you don't know what to do here, say N. 390 391config X86_MPPARSE 392 bool "Enable MPS table" if ACPI || SFI 393 default y 394 depends on X86_LOCAL_APIC 395 ---help--- 396 For old smp systems that do not have proper acpi support. Newer systems 397 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it 398 399config X86_BIGSMP 400 bool "Support for big SMP systems with more than 8 CPUs" 401 depends on X86_32 && SMP 402 ---help--- 403 This option is needed for the systems that have more than 8 CPUs 404 405config GOLDFISH 406 def_bool y 407 depends on X86_GOLDFISH 408 409if X86_32 410config X86_EXTENDED_PLATFORM 411 bool "Support for extended (non-PC) x86 platforms" 412 default y 413 ---help--- 414 If you disable this option then the kernel will only support 415 standard PC platforms. (which covers the vast majority of 416 systems out there.) 417 418 If you enable this option then you'll be able to select support 419 for the following (non-PC) 32 bit x86 platforms: 420 Goldfish (Android emulator) 421 AMD Elan 422 RDC R-321x SoC 423 SGI 320/540 (Visual Workstation) 424 STA2X11-based (e.g. Northville) 425 Moorestown MID devices 426 427 If you have one of these systems, or if you want to build a 428 generic distribution kernel, say Y here - otherwise say N. 429endif 430 431if X86_64 432config X86_EXTENDED_PLATFORM 433 bool "Support for extended (non-PC) x86 platforms" 434 default y 435 ---help--- 436 If you disable this option then the kernel will only support 437 standard PC platforms. (which covers the vast majority of 438 systems out there.) 439 440 If you enable this option then you'll be able to select support 441 for the following (non-PC) 64 bit x86 platforms: 442 Numascale NumaChip 443 ScaleMP vSMP 444 SGI Ultraviolet 445 446 If you have one of these systems, or if you want to build a 447 generic distribution kernel, say Y here - otherwise say N. 448endif 449# This is an alphabetically sorted list of 64 bit extended platforms 450# Please maintain the alphabetic order if and when there are additions 451config X86_NUMACHIP 452 bool "Numascale NumaChip" 453 depends on X86_64 454 depends on X86_EXTENDED_PLATFORM 455 depends on NUMA 456 depends on SMP 457 depends on X86_X2APIC 458 depends on PCI_MMCONFIG 459 ---help--- 460 Adds support for Numascale NumaChip large-SMP systems. Needed to 461 enable more than ~168 cores. 462 If you don't have one of these, you should say N here. 463 464config X86_VSMP 465 bool "ScaleMP vSMP" 466 select HYPERVISOR_GUEST 467 select PARAVIRT 468 depends on X86_64 && PCI 469 depends on X86_EXTENDED_PLATFORM 470 depends on SMP 471 ---help--- 472 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is 473 supposed to run on these EM64T-based machines. Only choose this option 474 if you have one of these machines. 475 476config X86_UV 477 bool "SGI Ultraviolet" 478 depends on X86_64 479 depends on X86_EXTENDED_PLATFORM 480 depends on NUMA 481 depends on EFI 482 depends on X86_X2APIC 483 depends on PCI 484 ---help--- 485 This option is needed in order to support SGI Ultraviolet systems. 486 If you don't have one of these, you should say N here. 487 488# Following is an alphabetically sorted list of 32 bit extended platforms 489# Please maintain the alphabetic order if and when there are additions 490 491config X86_GOLDFISH 492 bool "Goldfish (Virtual Platform)" 493 depends on X86_EXTENDED_PLATFORM 494 ---help--- 495 Enable support for the Goldfish virtual platform used primarily 496 for Android development. Unless you are building for the Android 497 Goldfish emulator say N here. 498 499config X86_INTEL_CE 500 bool "CE4100 TV platform" 501 depends on PCI 502 depends on PCI_GODIRECT 503 depends on X86_IO_APIC 504 depends on X86_32 505 depends on X86_EXTENDED_PLATFORM 506 select X86_REBOOTFIXUPS 507 select OF 508 select OF_EARLY_FLATTREE 509 ---help--- 510 Select for the Intel CE media processor (CE4100) SOC. 511 This option compiles in support for the CE4100 SOC for settop 512 boxes and media devices. 513 514config X86_INTEL_MID 515 bool "Intel MID platform support" 516 depends on X86_EXTENDED_PLATFORM 517 depends on X86_PLATFORM_DEVICES 518 depends on PCI 519 depends on X86_64 || (PCI_GOANY && X86_32) 520 depends on X86_IO_APIC 521 select SFI 522 select I2C 523 select DW_APB_TIMER 524 select APB_TIMER 525 select INTEL_SCU_IPC 526 select MFD_INTEL_MSIC 527 ---help--- 528 Select to build a kernel capable of supporting Intel MID (Mobile 529 Internet Device) platform systems which do not have the PCI legacy 530 interfaces. If you are building for a PC class system say N here. 531 532 Intel MID platforms are based on an Intel processor and chipset which 533 consume less power than most of the x86 derivatives. 534 535config X86_INTEL_QUARK 536 bool "Intel Quark platform support" 537 depends on X86_32 538 depends on X86_EXTENDED_PLATFORM 539 depends on X86_PLATFORM_DEVICES 540 depends on X86_TSC 541 depends on PCI 542 depends on PCI_GOANY 543 depends on X86_IO_APIC 544 select IOSF_MBI 545 select INTEL_IMR 546 select COMMON_CLK 547 ---help--- 548 Select to include support for Quark X1000 SoC. 549 Say Y here if you have a Quark based system such as the Arduino 550 compatible Intel Galileo. 551 552config X86_INTEL_LPSS 553 bool "Intel Low Power Subsystem Support" 554 depends on X86 && ACPI 555 select COMMON_CLK 556 select PINCTRL 557 select IOSF_MBI 558 ---help--- 559 Select to build support for Intel Low Power Subsystem such as 560 found on Intel Lynxpoint PCH. Selecting this option enables 561 things like clock tree (common clock framework) and pincontrol 562 which are needed by the LPSS peripheral drivers. 563 564config X86_AMD_PLATFORM_DEVICE 565 bool "AMD ACPI2Platform devices support" 566 depends on ACPI 567 select COMMON_CLK 568 select PINCTRL 569 ---help--- 570 Select to interpret AMD specific ACPI device to platform device 571 such as I2C, UART, GPIO found on AMD Carrizo and later chipsets. 572 I2C and UART depend on COMMON_CLK to set clock. GPIO driver is 573 implemented under PINCTRL subsystem. 574 575config IOSF_MBI 576 tristate "Intel SoC IOSF Sideband support for SoC platforms" 577 depends on PCI 578 ---help--- 579 This option enables sideband register access support for Intel SoC 580 platforms. On these platforms the IOSF sideband is used in lieu of 581 MSR's for some register accesses, mostly but not limited to thermal 582 and power. Drivers may query the availability of this device to 583 determine if they need the sideband in order to work on these 584 platforms. The sideband is available on the following SoC products. 585 This list is not meant to be exclusive. 586 - BayTrail 587 - Braswell 588 - Quark 589 590 You should say Y if you are running a kernel on one of these SoC's. 591 592config IOSF_MBI_DEBUG 593 bool "Enable IOSF sideband access through debugfs" 594 depends on IOSF_MBI && DEBUG_FS 595 ---help--- 596 Select this option to expose the IOSF sideband access registers (MCR, 597 MDR, MCRX) through debugfs to write and read register information from 598 different units on the SoC. This is most useful for obtaining device 599 state information for debug and analysis. As this is a general access 600 mechanism, users of this option would have specific knowledge of the 601 device they want to access. 602 603 If you don't require the option or are in doubt, say N. 604 605config X86_RDC321X 606 bool "RDC R-321x SoC" 607 depends on X86_32 608 depends on X86_EXTENDED_PLATFORM 609 select M486 610 select X86_REBOOTFIXUPS 611 ---help--- 612 This option is needed for RDC R-321x system-on-chip, also known 613 as R-8610-(G). 614 If you don't have one of these chips, you should say N here. 615 616config X86_32_NON_STANDARD 617 bool "Support non-standard 32-bit SMP architectures" 618 depends on X86_32 && SMP 619 depends on X86_EXTENDED_PLATFORM 620 ---help--- 621 This option compiles in the bigsmp and STA2X11 default 622 subarchitectures. It is intended for a generic binary 623 kernel. If you select them all, kernel will probe it one by 624 one and will fallback to default. 625 626# Alphabetically sorted list of Non standard 32 bit platforms 627 628config X86_SUPPORTS_MEMORY_FAILURE 629 def_bool y 630 # MCE code calls memory_failure(): 631 depends on X86_MCE 632 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags: 633 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH: 634 depends on X86_64 || !SPARSEMEM 635 select ARCH_SUPPORTS_MEMORY_FAILURE 636 637config STA2X11 638 bool "STA2X11 Companion Chip Support" 639 depends on X86_32_NON_STANDARD && PCI 640 select X86_DEV_DMA_OPS 641 select X86_DMA_REMAP 642 select SWIOTLB 643 select MFD_STA2X11 644 select ARCH_REQUIRE_GPIOLIB 645 default n 646 ---help--- 647 This adds support for boards based on the STA2X11 IO-Hub, 648 a.k.a. "ConneXt". The chip is used in place of the standard 649 PC chipset, so all "standard" peripherals are missing. If this 650 option is selected the kernel will still be able to boot on 651 standard PC machines. 652 653config X86_32_IRIS 654 tristate "Eurobraille/Iris poweroff module" 655 depends on X86_32 656 ---help--- 657 The Iris machines from EuroBraille do not have APM or ACPI support 658 to shut themselves down properly. A special I/O sequence is 659 needed to do so, which is what this module does at 660 kernel shutdown. 661 662 This is only for Iris machines from EuroBraille. 663 664 If unused, say N. 665 666config SCHED_OMIT_FRAME_POINTER 667 def_bool y 668 prompt "Single-depth WCHAN output" 669 depends on X86 670 ---help--- 671 Calculate simpler /proc/<PID>/wchan values. If this option 672 is disabled then wchan values will recurse back to the 673 caller function. This provides more accurate wchan values, 674 at the expense of slightly more scheduling overhead. 675 676 If in doubt, say "Y". 677 678menuconfig HYPERVISOR_GUEST 679 bool "Linux guest support" 680 ---help--- 681 Say Y here to enable options for running Linux under various hyper- 682 visors. This option enables basic hypervisor detection and platform 683 setup. 684 685 If you say N, all options in this submenu will be skipped and 686 disabled, and Linux guest support won't be built in. 687 688if HYPERVISOR_GUEST 689 690config PARAVIRT 691 bool "Enable paravirtualization code" 692 ---help--- 693 This changes the kernel so it can modify itself when it is run 694 under a hypervisor, potentially improving performance significantly 695 over full virtualization. However, when run without a hypervisor 696 the kernel is theoretically slower and slightly larger. 697 698config PARAVIRT_DEBUG 699 bool "paravirt-ops debugging" 700 depends on PARAVIRT && DEBUG_KERNEL 701 ---help--- 702 Enable to debug paravirt_ops internals. Specifically, BUG if 703 a paravirt_op is missing when it is called. 704 705config PARAVIRT_SPINLOCKS 706 bool "Paravirtualization layer for spinlocks" 707 depends on PARAVIRT && SMP 708 select UNINLINE_SPIN_UNLOCK if !QUEUED_SPINLOCKS 709 ---help--- 710 Paravirtualized spinlocks allow a pvops backend to replace the 711 spinlock implementation with something virtualization-friendly 712 (for example, block the virtual CPU rather than spinning). 713 714 It has a minimal impact on native kernels and gives a nice performance 715 benefit on paravirtualized KVM / Xen kernels. 716 717 If you are unsure how to answer this question, answer Y. 718 719config QUEUED_LOCK_STAT 720 bool "Paravirt queued spinlock statistics" 721 depends on PARAVIRT_SPINLOCKS && DEBUG_FS && QUEUED_SPINLOCKS 722 ---help--- 723 Enable the collection of statistical data on the slowpath 724 behavior of paravirtualized queued spinlocks and report 725 them on debugfs. 726 727source "arch/x86/xen/Kconfig" 728 729config KVM_GUEST 730 bool "KVM Guest support (including kvmclock)" 731 depends on PARAVIRT 732 select PARAVIRT_CLOCK 733 default y 734 ---help--- 735 This option enables various optimizations for running under the KVM 736 hypervisor. It includes a paravirtualized clock, so that instead 737 of relying on a PIT (or probably other) emulation by the 738 underlying device model, the host provides the guest with 739 timing infrastructure such as time of day, and system time 740 741config KVM_DEBUG_FS 742 bool "Enable debug information for KVM Guests in debugfs" 743 depends on KVM_GUEST && DEBUG_FS 744 default n 745 ---help--- 746 This option enables collection of various statistics for KVM guest. 747 Statistics are displayed in debugfs filesystem. Enabling this option 748 may incur significant overhead. 749 750source "arch/x86/lguest/Kconfig" 751 752config PARAVIRT_TIME_ACCOUNTING 753 bool "Paravirtual steal time accounting" 754 depends on PARAVIRT 755 default n 756 ---help--- 757 Select this option to enable fine granularity task steal time 758 accounting. Time spent executing other tasks in parallel with 759 the current vCPU is discounted from the vCPU power. To account for 760 that, there can be a small performance impact. 761 762 If in doubt, say N here. 763 764config PARAVIRT_CLOCK 765 bool 766 767endif #HYPERVISOR_GUEST 768 769config NO_BOOTMEM 770 def_bool y 771 772source "arch/x86/Kconfig.cpu" 773 774config HPET_TIMER 775 def_bool X86_64 776 prompt "HPET Timer Support" if X86_32 777 ---help--- 778 Use the IA-PC HPET (High Precision Event Timer) to manage 779 time in preference to the PIT and RTC, if a HPET is 780 present. 781 HPET is the next generation timer replacing legacy 8254s. 782 The HPET provides a stable time base on SMP 783 systems, unlike the TSC, but it is more expensive to access, 784 as it is off-chip. The interface used is documented 785 in the HPET spec, revision 1. 786 787 You can safely choose Y here. However, HPET will only be 788 activated if the platform and the BIOS support this feature. 789 Otherwise the 8254 will be used for timing services. 790 791 Choose N to continue using the legacy 8254 timer. 792 793config HPET_EMULATE_RTC 794 def_bool y 795 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y) 796 797config APB_TIMER 798 def_bool y if X86_INTEL_MID 799 prompt "Intel MID APB Timer Support" if X86_INTEL_MID 800 select DW_APB_TIMER 801 depends on X86_INTEL_MID && SFI 802 help 803 APB timer is the replacement for 8254, HPET on X86 MID platforms. 804 The APBT provides a stable time base on SMP 805 systems, unlike the TSC, but it is more expensive to access, 806 as it is off-chip. APB timers are always running regardless of CPU 807 C states, they are used as per CPU clockevent device when possible. 808 809# Mark as expert because too many people got it wrong. 810# The code disables itself when not needed. 811config DMI 812 default y 813 select DMI_SCAN_MACHINE_NON_EFI_FALLBACK 814 bool "Enable DMI scanning" if EXPERT 815 ---help--- 816 Enabled scanning of DMI to identify machine quirks. Say Y 817 here unless you have verified that your setup is not 818 affected by entries in the DMI blacklist. Required by PNP 819 BIOS code. 820 821config GART_IOMMU 822 bool "Old AMD GART IOMMU support" 823 select SWIOTLB 824 depends on X86_64 && PCI && AMD_NB 825 ---help--- 826 Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron 827 GART based hardware IOMMUs. 828 829 The GART supports full DMA access for devices with 32-bit access 830 limitations, on systems with more than 3 GB. This is usually needed 831 for USB, sound, many IDE/SATA chipsets and some other devices. 832 833 Newer systems typically have a modern AMD IOMMU, supported via 834 the CONFIG_AMD_IOMMU=y config option. 835 836 In normal configurations this driver is only active when needed: 837 there's more than 3 GB of memory and the system contains a 838 32-bit limited device. 839 840 If unsure, say Y. 841 842config CALGARY_IOMMU 843 bool "IBM Calgary IOMMU support" 844 select SWIOTLB 845 depends on X86_64 && PCI 846 ---help--- 847 Support for hardware IOMMUs in IBM's xSeries x366 and x460 848 systems. Needed to run systems with more than 3GB of memory 849 properly with 32-bit PCI devices that do not support DAC 850 (Double Address Cycle). Calgary also supports bus level 851 isolation, where all DMAs pass through the IOMMU. This 852 prevents them from going anywhere except their intended 853 destination. This catches hard-to-find kernel bugs and 854 mis-behaving drivers and devices that do not use the DMA-API 855 properly to set up their DMA buffers. The IOMMU can be 856 turned off at boot time with the iommu=off parameter. 857 Normally the kernel will make the right choice by itself. 858 If unsure, say Y. 859 860config CALGARY_IOMMU_ENABLED_BY_DEFAULT 861 def_bool y 862 prompt "Should Calgary be enabled by default?" 863 depends on CALGARY_IOMMU 864 ---help--- 865 Should Calgary be enabled by default? if you choose 'y', Calgary 866 will be used (if it exists). If you choose 'n', Calgary will not be 867 used even if it exists. If you choose 'n' and would like to use 868 Calgary anyway, pass 'iommu=calgary' on the kernel command line. 869 If unsure, say Y. 870 871# need this always selected by IOMMU for the VIA workaround 872config SWIOTLB 873 def_bool y if X86_64 874 ---help--- 875 Support for software bounce buffers used on x86-64 systems 876 which don't have a hardware IOMMU. Using this PCI devices 877 which can only access 32-bits of memory can be used on systems 878 with more than 3 GB of memory. 879 If unsure, say Y. 880 881config IOMMU_HELPER 882 def_bool y 883 depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU 884 885config MAXSMP 886 bool "Enable Maximum number of SMP Processors and NUMA Nodes" 887 depends on X86_64 && SMP && DEBUG_KERNEL 888 select CPUMASK_OFFSTACK 889 ---help--- 890 Enable maximum number of CPUS and NUMA Nodes for this architecture. 891 If unsure, say N. 892 893config NR_CPUS 894 int "Maximum number of CPUs" if SMP && !MAXSMP 895 range 2 8 if SMP && X86_32 && !X86_BIGSMP 896 range 2 512 if SMP && !MAXSMP && !CPUMASK_OFFSTACK 897 range 2 8192 if SMP && !MAXSMP && CPUMASK_OFFSTACK && X86_64 898 default "1" if !SMP 899 default "8192" if MAXSMP 900 default "32" if SMP && X86_BIGSMP 901 default "8" if SMP && X86_32 902 default "64" if SMP 903 ---help--- 904 This allows you to specify the maximum number of CPUs which this 905 kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum 906 supported value is 8192, otherwise the maximum value is 512. The 907 minimum value which makes sense is 2. 908 909 This is purely to save memory - each supported CPU adds 910 approximately eight kilobytes to the kernel image. 911 912config SCHED_SMT 913 bool "SMT (Hyperthreading) scheduler support" 914 depends on SMP 915 ---help--- 916 SMT scheduler support improves the CPU scheduler's decision making 917 when dealing with Intel Pentium 4 chips with HyperThreading at a 918 cost of slightly increased overhead in some places. If unsure say 919 N here. 920 921config SCHED_MC 922 def_bool y 923 prompt "Multi-core scheduler support" 924 depends on SMP 925 ---help--- 926 Multi-core scheduler support improves the CPU scheduler's decision 927 making when dealing with multi-core CPU chips at a cost of slightly 928 increased overhead in some places. If unsure say N here. 929 930source "kernel/Kconfig.preempt" 931 932config UP_LATE_INIT 933 def_bool y 934 depends on !SMP && X86_LOCAL_APIC 935 936config X86_UP_APIC 937 bool "Local APIC support on uniprocessors" if !PCI_MSI 938 default PCI_MSI 939 depends on X86_32 && !SMP && !X86_32_NON_STANDARD 940 ---help--- 941 A local APIC (Advanced Programmable Interrupt Controller) is an 942 integrated interrupt controller in the CPU. If you have a single-CPU 943 system which has a processor with a local APIC, you can say Y here to 944 enable and use it. If you say Y here even though your machine doesn't 945 have a local APIC, then the kernel will still run with no slowdown at 946 all. The local APIC supports CPU-generated self-interrupts (timer, 947 performance counters), and the NMI watchdog which detects hard 948 lockups. 949 950config X86_UP_IOAPIC 951 bool "IO-APIC support on uniprocessors" 952 depends on X86_UP_APIC 953 ---help--- 954 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an 955 SMP-capable replacement for PC-style interrupt controllers. Most 956 SMP systems and many recent uniprocessor systems have one. 957 958 If you have a single-CPU system with an IO-APIC, you can say Y here 959 to use it. If you say Y here even though your machine doesn't have 960 an IO-APIC, then the kernel will still run with no slowdown at all. 961 962config X86_LOCAL_APIC 963 def_bool y 964 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI 965 select IRQ_DOMAIN_HIERARCHY 966 select PCI_MSI_IRQ_DOMAIN if PCI_MSI 967 968config X86_IO_APIC 969 def_bool y 970 depends on X86_LOCAL_APIC || X86_UP_IOAPIC 971 972config X86_REROUTE_FOR_BROKEN_BOOT_IRQS 973 bool "Reroute for broken boot IRQs" 974 depends on X86_IO_APIC 975 ---help--- 976 This option enables a workaround that fixes a source of 977 spurious interrupts. This is recommended when threaded 978 interrupt handling is used on systems where the generation of 979 superfluous "boot interrupts" cannot be disabled. 980 981 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ 982 entry in the chipset's IO-APIC is masked (as, e.g. the RT 983 kernel does during interrupt handling). On chipsets where this 984 boot IRQ generation cannot be disabled, this workaround keeps 985 the original IRQ line masked so that only the equivalent "boot 986 IRQ" is delivered to the CPUs. The workaround also tells the 987 kernel to set up the IRQ handler on the boot IRQ line. In this 988 way only one interrupt is delivered to the kernel. Otherwise 989 the spurious second interrupt may cause the kernel to bring 990 down (vital) interrupt lines. 991 992 Only affects "broken" chipsets. Interrupt sharing may be 993 increased on these systems. 994 995config X86_MCE 996 bool "Machine Check / overheating reporting" 997 select GENERIC_ALLOCATOR 998 default y 999 ---help--- 1000 Machine Check support allows the processor to notify the 1001 kernel if it detects a problem (e.g. overheating, data corruption). 1002 The action the kernel takes depends on the severity of the problem, 1003 ranging from warning messages to halting the machine. 1004 1005config X86_MCE_INTEL 1006 def_bool y 1007 prompt "Intel MCE features" 1008 depends on X86_MCE && X86_LOCAL_APIC 1009 ---help--- 1010 Additional support for intel specific MCE features such as 1011 the thermal monitor. 1012 1013config X86_MCE_AMD 1014 def_bool y 1015 prompt "AMD MCE features" 1016 depends on X86_MCE && X86_LOCAL_APIC 1017 ---help--- 1018 Additional support for AMD specific MCE features such as 1019 the DRAM Error Threshold. 1020 1021config X86_ANCIENT_MCE 1022 bool "Support for old Pentium 5 / WinChip machine checks" 1023 depends on X86_32 && X86_MCE 1024 ---help--- 1025 Include support for machine check handling on old Pentium 5 or WinChip 1026 systems. These typically need to be enabled explicitly on the command 1027 line. 1028 1029config X86_MCE_THRESHOLD 1030 depends on X86_MCE_AMD || X86_MCE_INTEL 1031 def_bool y 1032 1033config X86_MCE_INJECT 1034 depends on X86_MCE 1035 tristate "Machine check injector support" 1036 ---help--- 1037 Provide support for injecting machine checks for testing purposes. 1038 If you don't know what a machine check is and you don't do kernel 1039 QA it is safe to say n. 1040 1041config X86_THERMAL_VECTOR 1042 def_bool y 1043 depends on X86_MCE_INTEL 1044 1045config X86_LEGACY_VM86 1046 bool "Legacy VM86 support" 1047 default n 1048 depends on X86_32 1049 ---help--- 1050 This option allows user programs to put the CPU into V8086 1051 mode, which is an 80286-era approximation of 16-bit real mode. 1052 1053 Some very old versions of X and/or vbetool require this option 1054 for user mode setting. Similarly, DOSEMU will use it if 1055 available to accelerate real mode DOS programs. However, any 1056 recent version of DOSEMU, X, or vbetool should be fully 1057 functional even without kernel VM86 support, as they will all 1058 fall back to software emulation. Nevertheless, if you are using 1059 a 16-bit DOS program where 16-bit performance matters, vm86 1060 mode might be faster than emulation and you might want to 1061 enable this option. 1062 1063 Note that any app that works on a 64-bit kernel is unlikely to 1064 need this option, as 64-bit kernels don't, and can't, support 1065 V8086 mode. This option is also unrelated to 16-bit protected 1066 mode and is not needed to run most 16-bit programs under Wine. 1067 1068 Enabling this option increases the complexity of the kernel 1069 and slows down exception handling a tiny bit. 1070 1071 If unsure, say N here. 1072 1073config VM86 1074 bool 1075 default X86_LEGACY_VM86 1076 1077config X86_16BIT 1078 bool "Enable support for 16-bit segments" if EXPERT 1079 default y 1080 depends on MODIFY_LDT_SYSCALL 1081 ---help--- 1082 This option is required by programs like Wine to run 16-bit 1083 protected mode legacy code on x86 processors. Disabling 1084 this option saves about 300 bytes on i386, or around 6K text 1085 plus 16K runtime memory on x86-64, 1086 1087config X86_ESPFIX32 1088 def_bool y 1089 depends on X86_16BIT && X86_32 1090 1091config X86_ESPFIX64 1092 def_bool y 1093 depends on X86_16BIT && X86_64 1094 1095config X86_VSYSCALL_EMULATION 1096 bool "Enable vsyscall emulation" if EXPERT 1097 default y 1098 depends on X86_64 1099 ---help--- 1100 This enables emulation of the legacy vsyscall page. Disabling 1101 it is roughly equivalent to booting with vsyscall=none, except 1102 that it will also disable the helpful warning if a program 1103 tries to use a vsyscall. With this option set to N, offending 1104 programs will just segfault, citing addresses of the form 1105 0xffffffffff600?00. 1106 1107 This option is required by many programs built before 2013, and 1108 care should be used even with newer programs if set to N. 1109 1110 Disabling this option saves about 7K of kernel size and 1111 possibly 4K of additional runtime pagetable memory. 1112 1113config TOSHIBA 1114 tristate "Toshiba Laptop support" 1115 depends on X86_32 1116 ---help--- 1117 This adds a driver to safely access the System Management Mode of 1118 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does 1119 not work on models with a Phoenix BIOS. The System Management Mode 1120 is used to set the BIOS and power saving options on Toshiba portables. 1121 1122 For information on utilities to make use of this driver see the 1123 Toshiba Linux utilities web site at: 1124 <http://www.buzzard.org.uk/toshiba/>. 1125 1126 Say Y if you intend to run this kernel on a Toshiba portable. 1127 Say N otherwise. 1128 1129config I8K 1130 tristate "Dell i8k legacy laptop support" 1131 select HWMON 1132 select SENSORS_DELL_SMM 1133 ---help--- 1134 This option enables legacy /proc/i8k userspace interface in hwmon 1135 dell-smm-hwmon driver. Character file /proc/i8k reports bios version, 1136 temperature and allows controlling fan speeds of Dell laptops via 1137 System Management Mode. For old Dell laptops (like Dell Inspiron 8000) 1138 it reports also power and hotkey status. For fan speed control is 1139 needed userspace package i8kutils. 1140 1141 Say Y if you intend to run this kernel on old Dell laptops or want to 1142 use userspace package i8kutils. 1143 Say N otherwise. 1144 1145config X86_REBOOTFIXUPS 1146 bool "Enable X86 board specific fixups for reboot" 1147 depends on X86_32 1148 ---help--- 1149 This enables chipset and/or board specific fixups to be done 1150 in order to get reboot to work correctly. This is only needed on 1151 some combinations of hardware and BIOS. The symptom, for which 1152 this config is intended, is when reboot ends with a stalled/hung 1153 system. 1154 1155 Currently, the only fixup is for the Geode machines using 1156 CS5530A and CS5536 chipsets and the RDC R-321x SoC. 1157 1158 Say Y if you want to enable the fixup. Currently, it's safe to 1159 enable this option even if you don't need it. 1160 Say N otherwise. 1161 1162config MICROCODE 1163 bool "CPU microcode loading support" 1164 default y 1165 depends on CPU_SUP_AMD || CPU_SUP_INTEL 1166 select FW_LOADER 1167 ---help--- 1168 If you say Y here, you will be able to update the microcode on 1169 Intel and AMD processors. The Intel support is for the IA32 family, 1170 e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4, Xeon etc. The 1171 AMD support is for families 0x10 and later. You will obviously need 1172 the actual microcode binary data itself which is not shipped with 1173 the Linux kernel. 1174 1175 The preferred method to load microcode from a detached initrd is described 1176 in Documentation/x86/early-microcode.txt. For that you need to enable 1177 CONFIG_BLK_DEV_INITRD in order for the loader to be able to scan the 1178 initrd for microcode blobs. 1179 1180 In addition, you can build-in the microcode into the kernel. For that you 1181 need to enable FIRMWARE_IN_KERNEL and add the vendor-supplied microcode 1182 to the CONFIG_EXTRA_FIRMWARE config option. 1183 1184config MICROCODE_INTEL 1185 bool "Intel microcode loading support" 1186 depends on MICROCODE 1187 default MICROCODE 1188 select FW_LOADER 1189 ---help--- 1190 This options enables microcode patch loading support for Intel 1191 processors. 1192 1193 For the current Intel microcode data package go to 1194 <https://downloadcenter.intel.com> and search for 1195 'Linux Processor Microcode Data File'. 1196 1197config MICROCODE_AMD 1198 bool "AMD microcode loading support" 1199 depends on MICROCODE 1200 select FW_LOADER 1201 ---help--- 1202 If you select this option, microcode patch loading support for AMD 1203 processors will be enabled. 1204 1205config MICROCODE_OLD_INTERFACE 1206 def_bool y 1207 depends on MICROCODE 1208 1209config X86_MSR 1210 tristate "/dev/cpu/*/msr - Model-specific register support" 1211 ---help--- 1212 This device gives privileged processes access to the x86 1213 Model-Specific Registers (MSRs). It is a character device with 1214 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. 1215 MSR accesses are directed to a specific CPU on multi-processor 1216 systems. 1217 1218config X86_CPUID 1219 tristate "/dev/cpu/*/cpuid - CPU information support" 1220 ---help--- 1221 This device gives processes access to the x86 CPUID instruction to 1222 be executed on a specific processor. It is a character device 1223 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to 1224 /dev/cpu/31/cpuid. 1225 1226choice 1227 prompt "High Memory Support" 1228 default HIGHMEM4G 1229 depends on X86_32 1230 1231config NOHIGHMEM 1232 bool "off" 1233 ---help--- 1234 Linux can use up to 64 Gigabytes of physical memory on x86 systems. 1235 However, the address space of 32-bit x86 processors is only 4 1236 Gigabytes large. That means that, if you have a large amount of 1237 physical memory, not all of it can be "permanently mapped" by the 1238 kernel. The physical memory that's not permanently mapped is called 1239 "high memory". 1240 1241 If you are compiling a kernel which will never run on a machine with 1242 more than 1 Gigabyte total physical RAM, answer "off" here (default 1243 choice and suitable for most users). This will result in a "3GB/1GB" 1244 split: 3GB are mapped so that each process sees a 3GB virtual memory 1245 space and the remaining part of the 4GB virtual memory space is used 1246 by the kernel to permanently map as much physical memory as 1247 possible. 1248 1249 If the machine has between 1 and 4 Gigabytes physical RAM, then 1250 answer "4GB" here. 1251 1252 If more than 4 Gigabytes is used then answer "64GB" here. This 1253 selection turns Intel PAE (Physical Address Extension) mode on. 1254 PAE implements 3-level paging on IA32 processors. PAE is fully 1255 supported by Linux, PAE mode is implemented on all recent Intel 1256 processors (Pentium Pro and better). NOTE: If you say "64GB" here, 1257 then the kernel will not boot on CPUs that don't support PAE! 1258 1259 The actual amount of total physical memory will either be 1260 auto detected or can be forced by using a kernel command line option 1261 such as "mem=256M". (Try "man bootparam" or see the documentation of 1262 your boot loader (lilo or loadlin) about how to pass options to the 1263 kernel at boot time.) 1264 1265 If unsure, say "off". 1266 1267config HIGHMEM4G 1268 bool "4GB" 1269 ---help--- 1270 Select this if you have a 32-bit processor and between 1 and 4 1271 gigabytes of physical RAM. 1272 1273config HIGHMEM64G 1274 bool "64GB" 1275 depends on !M486 1276 select X86_PAE 1277 ---help--- 1278 Select this if you have a 32-bit processor and more than 4 1279 gigabytes of physical RAM. 1280 1281endchoice 1282 1283choice 1284 prompt "Memory split" if EXPERT 1285 default VMSPLIT_3G 1286 depends on X86_32 1287 ---help--- 1288 Select the desired split between kernel and user memory. 1289 1290 If the address range available to the kernel is less than the 1291 physical memory installed, the remaining memory will be available 1292 as "high memory". Accessing high memory is a little more costly 1293 than low memory, as it needs to be mapped into the kernel first. 1294 Note that increasing the kernel address space limits the range 1295 available to user programs, making the address space there 1296 tighter. Selecting anything other than the default 3G/1G split 1297 will also likely make your kernel incompatible with binary-only 1298 kernel modules. 1299 1300 If you are not absolutely sure what you are doing, leave this 1301 option alone! 1302 1303 config VMSPLIT_3G 1304 bool "3G/1G user/kernel split" 1305 config VMSPLIT_3G_OPT 1306 depends on !X86_PAE 1307 bool "3G/1G user/kernel split (for full 1G low memory)" 1308 config VMSPLIT_2G 1309 bool "2G/2G user/kernel split" 1310 config VMSPLIT_2G_OPT 1311 depends on !X86_PAE 1312 bool "2G/2G user/kernel split (for full 2G low memory)" 1313 config VMSPLIT_1G 1314 bool "1G/3G user/kernel split" 1315endchoice 1316 1317config PAGE_OFFSET 1318 hex 1319 default 0xB0000000 if VMSPLIT_3G_OPT 1320 default 0x80000000 if VMSPLIT_2G 1321 default 0x78000000 if VMSPLIT_2G_OPT 1322 default 0x40000000 if VMSPLIT_1G 1323 default 0xC0000000 1324 depends on X86_32 1325 1326config HIGHMEM 1327 def_bool y 1328 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G) 1329 1330config X86_PAE 1331 bool "PAE (Physical Address Extension) Support" 1332 depends on X86_32 && !HIGHMEM4G 1333 select SWIOTLB 1334 ---help--- 1335 PAE is required for NX support, and furthermore enables 1336 larger swapspace support for non-overcommit purposes. It 1337 has the cost of more pagetable lookup overhead, and also 1338 consumes more pagetable space per process. 1339 1340config ARCH_PHYS_ADDR_T_64BIT 1341 def_bool y 1342 depends on X86_64 || X86_PAE 1343 1344config ARCH_DMA_ADDR_T_64BIT 1345 def_bool y 1346 depends on X86_64 || HIGHMEM64G 1347 1348config X86_DIRECT_GBPAGES 1349 def_bool y 1350 depends on X86_64 && !DEBUG_PAGEALLOC && !KMEMCHECK 1351 ---help--- 1352 Certain kernel features effectively disable kernel 1353 linear 1 GB mappings (even if the CPU otherwise 1354 supports them), so don't confuse the user by printing 1355 that we have them enabled. 1356 1357# Common NUMA Features 1358config NUMA 1359 bool "Numa Memory Allocation and Scheduler Support" 1360 depends on SMP 1361 depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP) 1362 default y if X86_BIGSMP 1363 ---help--- 1364 Enable NUMA (Non Uniform Memory Access) support. 1365 1366 The kernel will try to allocate memory used by a CPU on the 1367 local memory controller of the CPU and add some more 1368 NUMA awareness to the kernel. 1369 1370 For 64-bit this is recommended if the system is Intel Core i7 1371 (or later), AMD Opteron, or EM64T NUMA. 1372 1373 For 32-bit this is only needed if you boot a 32-bit 1374 kernel on a 64-bit NUMA platform. 1375 1376 Otherwise, you should say N. 1377 1378config AMD_NUMA 1379 def_bool y 1380 prompt "Old style AMD Opteron NUMA detection" 1381 depends on X86_64 && NUMA && PCI 1382 ---help--- 1383 Enable AMD NUMA node topology detection. You should say Y here if 1384 you have a multi processor AMD system. This uses an old method to 1385 read the NUMA configuration directly from the builtin Northbridge 1386 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead, 1387 which also takes priority if both are compiled in. 1388 1389config X86_64_ACPI_NUMA 1390 def_bool y 1391 prompt "ACPI NUMA detection" 1392 depends on X86_64 && NUMA && ACPI && PCI 1393 select ACPI_NUMA 1394 ---help--- 1395 Enable ACPI SRAT based node topology detection. 1396 1397# Some NUMA nodes have memory ranges that span 1398# other nodes. Even though a pfn is valid and 1399# between a node's start and end pfns, it may not 1400# reside on that node. See memmap_init_zone() 1401# for details. 1402config NODES_SPAN_OTHER_NODES 1403 def_bool y 1404 depends on X86_64_ACPI_NUMA 1405 1406config NUMA_EMU 1407 bool "NUMA emulation" 1408 depends on NUMA 1409 ---help--- 1410 Enable NUMA emulation. A flat machine will be split 1411 into virtual nodes when booted with "numa=fake=N", where N is the 1412 number of nodes. This is only useful for debugging. 1413 1414config NODES_SHIFT 1415 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP 1416 range 1 10 1417 default "10" if MAXSMP 1418 default "6" if X86_64 1419 default "3" 1420 depends on NEED_MULTIPLE_NODES 1421 ---help--- 1422 Specify the maximum number of NUMA Nodes available on the target 1423 system. Increases memory reserved to accommodate various tables. 1424 1425config ARCH_HAVE_MEMORY_PRESENT 1426 def_bool y 1427 depends on X86_32 && DISCONTIGMEM 1428 1429config NEED_NODE_MEMMAP_SIZE 1430 def_bool y 1431 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM) 1432 1433config ARCH_FLATMEM_ENABLE 1434 def_bool y 1435 depends on X86_32 && !NUMA 1436 1437config ARCH_DISCONTIGMEM_ENABLE 1438 def_bool y 1439 depends on NUMA && X86_32 1440 1441config ARCH_DISCONTIGMEM_DEFAULT 1442 def_bool y 1443 depends on NUMA && X86_32 1444 1445config ARCH_SPARSEMEM_ENABLE 1446 def_bool y 1447 depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD 1448 select SPARSEMEM_STATIC if X86_32 1449 select SPARSEMEM_VMEMMAP_ENABLE if X86_64 1450 1451config ARCH_SPARSEMEM_DEFAULT 1452 def_bool y 1453 depends on X86_64 1454 1455config ARCH_SELECT_MEMORY_MODEL 1456 def_bool y 1457 depends on ARCH_SPARSEMEM_ENABLE 1458 1459config ARCH_MEMORY_PROBE 1460 bool "Enable sysfs memory/probe interface" 1461 depends on X86_64 && MEMORY_HOTPLUG 1462 help 1463 This option enables a sysfs memory/probe interface for testing. 1464 See Documentation/memory-hotplug.txt for more information. 1465 If you are unsure how to answer this question, answer N. 1466 1467config ARCH_PROC_KCORE_TEXT 1468 def_bool y 1469 depends on X86_64 && PROC_KCORE 1470 1471config ILLEGAL_POINTER_VALUE 1472 hex 1473 default 0 if X86_32 1474 default 0xdead000000000000 if X86_64 1475 1476source "mm/Kconfig" 1477 1478config X86_PMEM_LEGACY_DEVICE 1479 bool 1480 1481config X86_PMEM_LEGACY 1482 tristate "Support non-standard NVDIMMs and ADR protected memory" 1483 depends on PHYS_ADDR_T_64BIT 1484 depends on BLK_DEV 1485 select X86_PMEM_LEGACY_DEVICE 1486 select LIBNVDIMM 1487 help 1488 Treat memory marked using the non-standard e820 type of 12 as used 1489 by the Intel Sandy Bridge-EP reference BIOS as protected memory. 1490 The kernel will offer these regions to the 'pmem' driver so 1491 they can be used for persistent storage. 1492 1493 Say Y if unsure. 1494 1495config HIGHPTE 1496 bool "Allocate 3rd-level pagetables from highmem" 1497 depends on HIGHMEM 1498 ---help--- 1499 The VM uses one page table entry for each page of physical memory. 1500 For systems with a lot of RAM, this can be wasteful of precious 1501 low memory. Setting this option will put user-space page table 1502 entries in high memory. 1503 1504config X86_CHECK_BIOS_CORRUPTION 1505 bool "Check for low memory corruption" 1506 ---help--- 1507 Periodically check for memory corruption in low memory, which 1508 is suspected to be caused by BIOS. Even when enabled in the 1509 configuration, it is disabled at runtime. Enable it by 1510 setting "memory_corruption_check=1" on the kernel command 1511 line. By default it scans the low 64k of memory every 60 1512 seconds; see the memory_corruption_check_size and 1513 memory_corruption_check_period parameters in 1514 Documentation/kernel-parameters.txt to adjust this. 1515 1516 When enabled with the default parameters, this option has 1517 almost no overhead, as it reserves a relatively small amount 1518 of memory and scans it infrequently. It both detects corruption 1519 and prevents it from affecting the running system. 1520 1521 It is, however, intended as a diagnostic tool; if repeatable 1522 BIOS-originated corruption always affects the same memory, 1523 you can use memmap= to prevent the kernel from using that 1524 memory. 1525 1526config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK 1527 bool "Set the default setting of memory_corruption_check" 1528 depends on X86_CHECK_BIOS_CORRUPTION 1529 default y 1530 ---help--- 1531 Set whether the default state of memory_corruption_check is 1532 on or off. 1533 1534config X86_RESERVE_LOW 1535 int "Amount of low memory, in kilobytes, to reserve for the BIOS" 1536 default 64 1537 range 4 640 1538 ---help--- 1539 Specify the amount of low memory to reserve for the BIOS. 1540 1541 The first page contains BIOS data structures that the kernel 1542 must not use, so that page must always be reserved. 1543 1544 By default we reserve the first 64K of physical RAM, as a 1545 number of BIOSes are known to corrupt that memory range 1546 during events such as suspend/resume or monitor cable 1547 insertion, so it must not be used by the kernel. 1548 1549 You can set this to 4 if you are absolutely sure that you 1550 trust the BIOS to get all its memory reservations and usages 1551 right. If you know your BIOS have problems beyond the 1552 default 64K area, you can set this to 640 to avoid using the 1553 entire low memory range. 1554 1555 If you have doubts about the BIOS (e.g. suspend/resume does 1556 not work or there's kernel crashes after certain hardware 1557 hotplug events) then you might want to enable 1558 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check 1559 typical corruption patterns. 1560 1561 Leave this to the default value of 64 if you are unsure. 1562 1563config MATH_EMULATION 1564 bool 1565 depends on MODIFY_LDT_SYSCALL 1566 prompt "Math emulation" if X86_32 1567 ---help--- 1568 Linux can emulate a math coprocessor (used for floating point 1569 operations) if you don't have one. 486DX and Pentium processors have 1570 a math coprocessor built in, 486SX and 386 do not, unless you added 1571 a 487DX or 387, respectively. (The messages during boot time can 1572 give you some hints here ["man dmesg"].) Everyone needs either a 1573 coprocessor or this emulation. 1574 1575 If you don't have a math coprocessor, you need to say Y here; if you 1576 say Y here even though you have a coprocessor, the coprocessor will 1577 be used nevertheless. (This behavior can be changed with the kernel 1578 command line option "no387", which comes handy if your coprocessor 1579 is broken. Try "man bootparam" or see the documentation of your boot 1580 loader (lilo or loadlin) about how to pass options to the kernel at 1581 boot time.) This means that it is a good idea to say Y here if you 1582 intend to use this kernel on different machines. 1583 1584 More information about the internals of the Linux math coprocessor 1585 emulation can be found in <file:arch/x86/math-emu/README>. 1586 1587 If you are not sure, say Y; apart from resulting in a 66 KB bigger 1588 kernel, it won't hurt. 1589 1590config MTRR 1591 def_bool y 1592 prompt "MTRR (Memory Type Range Register) support" if EXPERT 1593 ---help--- 1594 On Intel P6 family processors (Pentium Pro, Pentium II and later) 1595 the Memory Type Range Registers (MTRRs) may be used to control 1596 processor access to memory ranges. This is most useful if you have 1597 a video (VGA) card on a PCI or AGP bus. Enabling write-combining 1598 allows bus write transfers to be combined into a larger transfer 1599 before bursting over the PCI/AGP bus. This can increase performance 1600 of image write operations 2.5 times or more. Saying Y here creates a 1601 /proc/mtrr file which may be used to manipulate your processor's 1602 MTRRs. Typically the X server should use this. 1603 1604 This code has a reasonably generic interface so that similar 1605 control registers on other processors can be easily supported 1606 as well: 1607 1608 The Cyrix 6x86, 6x86MX and M II processors have Address Range 1609 Registers (ARRs) which provide a similar functionality to MTRRs. For 1610 these, the ARRs are used to emulate the MTRRs. 1611 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two 1612 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing 1613 write-combining. All of these processors are supported by this code 1614 and it makes sense to say Y here if you have one of them. 1615 1616 Saying Y here also fixes a problem with buggy SMP BIOSes which only 1617 set the MTRRs for the boot CPU and not for the secondary CPUs. This 1618 can lead to all sorts of problems, so it's good to say Y here. 1619 1620 You can safely say Y even if your machine doesn't have MTRRs, you'll 1621 just add about 9 KB to your kernel. 1622 1623 See <file:Documentation/x86/mtrr.txt> for more information. 1624 1625config MTRR_SANITIZER 1626 def_bool y 1627 prompt "MTRR cleanup support" 1628 depends on MTRR 1629 ---help--- 1630 Convert MTRR layout from continuous to discrete, so X drivers can 1631 add writeback entries. 1632 1633 Can be disabled with disable_mtrr_cleanup on the kernel command line. 1634 The largest mtrr entry size for a continuous block can be set with 1635 mtrr_chunk_size. 1636 1637 If unsure, say Y. 1638 1639config MTRR_SANITIZER_ENABLE_DEFAULT 1640 int "MTRR cleanup enable value (0-1)" 1641 range 0 1 1642 default "0" 1643 depends on MTRR_SANITIZER 1644 ---help--- 1645 Enable mtrr cleanup default value 1646 1647config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT 1648 int "MTRR cleanup spare reg num (0-7)" 1649 range 0 7 1650 default "1" 1651 depends on MTRR_SANITIZER 1652 ---help--- 1653 mtrr cleanup spare entries default, it can be changed via 1654 mtrr_spare_reg_nr=N on the kernel command line. 1655 1656config X86_PAT 1657 def_bool y 1658 prompt "x86 PAT support" if EXPERT 1659 depends on MTRR 1660 ---help--- 1661 Use PAT attributes to setup page level cache control. 1662 1663 PATs are the modern equivalents of MTRRs and are much more 1664 flexible than MTRRs. 1665 1666 Say N here if you see bootup problems (boot crash, boot hang, 1667 spontaneous reboots) or a non-working video driver. 1668 1669 If unsure, say Y. 1670 1671config ARCH_USES_PG_UNCACHED 1672 def_bool y 1673 depends on X86_PAT 1674 1675config ARCH_RANDOM 1676 def_bool y 1677 prompt "x86 architectural random number generator" if EXPERT 1678 ---help--- 1679 Enable the x86 architectural RDRAND instruction 1680 (Intel Bull Mountain technology) to generate random numbers. 1681 If supported, this is a high bandwidth, cryptographically 1682 secure hardware random number generator. 1683 1684config X86_SMAP 1685 def_bool y 1686 prompt "Supervisor Mode Access Prevention" if EXPERT 1687 ---help--- 1688 Supervisor Mode Access Prevention (SMAP) is a security 1689 feature in newer Intel processors. There is a small 1690 performance cost if this enabled and turned on; there is 1691 also a small increase in the kernel size if this is enabled. 1692 1693 If unsure, say Y. 1694 1695config X86_INTEL_MPX 1696 prompt "Intel MPX (Memory Protection Extensions)" 1697 def_bool n 1698 depends on CPU_SUP_INTEL 1699 ---help--- 1700 MPX provides hardware features that can be used in 1701 conjunction with compiler-instrumented code to check 1702 memory references. It is designed to detect buffer 1703 overflow or underflow bugs. 1704 1705 This option enables running applications which are 1706 instrumented or otherwise use MPX. It does not use MPX 1707 itself inside the kernel or to protect the kernel 1708 against bad memory references. 1709 1710 Enabling this option will make the kernel larger: 1711 ~8k of kernel text and 36 bytes of data on a 64-bit 1712 defconfig. It adds a long to the 'mm_struct' which 1713 will increase the kernel memory overhead of each 1714 process and adds some branches to paths used during 1715 exec() and munmap(). 1716 1717 For details, see Documentation/x86/intel_mpx.txt 1718 1719 If unsure, say N. 1720 1721config EFI 1722 bool "EFI runtime service support" 1723 depends on ACPI 1724 select UCS2_STRING 1725 select EFI_RUNTIME_WRAPPERS 1726 ---help--- 1727 This enables the kernel to use EFI runtime services that are 1728 available (such as the EFI variable services). 1729 1730 This option is only useful on systems that have EFI firmware. 1731 In addition, you should use the latest ELILO loader available 1732 at <http://elilo.sourceforge.net> in order to take advantage 1733 of EFI runtime services. However, even with this option, the 1734 resultant kernel should continue to boot on existing non-EFI 1735 platforms. 1736 1737config EFI_STUB 1738 bool "EFI stub support" 1739 depends on EFI && !X86_USE_3DNOW 1740 select RELOCATABLE 1741 ---help--- 1742 This kernel feature allows a bzImage to be loaded directly 1743 by EFI firmware without the use of a bootloader. 1744 1745 See Documentation/efi-stub.txt for more information. 1746 1747config EFI_MIXED 1748 bool "EFI mixed-mode support" 1749 depends on EFI_STUB && X86_64 1750 ---help--- 1751 Enabling this feature allows a 64-bit kernel to be booted 1752 on a 32-bit firmware, provided that your CPU supports 64-bit 1753 mode. 1754 1755 Note that it is not possible to boot a mixed-mode enabled 1756 kernel via the EFI boot stub - a bootloader that supports 1757 the EFI handover protocol must be used. 1758 1759 If unsure, say N. 1760 1761config SECCOMP 1762 def_bool y 1763 prompt "Enable seccomp to safely compute untrusted bytecode" 1764 ---help--- 1765 This kernel feature is useful for number crunching applications 1766 that may need to compute untrusted bytecode during their 1767 execution. By using pipes or other transports made available to 1768 the process as file descriptors supporting the read/write 1769 syscalls, it's possible to isolate those applications in 1770 their own address space using seccomp. Once seccomp is 1771 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled 1772 and the task is only allowed to execute a few safe syscalls 1773 defined by each seccomp mode. 1774 1775 If unsure, say Y. Only embedded should say N here. 1776 1777source kernel/Kconfig.hz 1778 1779config KEXEC 1780 bool "kexec system call" 1781 select KEXEC_CORE 1782 ---help--- 1783 kexec is a system call that implements the ability to shutdown your 1784 current kernel, and to start another kernel. It is like a reboot 1785 but it is independent of the system firmware. And like a reboot 1786 you can start any kernel with it, not just Linux. 1787 1788 The name comes from the similarity to the exec system call. 1789 1790 It is an ongoing process to be certain the hardware in a machine 1791 is properly shutdown, so do not be surprised if this code does not 1792 initially work for you. As of this writing the exact hardware 1793 interface is strongly in flux, so no good recommendation can be 1794 made. 1795 1796config KEXEC_FILE 1797 bool "kexec file based system call" 1798 select KEXEC_CORE 1799 select BUILD_BIN2C 1800 depends on X86_64 1801 depends on CRYPTO=y 1802 depends on CRYPTO_SHA256=y 1803 ---help--- 1804 This is new version of kexec system call. This system call is 1805 file based and takes file descriptors as system call argument 1806 for kernel and initramfs as opposed to list of segments as 1807 accepted by previous system call. 1808 1809config KEXEC_VERIFY_SIG 1810 bool "Verify kernel signature during kexec_file_load() syscall" 1811 depends on KEXEC_FILE 1812 ---help--- 1813 This option makes kernel signature verification mandatory for 1814 the kexec_file_load() syscall. 1815 1816 In addition to that option, you need to enable signature 1817 verification for the corresponding kernel image type being 1818 loaded in order for this to work. 1819 1820config KEXEC_BZIMAGE_VERIFY_SIG 1821 bool "Enable bzImage signature verification support" 1822 depends on KEXEC_VERIFY_SIG 1823 depends on SIGNED_PE_FILE_VERIFICATION 1824 select SYSTEM_TRUSTED_KEYRING 1825 ---help--- 1826 Enable bzImage signature verification support. 1827 1828config CRASH_DUMP 1829 bool "kernel crash dumps" 1830 depends on X86_64 || (X86_32 && HIGHMEM) 1831 ---help--- 1832 Generate crash dump after being started by kexec. 1833 This should be normally only set in special crash dump kernels 1834 which are loaded in the main kernel with kexec-tools into 1835 a specially reserved region and then later executed after 1836 a crash by kdump/kexec. The crash dump kernel must be compiled 1837 to a memory address not used by the main kernel or BIOS using 1838 PHYSICAL_START, or it must be built as a relocatable image 1839 (CONFIG_RELOCATABLE=y). 1840 For more details see Documentation/kdump/kdump.txt 1841 1842config KEXEC_JUMP 1843 bool "kexec jump" 1844 depends on KEXEC && HIBERNATION 1845 ---help--- 1846 Jump between original kernel and kexeced kernel and invoke 1847 code in physical address mode via KEXEC 1848 1849config PHYSICAL_START 1850 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP) 1851 default "0x1000000" 1852 ---help--- 1853 This gives the physical address where the kernel is loaded. 1854 1855 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then 1856 bzImage will decompress itself to above physical address and 1857 run from there. Otherwise, bzImage will run from the address where 1858 it has been loaded by the boot loader and will ignore above physical 1859 address. 1860 1861 In normal kdump cases one does not have to set/change this option 1862 as now bzImage can be compiled as a completely relocatable image 1863 (CONFIG_RELOCATABLE=y) and be used to load and run from a different 1864 address. This option is mainly useful for the folks who don't want 1865 to use a bzImage for capturing the crash dump and want to use a 1866 vmlinux instead. vmlinux is not relocatable hence a kernel needs 1867 to be specifically compiled to run from a specific memory area 1868 (normally a reserved region) and this option comes handy. 1869 1870 So if you are using bzImage for capturing the crash dump, 1871 leave the value here unchanged to 0x1000000 and set 1872 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux 1873 for capturing the crash dump change this value to start of 1874 the reserved region. In other words, it can be set based on 1875 the "X" value as specified in the "crashkernel=YM@XM" 1876 command line boot parameter passed to the panic-ed 1877 kernel. Please take a look at Documentation/kdump/kdump.txt 1878 for more details about crash dumps. 1879 1880 Usage of bzImage for capturing the crash dump is recommended as 1881 one does not have to build two kernels. Same kernel can be used 1882 as production kernel and capture kernel. Above option should have 1883 gone away after relocatable bzImage support is introduced. But it 1884 is present because there are users out there who continue to use 1885 vmlinux for dump capture. This option should go away down the 1886 line. 1887 1888 Don't change this unless you know what you are doing. 1889 1890config RELOCATABLE 1891 bool "Build a relocatable kernel" 1892 default y 1893 ---help--- 1894 This builds a kernel image that retains relocation information 1895 so it can be loaded someplace besides the default 1MB. 1896 The relocations tend to make the kernel binary about 10% larger, 1897 but are discarded at runtime. 1898 1899 One use is for the kexec on panic case where the recovery kernel 1900 must live at a different physical address than the primary 1901 kernel. 1902 1903 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address 1904 it has been loaded at and the compile time physical address 1905 (CONFIG_PHYSICAL_START) is used as the minimum location. 1906 1907config RANDOMIZE_BASE 1908 bool "Randomize the address of the kernel image" 1909 depends on RELOCATABLE 1910 default n 1911 ---help--- 1912 Randomizes the physical and virtual address at which the 1913 kernel image is decompressed, as a security feature that 1914 deters exploit attempts relying on knowledge of the location 1915 of kernel internals. 1916 1917 Entropy is generated using the RDRAND instruction if it is 1918 supported. If RDTSC is supported, it is used as well. If 1919 neither RDRAND nor RDTSC are supported, then randomness is 1920 read from the i8254 timer. 1921 1922 The kernel will be offset by up to RANDOMIZE_BASE_MAX_OFFSET, 1923 and aligned according to PHYSICAL_ALIGN. Since the kernel is 1924 built using 2GiB addressing, and PHYSICAL_ALGIN must be at a 1925 minimum of 2MiB, only 10 bits of entropy is theoretically 1926 possible. At best, due to page table layouts, 64-bit can use 1927 9 bits of entropy and 32-bit uses 8 bits. 1928 1929 If unsure, say N. 1930 1931config RANDOMIZE_BASE_MAX_OFFSET 1932 hex "Maximum kASLR offset allowed" if EXPERT 1933 depends on RANDOMIZE_BASE 1934 range 0x0 0x20000000 if X86_32 1935 default "0x20000000" if X86_32 1936 range 0x0 0x40000000 if X86_64 1937 default "0x40000000" if X86_64 1938 ---help--- 1939 The lesser of RANDOMIZE_BASE_MAX_OFFSET and available physical 1940 memory is used to determine the maximal offset in bytes that will 1941 be applied to the kernel when kernel Address Space Layout 1942 Randomization (kASLR) is active. This must be a multiple of 1943 PHYSICAL_ALIGN. 1944 1945 On 32-bit this is limited to 512MiB by page table layouts. The 1946 default is 512MiB. 1947 1948 On 64-bit this is limited by how the kernel fixmap page table is 1949 positioned, so this cannot be larger than 1GiB currently. Without 1950 RANDOMIZE_BASE, there is a 512MiB to 1.5GiB split between kernel 1951 and modules. When RANDOMIZE_BASE_MAX_OFFSET is above 512MiB, the 1952 modules area will shrink to compensate, up to the current maximum 1953 1GiB to 1GiB split. The default is 1GiB. 1954 1955 If unsure, leave at the default value. 1956 1957# Relocation on x86 needs some additional build support 1958config X86_NEED_RELOCS 1959 def_bool y 1960 depends on RANDOMIZE_BASE || (X86_32 && RELOCATABLE) 1961 1962config PHYSICAL_ALIGN 1963 hex "Alignment value to which kernel should be aligned" 1964 default "0x200000" 1965 range 0x2000 0x1000000 if X86_32 1966 range 0x200000 0x1000000 if X86_64 1967 ---help--- 1968 This value puts the alignment restrictions on physical address 1969 where kernel is loaded and run from. Kernel is compiled for an 1970 address which meets above alignment restriction. 1971 1972 If bootloader loads the kernel at a non-aligned address and 1973 CONFIG_RELOCATABLE is set, kernel will move itself to nearest 1974 address aligned to above value and run from there. 1975 1976 If bootloader loads the kernel at a non-aligned address and 1977 CONFIG_RELOCATABLE is not set, kernel will ignore the run time 1978 load address and decompress itself to the address it has been 1979 compiled for and run from there. The address for which kernel is 1980 compiled already meets above alignment restrictions. Hence the 1981 end result is that kernel runs from a physical address meeting 1982 above alignment restrictions. 1983 1984 On 32-bit this value must be a multiple of 0x2000. On 64-bit 1985 this value must be a multiple of 0x200000. 1986 1987 Don't change this unless you know what you are doing. 1988 1989config HOTPLUG_CPU 1990 bool "Support for hot-pluggable CPUs" 1991 depends on SMP 1992 ---help--- 1993 Say Y here to allow turning CPUs off and on. CPUs can be 1994 controlled through /sys/devices/system/cpu. 1995 ( Note: power management support will enable this option 1996 automatically on SMP systems. ) 1997 Say N if you want to disable CPU hotplug. 1998 1999config BOOTPARAM_HOTPLUG_CPU0 2000 bool "Set default setting of cpu0_hotpluggable" 2001 default n 2002 depends on HOTPLUG_CPU 2003 ---help--- 2004 Set whether default state of cpu0_hotpluggable is on or off. 2005 2006 Say Y here to enable CPU0 hotplug by default. If this switch 2007 is turned on, there is no need to give cpu0_hotplug kernel 2008 parameter and the CPU0 hotplug feature is enabled by default. 2009 2010 Please note: there are two known CPU0 dependencies if you want 2011 to enable the CPU0 hotplug feature either by this switch or by 2012 cpu0_hotplug kernel parameter. 2013 2014 First, resume from hibernate or suspend always starts from CPU0. 2015 So hibernate and suspend are prevented if CPU0 is offline. 2016 2017 Second dependency is PIC interrupts always go to CPU0. CPU0 can not 2018 offline if any interrupt can not migrate out of CPU0. There may 2019 be other CPU0 dependencies. 2020 2021 Please make sure the dependencies are under your control before 2022 you enable this feature. 2023 2024 Say N if you don't want to enable CPU0 hotplug feature by default. 2025 You still can enable the CPU0 hotplug feature at boot by kernel 2026 parameter cpu0_hotplug. 2027 2028config DEBUG_HOTPLUG_CPU0 2029 def_bool n 2030 prompt "Debug CPU0 hotplug" 2031 depends on HOTPLUG_CPU 2032 ---help--- 2033 Enabling this option offlines CPU0 (if CPU0 can be offlined) as 2034 soon as possible and boots up userspace with CPU0 offlined. User 2035 can online CPU0 back after boot time. 2036 2037 To debug CPU0 hotplug, you need to enable CPU0 offline/online 2038 feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during 2039 compilation or giving cpu0_hotplug kernel parameter at boot. 2040 2041 If unsure, say N. 2042 2043config COMPAT_VDSO 2044 def_bool n 2045 prompt "Disable the 32-bit vDSO (needed for glibc 2.3.3)" 2046 depends on X86_32 || IA32_EMULATION 2047 ---help--- 2048 Certain buggy versions of glibc will crash if they are 2049 presented with a 32-bit vDSO that is not mapped at the address 2050 indicated in its segment table. 2051 2052 The bug was introduced by f866314b89d56845f55e6f365e18b31ec978ec3a 2053 and fixed by 3b3ddb4f7db98ec9e912ccdf54d35df4aa30e04a and 2054 49ad572a70b8aeb91e57483a11dd1b77e31c4468. Glibc 2.3.3 is 2055 the only released version with the bug, but OpenSUSE 9 2056 contains a buggy "glibc 2.3.2". 2057 2058 The symptom of the bug is that everything crashes on startup, saying: 2059 dl_main: Assertion `(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed! 2060 2061 Saying Y here changes the default value of the vdso32 boot 2062 option from 1 to 0, which turns off the 32-bit vDSO entirely. 2063 This works around the glibc bug but hurts performance. 2064 2065 If unsure, say N: if you are compiling your own kernel, you 2066 are unlikely to be using a buggy version of glibc. 2067 2068choice 2069 prompt "vsyscall table for legacy applications" 2070 depends on X86_64 2071 default LEGACY_VSYSCALL_EMULATE 2072 help 2073 Legacy user code that does not know how to find the vDSO expects 2074 to be able to issue three syscalls by calling fixed addresses in 2075 kernel space. Since this location is not randomized with ASLR, 2076 it can be used to assist security vulnerability exploitation. 2077 2078 This setting can be changed at boot time via the kernel command 2079 line parameter vsyscall=[native|emulate|none]. 2080 2081 On a system with recent enough glibc (2.14 or newer) and no 2082 static binaries, you can say None without a performance penalty 2083 to improve security. 2084 2085 If unsure, select "Emulate". 2086 2087 config LEGACY_VSYSCALL_NATIVE 2088 bool "Native" 2089 help 2090 Actual executable code is located in the fixed vsyscall 2091 address mapping, implementing time() efficiently. Since 2092 this makes the mapping executable, it can be used during 2093 security vulnerability exploitation (traditionally as 2094 ROP gadgets). This configuration is not recommended. 2095 2096 config LEGACY_VSYSCALL_EMULATE 2097 bool "Emulate" 2098 help 2099 The kernel traps and emulates calls into the fixed 2100 vsyscall address mapping. This makes the mapping 2101 non-executable, but it still contains known contents, 2102 which could be used in certain rare security vulnerability 2103 exploits. This configuration is recommended when userspace 2104 still uses the vsyscall area. 2105 2106 config LEGACY_VSYSCALL_NONE 2107 bool "None" 2108 help 2109 There will be no vsyscall mapping at all. This will 2110 eliminate any risk of ASLR bypass due to the vsyscall 2111 fixed address mapping. Attempts to use the vsyscalls 2112 will be reported to dmesg, so that either old or 2113 malicious userspace programs can be identified. 2114 2115endchoice 2116 2117config CMDLINE_BOOL 2118 bool "Built-in kernel command line" 2119 ---help--- 2120 Allow for specifying boot arguments to the kernel at 2121 build time. On some systems (e.g. embedded ones), it is 2122 necessary or convenient to provide some or all of the 2123 kernel boot arguments with the kernel itself (that is, 2124 to not rely on the boot loader to provide them.) 2125 2126 To compile command line arguments into the kernel, 2127 set this option to 'Y', then fill in the 2128 boot arguments in CONFIG_CMDLINE. 2129 2130 Systems with fully functional boot loaders (i.e. non-embedded) 2131 should leave this option set to 'N'. 2132 2133config CMDLINE 2134 string "Built-in kernel command string" 2135 depends on CMDLINE_BOOL 2136 default "" 2137 ---help--- 2138 Enter arguments here that should be compiled into the kernel 2139 image and used at boot time. If the boot loader provides a 2140 command line at boot time, it is appended to this string to 2141 form the full kernel command line, when the system boots. 2142 2143 However, you can use the CONFIG_CMDLINE_OVERRIDE option to 2144 change this behavior. 2145 2146 In most cases, the command line (whether built-in or provided 2147 by the boot loader) should specify the device for the root 2148 file system. 2149 2150config CMDLINE_OVERRIDE 2151 bool "Built-in command line overrides boot loader arguments" 2152 depends on CMDLINE_BOOL 2153 ---help--- 2154 Set this option to 'Y' to have the kernel ignore the boot loader 2155 command line, and use ONLY the built-in command line. 2156 2157 This is used to work around broken boot loaders. This should 2158 be set to 'N' under normal conditions. 2159 2160config MODIFY_LDT_SYSCALL 2161 bool "Enable the LDT (local descriptor table)" if EXPERT 2162 default y 2163 ---help--- 2164 Linux can allow user programs to install a per-process x86 2165 Local Descriptor Table (LDT) using the modify_ldt(2) system 2166 call. This is required to run 16-bit or segmented code such as 2167 DOSEMU or some Wine programs. It is also used by some very old 2168 threading libraries. 2169 2170 Enabling this feature adds a small amount of overhead to 2171 context switches and increases the low-level kernel attack 2172 surface. Disabling it removes the modify_ldt(2) system call. 2173 2174 Saying 'N' here may make sense for embedded or server kernels. 2175 2176source "kernel/livepatch/Kconfig" 2177 2178endmenu 2179 2180config ARCH_ENABLE_MEMORY_HOTPLUG 2181 def_bool y 2182 depends on X86_64 || (X86_32 && HIGHMEM) 2183 2184config ARCH_ENABLE_MEMORY_HOTREMOVE 2185 def_bool y 2186 depends on MEMORY_HOTPLUG 2187 2188config USE_PERCPU_NUMA_NODE_ID 2189 def_bool y 2190 depends on NUMA 2191 2192config ARCH_ENABLE_SPLIT_PMD_PTLOCK 2193 def_bool y 2194 depends on X86_64 || X86_PAE 2195 2196config ARCH_ENABLE_HUGEPAGE_MIGRATION 2197 def_bool y 2198 depends on X86_64 && HUGETLB_PAGE && MIGRATION 2199 2200menu "Power management and ACPI options" 2201 2202config ARCH_HIBERNATION_HEADER 2203 def_bool y 2204 depends on X86_64 && HIBERNATION 2205 2206source "kernel/power/Kconfig" 2207 2208source "drivers/acpi/Kconfig" 2209 2210source "drivers/sfi/Kconfig" 2211 2212config X86_APM_BOOT 2213 def_bool y 2214 depends on APM 2215 2216menuconfig APM 2217 tristate "APM (Advanced Power Management) BIOS support" 2218 depends on X86_32 && PM_SLEEP 2219 ---help--- 2220 APM is a BIOS specification for saving power using several different 2221 techniques. This is mostly useful for battery powered laptops with 2222 APM compliant BIOSes. If you say Y here, the system time will be 2223 reset after a RESUME operation, the /proc/apm device will provide 2224 battery status information, and user-space programs will receive 2225 notification of APM "events" (e.g. battery status change). 2226 2227 If you select "Y" here, you can disable actual use of the APM 2228 BIOS by passing the "apm=off" option to the kernel at boot time. 2229 2230 Note that the APM support is almost completely disabled for 2231 machines with more than one CPU. 2232 2233 In order to use APM, you will need supporting software. For location 2234 and more information, read <file:Documentation/power/apm-acpi.txt> 2235 and the Battery Powered Linux mini-HOWTO, available from 2236 <http://www.tldp.org/docs.html#howto>. 2237 2238 This driver does not spin down disk drives (see the hdparm(8) 2239 manpage ("man 8 hdparm") for that), and it doesn't turn off 2240 VESA-compliant "green" monitors. 2241 2242 This driver does not support the TI 4000M TravelMate and the ACER 2243 486/DX4/75 because they don't have compliant BIOSes. Many "green" 2244 desktop machines also don't have compliant BIOSes, and this driver 2245 may cause those machines to panic during the boot phase. 2246 2247 Generally, if you don't have a battery in your machine, there isn't 2248 much point in using this driver and you should say N. If you get 2249 random kernel OOPSes or reboots that don't seem to be related to 2250 anything, try disabling/enabling this option (or disabling/enabling 2251 APM in your BIOS). 2252 2253 Some other things you should try when experiencing seemingly random, 2254 "weird" problems: 2255 2256 1) make sure that you have enough swap space and that it is 2257 enabled. 2258 2) pass the "no-hlt" option to the kernel 2259 3) switch on floating point emulation in the kernel and pass 2260 the "no387" option to the kernel 2261 4) pass the "floppy=nodma" option to the kernel 2262 5) pass the "mem=4M" option to the kernel (thereby disabling 2263 all but the first 4 MB of RAM) 2264 6) make sure that the CPU is not over clocked. 2265 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/> 2266 8) disable the cache from your BIOS settings 2267 9) install a fan for the video card or exchange video RAM 2268 10) install a better fan for the CPU 2269 11) exchange RAM chips 2270 12) exchange the motherboard. 2271 2272 To compile this driver as a module, choose M here: the 2273 module will be called apm. 2274 2275if APM 2276 2277config APM_IGNORE_USER_SUSPEND 2278 bool "Ignore USER SUSPEND" 2279 ---help--- 2280 This option will ignore USER SUSPEND requests. On machines with a 2281 compliant APM BIOS, you want to say N. However, on the NEC Versa M 2282 series notebooks, it is necessary to say Y because of a BIOS bug. 2283 2284config APM_DO_ENABLE 2285 bool "Enable PM at boot time" 2286 ---help--- 2287 Enable APM features at boot time. From page 36 of the APM BIOS 2288 specification: "When disabled, the APM BIOS does not automatically 2289 power manage devices, enter the Standby State, enter the Suspend 2290 State, or take power saving steps in response to CPU Idle calls." 2291 This driver will make CPU Idle calls when Linux is idle (unless this 2292 feature is turned off -- see "Do CPU IDLE calls", below). This 2293 should always save battery power, but more complicated APM features 2294 will be dependent on your BIOS implementation. You may need to turn 2295 this option off if your computer hangs at boot time when using APM 2296 support, or if it beeps continuously instead of suspending. Turn 2297 this off if you have a NEC UltraLite Versa 33/C or a Toshiba 2298 T400CDT. This is off by default since most machines do fine without 2299 this feature. 2300 2301config APM_CPU_IDLE 2302 depends on CPU_IDLE 2303 bool "Make CPU Idle calls when idle" 2304 ---help--- 2305 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop. 2306 On some machines, this can activate improved power savings, such as 2307 a slowed CPU clock rate, when the machine is idle. These idle calls 2308 are made after the idle loop has run for some length of time (e.g., 2309 333 mS). On some machines, this will cause a hang at boot time or 2310 whenever the CPU becomes idle. (On machines with more than one CPU, 2311 this option does nothing.) 2312 2313config APM_DISPLAY_BLANK 2314 bool "Enable console blanking using APM" 2315 ---help--- 2316 Enable console blanking using the APM. Some laptops can use this to 2317 turn off the LCD backlight when the screen blanker of the Linux 2318 virtual console blanks the screen. Note that this is only used by 2319 the virtual console screen blanker, and won't turn off the backlight 2320 when using the X Window system. This also doesn't have anything to 2321 do with your VESA-compliant power-saving monitor. Further, this 2322 option doesn't work for all laptops -- it might not turn off your 2323 backlight at all, or it might print a lot of errors to the console, 2324 especially if you are using gpm. 2325 2326config APM_ALLOW_INTS 2327 bool "Allow interrupts during APM BIOS calls" 2328 ---help--- 2329 Normally we disable external interrupts while we are making calls to 2330 the APM BIOS as a measure to lessen the effects of a badly behaving 2331 BIOS implementation. The BIOS should reenable interrupts if it 2332 needs to. Unfortunately, some BIOSes do not -- especially those in 2333 many of the newer IBM Thinkpads. If you experience hangs when you 2334 suspend, try setting this to Y. Otherwise, say N. 2335 2336endif # APM 2337 2338source "drivers/cpufreq/Kconfig" 2339 2340source "drivers/cpuidle/Kconfig" 2341 2342source "drivers/idle/Kconfig" 2343 2344endmenu 2345 2346 2347menu "Bus options (PCI etc.)" 2348 2349config PCI 2350 bool "PCI support" 2351 default y 2352 ---help--- 2353 Find out whether you have a PCI motherboard. PCI is the name of a 2354 bus system, i.e. the way the CPU talks to the other stuff inside 2355 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or 2356 VESA. If you have PCI, say Y, otherwise N. 2357 2358choice 2359 prompt "PCI access mode" 2360 depends on X86_32 && PCI 2361 default PCI_GOANY 2362 ---help--- 2363 On PCI systems, the BIOS can be used to detect the PCI devices and 2364 determine their configuration. However, some old PCI motherboards 2365 have BIOS bugs and may crash if this is done. Also, some embedded 2366 PCI-based systems don't have any BIOS at all. Linux can also try to 2367 detect the PCI hardware directly without using the BIOS. 2368 2369 With this option, you can specify how Linux should detect the 2370 PCI devices. If you choose "BIOS", the BIOS will be used, 2371 if you choose "Direct", the BIOS won't be used, and if you 2372 choose "MMConfig", then PCI Express MMCONFIG will be used. 2373 If you choose "Any", the kernel will try MMCONFIG, then the 2374 direct access method and falls back to the BIOS if that doesn't 2375 work. If unsure, go with the default, which is "Any". 2376 2377config PCI_GOBIOS 2378 bool "BIOS" 2379 2380config PCI_GOMMCONFIG 2381 bool "MMConfig" 2382 2383config PCI_GODIRECT 2384 bool "Direct" 2385 2386config PCI_GOOLPC 2387 bool "OLPC XO-1" 2388 depends on OLPC 2389 2390config PCI_GOANY 2391 bool "Any" 2392 2393endchoice 2394 2395config PCI_BIOS 2396 def_bool y 2397 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY) 2398 2399# x86-64 doesn't support PCI BIOS access from long mode so always go direct. 2400config PCI_DIRECT 2401 def_bool y 2402 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG)) 2403 2404config PCI_MMCONFIG 2405 def_bool y 2406 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY) 2407 2408config PCI_OLPC 2409 def_bool y 2410 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY) 2411 2412config PCI_XEN 2413 def_bool y 2414 depends on PCI && XEN 2415 select SWIOTLB_XEN 2416 2417config PCI_DOMAINS 2418 def_bool y 2419 depends on PCI 2420 2421config PCI_MMCONFIG 2422 bool "Support mmconfig PCI config space access" 2423 depends on X86_64 && PCI && ACPI 2424 2425config PCI_CNB20LE_QUIRK 2426 bool "Read CNB20LE Host Bridge Windows" if EXPERT 2427 depends on PCI 2428 help 2429 Read the PCI windows out of the CNB20LE host bridge. This allows 2430 PCI hotplug to work on systems with the CNB20LE chipset which do 2431 not have ACPI. 2432 2433 There's no public spec for this chipset, and this functionality 2434 is known to be incomplete. 2435 2436 You should say N unless you know you need this. 2437 2438source "drivers/pci/Kconfig" 2439 2440# x86_64 have no ISA slots, but can have ISA-style DMA. 2441config ISA_DMA_API 2442 bool "ISA-style DMA support" if (X86_64 && EXPERT) 2443 default y 2444 help 2445 Enables ISA-style DMA support for devices requiring such controllers. 2446 If unsure, say Y. 2447 2448if X86_32 2449 2450config ISA 2451 bool "ISA support" 2452 ---help--- 2453 Find out whether you have ISA slots on your motherboard. ISA is the 2454 name of a bus system, i.e. the way the CPU talks to the other stuff 2455 inside your box. Other bus systems are PCI, EISA, MicroChannel 2456 (MCA) or VESA. ISA is an older system, now being displaced by PCI; 2457 newer boards don't support it. If you have ISA, say Y, otherwise N. 2458 2459config EISA 2460 bool "EISA support" 2461 depends on ISA 2462 ---help--- 2463 The Extended Industry Standard Architecture (EISA) bus was 2464 developed as an open alternative to the IBM MicroChannel bus. 2465 2466 The EISA bus provided some of the features of the IBM MicroChannel 2467 bus while maintaining backward compatibility with cards made for 2468 the older ISA bus. The EISA bus saw limited use between 1988 and 2469 1995 when it was made obsolete by the PCI bus. 2470 2471 Say Y here if you are building a kernel for an EISA-based machine. 2472 2473 Otherwise, say N. 2474 2475source "drivers/eisa/Kconfig" 2476 2477config SCx200 2478 tristate "NatSemi SCx200 support" 2479 ---help--- 2480 This provides basic support for National Semiconductor's 2481 (now AMD's) Geode processors. The driver probes for the 2482 PCI-IDs of several on-chip devices, so its a good dependency 2483 for other scx200_* drivers. 2484 2485 If compiled as a module, the driver is named scx200. 2486 2487config SCx200HR_TIMER 2488 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support" 2489 depends on SCx200 2490 default y 2491 ---help--- 2492 This driver provides a clocksource built upon the on-chip 2493 27MHz high-resolution timer. Its also a workaround for 2494 NSC Geode SC-1100's buggy TSC, which loses time when the 2495 processor goes idle (as is done by the scheduler). The 2496 other workaround is idle=poll boot option. 2497 2498config OLPC 2499 bool "One Laptop Per Child support" 2500 depends on !X86_PAE 2501 select GPIOLIB 2502 select OF 2503 select OF_PROMTREE 2504 select IRQ_DOMAIN 2505 ---help--- 2506 Add support for detecting the unique features of the OLPC 2507 XO hardware. 2508 2509config OLPC_XO1_PM 2510 bool "OLPC XO-1 Power Management" 2511 depends on OLPC && MFD_CS5535 && PM_SLEEP 2512 select MFD_CORE 2513 ---help--- 2514 Add support for poweroff and suspend of the OLPC XO-1 laptop. 2515 2516config OLPC_XO1_RTC 2517 bool "OLPC XO-1 Real Time Clock" 2518 depends on OLPC_XO1_PM && RTC_DRV_CMOS 2519 ---help--- 2520 Add support for the XO-1 real time clock, which can be used as a 2521 programmable wakeup source. 2522 2523config OLPC_XO1_SCI 2524 bool "OLPC XO-1 SCI extras" 2525 depends on OLPC && OLPC_XO1_PM 2526 depends on INPUT=y 2527 select POWER_SUPPLY 2528 select GPIO_CS5535 2529 select MFD_CORE 2530 ---help--- 2531 Add support for SCI-based features of the OLPC XO-1 laptop: 2532 - EC-driven system wakeups 2533 - Power button 2534 - Ebook switch 2535 - Lid switch 2536 - AC adapter status updates 2537 - Battery status updates 2538 2539config OLPC_XO15_SCI 2540 bool "OLPC XO-1.5 SCI extras" 2541 depends on OLPC && ACPI 2542 select POWER_SUPPLY 2543 ---help--- 2544 Add support for SCI-based features of the OLPC XO-1.5 laptop: 2545 - EC-driven system wakeups 2546 - AC adapter status updates 2547 - Battery status updates 2548 2549config ALIX 2550 bool "PCEngines ALIX System Support (LED setup)" 2551 select GPIOLIB 2552 ---help--- 2553 This option enables system support for the PCEngines ALIX. 2554 At present this just sets up LEDs for GPIO control on 2555 ALIX2/3/6 boards. However, other system specific setup should 2556 get added here. 2557 2558 Note: You must still enable the drivers for GPIO and LED support 2559 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs 2560 2561 Note: You have to set alix.force=1 for boards with Award BIOS. 2562 2563config NET5501 2564 bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)" 2565 select GPIOLIB 2566 ---help--- 2567 This option enables system support for the Soekris Engineering net5501. 2568 2569config GEOS 2570 bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)" 2571 select GPIOLIB 2572 depends on DMI 2573 ---help--- 2574 This option enables system support for the Traverse Technologies GEOS. 2575 2576config TS5500 2577 bool "Technologic Systems TS-5500 platform support" 2578 depends on MELAN 2579 select CHECK_SIGNATURE 2580 select NEW_LEDS 2581 select LEDS_CLASS 2582 ---help--- 2583 This option enables system support for the Technologic Systems TS-5500. 2584 2585endif # X86_32 2586 2587config AMD_NB 2588 def_bool y 2589 depends on CPU_SUP_AMD && PCI 2590 2591source "drivers/pcmcia/Kconfig" 2592 2593config RAPIDIO 2594 tristate "RapidIO support" 2595 depends on PCI 2596 default n 2597 help 2598 If enabled this option will include drivers and the core 2599 infrastructure code to support RapidIO interconnect devices. 2600 2601source "drivers/rapidio/Kconfig" 2602 2603config X86_SYSFB 2604 bool "Mark VGA/VBE/EFI FB as generic system framebuffer" 2605 help 2606 Firmwares often provide initial graphics framebuffers so the BIOS, 2607 bootloader or kernel can show basic video-output during boot for 2608 user-guidance and debugging. Historically, x86 used the VESA BIOS 2609 Extensions and EFI-framebuffers for this, which are mostly limited 2610 to x86. 2611 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic 2612 framebuffers so the new generic system-framebuffer drivers can be 2613 used on x86. If the framebuffer is not compatible with the generic 2614 modes, it is adverticed as fallback platform framebuffer so legacy 2615 drivers like efifb, vesafb and uvesafb can pick it up. 2616 If this option is not selected, all system framebuffers are always 2617 marked as fallback platform framebuffers as usual. 2618 2619 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will 2620 not be able to pick up generic system framebuffers if this option 2621 is selected. You are highly encouraged to enable simplefb as 2622 replacement if you select this option. simplefb can correctly deal 2623 with generic system framebuffers. But you should still keep vesafb 2624 and others enabled as fallback if a system framebuffer is 2625 incompatible with simplefb. 2626 2627 If unsure, say Y. 2628 2629endmenu 2630 2631 2632menu "Executable file formats / Emulations" 2633 2634source "fs/Kconfig.binfmt" 2635 2636config IA32_EMULATION 2637 bool "IA32 Emulation" 2638 depends on X86_64 2639 select BINFMT_ELF 2640 select COMPAT_BINFMT_ELF 2641 select ARCH_WANT_OLD_COMPAT_IPC 2642 ---help--- 2643 Include code to run legacy 32-bit programs under a 2644 64-bit kernel. You should likely turn this on, unless you're 2645 100% sure that you don't have any 32-bit programs left. 2646 2647config IA32_AOUT 2648 tristate "IA32 a.out support" 2649 depends on IA32_EMULATION 2650 ---help--- 2651 Support old a.out binaries in the 32bit emulation. 2652 2653config X86_X32 2654 bool "x32 ABI for 64-bit mode" 2655 depends on X86_64 2656 ---help--- 2657 Include code to run binaries for the x32 native 32-bit ABI 2658 for 64-bit processors. An x32 process gets access to the 2659 full 64-bit register file and wide data path while leaving 2660 pointers at 32 bits for smaller memory footprint. 2661 2662 You will need a recent binutils (2.22 or later) with 2663 elf32_x86_64 support enabled to compile a kernel with this 2664 option set. 2665 2666config COMPAT 2667 def_bool y 2668 depends on IA32_EMULATION || X86_X32 2669 2670if COMPAT 2671config COMPAT_FOR_U64_ALIGNMENT 2672 def_bool y 2673 2674config SYSVIPC_COMPAT 2675 def_bool y 2676 depends on SYSVIPC 2677 2678config KEYS_COMPAT 2679 def_bool y 2680 depends on KEYS 2681endif 2682 2683endmenu 2684 2685 2686config HAVE_ATOMIC_IOMAP 2687 def_bool y 2688 depends on X86_32 2689 2690config X86_DEV_DMA_OPS 2691 bool 2692 depends on X86_64 || STA2X11 2693 2694config X86_DMA_REMAP 2695 bool 2696 depends on STA2X11 2697 2698config PMC_ATOM 2699 def_bool y 2700 depends on PCI 2701 2702config VMD 2703 depends on PCI_MSI 2704 tristate "Volume Management Device Driver" 2705 default N 2706 ---help--- 2707 Adds support for the Intel Volume Management Device (VMD). VMD is a 2708 secondary PCI host bridge that allows PCI Express root ports, 2709 and devices attached to them, to be removed from the default 2710 PCI domain and placed within the VMD domain. This provides 2711 more bus resources than are otherwise possible with a 2712 single domain. If you know your system provides one of these and 2713 has devices attached to it, say Y; if you are not sure, say N. 2714 2715source "net/Kconfig" 2716 2717source "drivers/Kconfig" 2718 2719source "drivers/firmware/Kconfig" 2720 2721source "fs/Kconfig" 2722 2723source "arch/x86/Kconfig.debug" 2724 2725source "security/Kconfig" 2726 2727source "crypto/Kconfig" 2728 2729source "arch/x86/kvm/Kconfig" 2730 2731source "lib/Kconfig" 2732