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