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