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