arch/x86_64/Kconfig

   1 #
   2 # For a description of the syntax of this configuration file,
   3 # see Documentation/kbuild/kconfig-language.txt.
   4 #
   5 # Note: ISA is disabled and will hopefully never be enabled.
   6 # If you managed to buy an ISA x86-64 box you'll have to fix all the
   7 # ISA drivers you need yourself.
   8 #
   9
  10 mainmenu "Linux Kernel Configuration"
  11
  12 config X86_64
  13         bool
  14         default y
  15         help
  16           Port to the x86-64 architecture. x86-64 is a 64-bit extension to the
  17           classical 32-bit x86 architecture. For details see
  18           <http://www.x86-64.org/>.
  19
  20 config 64BIT
  21         def_bool y
  22
  23 config X86
  24         bool
  25         default y
  26
  27 config ZONE_DMA32
  28         bool
  29         default y
  30
  31 config LOCKDEP_SUPPORT
  32         bool
  33         default y
  34
  35 config STACKTRACE_SUPPORT
  36         bool
  37         default y
  38
  39 config SEMAPHORE_SLEEPERS
  40         bool
  41         default y
  42
  43 config MMU
  44         bool
  45         default y
  46
  47 config ISA
  48         bool
  49
  50 config SBUS
  51         bool
  52
  53 config RWSEM_GENERIC_SPINLOCK
  54         bool
  55         default y
  56
  57 config RWSEM_XCHGADD_ALGORITHM
  58         bool
  59
  60 config GENERIC_HWEIGHT
  61         bool
  62         default y
  63
  64 config GENERIC_CALIBRATE_DELAY
  65         bool
  66         default y
  67
  68 config X86_CMPXCHG
  69         bool
  70         default y
  71
  72 config EARLY_PRINTK
  73         bool
  74         default y
  75
  76 config GENERIC_ISA_DMA
  77         bool
  78         default y
  79
  80 config GENERIC_IOMAP
  81         bool
  82         default y
  83
  84 config ARCH_MAY_HAVE_PC_FDC
  85         bool
  86         default y
  87
  88 config ARCH_POPULATES_NODE_MAP
  89         def_bool y
  90
  91 config DMI
  92         bool
  93         default y
  94
  95 config AUDIT_ARCH
  96         bool
  97         default y
  98
  99 source "init/Kconfig"
 100
 101
 102 menu "Processor type and features"
 103
 104 choice
 105         prompt "Subarchitecture Type"
 106         default X86_PC
 107
 108 config X86_PC
 109         bool "PC-compatible"
 110         help
 111           Choose this option if your computer is a standard PC or compatible.
 112
 113 config X86_VSMP
 114         bool "Support for ScaleMP vSMP"
 115         depends on PCI
 116          help
 117           Support for ScaleMP vSMP systems.  Say 'Y' here if this kernel is
 118           supposed to run on these EM64T-based machines.  Only choose this option
 119           if you have one of these machines.
 120
 121 endchoice
 122
 123 choice
 124         prompt "Processor family"
 125         default MK8
 126
 127 config MK8
 128         bool "AMD-Opteron/Athlon64"
 129         help
 130           Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
 131
 132 config MPSC
 133        bool "Intel EM64T"
 134        help
 135           Optimize for Intel Pentium 4 and Xeon CPUs with Intel
 136           Extended Memory 64 Technology(EM64T). For details see
 137           <http://www.intel.com/technology/64bitextensions/>.
 138
 139 config GENERIC_CPU
 140         bool "Generic-x86-64"
 141         help
 142           Generic x86-64 CPU.
 143
 144 endchoice
 145
 146 #
 147 # Define implied options from the CPU selection here
 148 #
 149 config X86_L1_CACHE_BYTES
 150         int
 151         default "128" if GENERIC_CPU || MPSC
 152         default "64" if MK8
 153
 154 config X86_L1_CACHE_SHIFT
 155         int
 156         default "7" if GENERIC_CPU || MPSC
 157         default "6" if MK8
 158
 159 config X86_INTERNODE_CACHE_BYTES
 160         int
 161         default "4096" if X86_VSMP
 162         default X86_L1_CACHE_BYTES if !X86_VSMP
 163
 164 config X86_TSC
 165         bool
 166         default y
 167
 168 config X86_GOOD_APIC
 169         bool
 170         default y
 171
 172 config MICROCODE
 173         tristate "/dev/cpu/microcode - Intel CPU microcode support"
 174         select FW_LOADER
 175         ---help---
 176           If you say Y here the 'File systems' section, you will be
 177           able to update the microcode on Intel processors. You will
 178           obviously need the actual microcode binary data itself which is
 179           not shipped with the Linux kernel.
 180
 181           For latest news and information on obtaining all the required
 182           ingredients for this driver, check:
 183           <http://www.urbanmyth.org/microcode/>.
 184
 185           To compile this driver as a module, choose M here: the
 186           module will be called microcode.
 187           If you use modprobe or kmod you may also want to add the line
 188           'alias char-major-10-184 microcode' to your /etc/modules.conf file.
 189
 190 config MICROCODE_OLD_INTERFACE
 191         bool
 192         depends on MICROCODE
 193         default y
 194
 195 config X86_MSR
 196         tristate "/dev/cpu/*/msr - Model-specific register support"
 197         help
 198           This device gives privileged processes access to the x86
 199           Model-Specific Registers (MSRs).  It is a character device with
 200           major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
 201           MSR accesses are directed to a specific CPU on multi-processor
 202           systems.
 203
 204 config X86_CPUID
 205         tristate "/dev/cpu/*/cpuid - CPU information support"
 206         help
 207           This device gives processes access to the x86 CPUID instruction to
 208           be executed on a specific processor.  It is a character device
 209           with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
 210           /dev/cpu/31/cpuid.
 211
 212 config X86_HT
 213         bool
 214         depends on SMP && !MK8
 215         default y
 216
 217 config MATH_EMULATION
 218         bool
 219
 220 config MCA
 221         bool
 222
 223 config EISA
 224         bool
 225
 226 config X86_IO_APIC
 227         bool
 228         default y
 229
 230 config X86_LOCAL_APIC
 231         bool
 232         default y
 233
 234 config MTRR
 235         bool "MTRR (Memory Type Range Register) support"
 236         ---help---
 237           On Intel P6 family processors (Pentium Pro, Pentium II and later)
 238           the Memory Type Range Registers (MTRRs) may be used to control
 239           processor access to memory ranges. This is most useful if you have
 240           a video (VGA) card on a PCI or AGP bus. Enabling write-combining
 241           allows bus write transfers to be combined into a larger transfer
 242           before bursting over the PCI/AGP bus. This can increase performance
 243           of image write operations 2.5 times or more. Saying Y here creates a
 244           /proc/mtrr file which may be used to manipulate your processor's
 245           MTRRs. Typically the X server should use this.
 246
 247           This code has a reasonably generic interface so that similar
 248           control registers on other processors can be easily supported
 249           as well.
 250
 251           Saying Y here also fixes a problem with buggy SMP BIOSes which only
 252           set the MTRRs for the boot CPU and not for the secondary CPUs. This
 253           can lead to all sorts of problems, so it's good to say Y here.
 254
 255           Just say Y here, all x86-64 machines support MTRRs.
 256
 257           See <file:Documentation/mtrr.txt> for more information.
 258
 259 config SMP
 260         bool "Symmetric multi-processing support"
 261         ---help---
 262           This enables support for systems with more than one CPU. If you have
 263           a system with only one CPU, like most personal computers, say N. If
 264           you have a system with more than one CPU, say Y.
 265
 266           If you say N here, the kernel will run on single and multiprocessor
 267           machines, but will use only one CPU of a multiprocessor machine. If
 268           you say Y here, the kernel will run on many, but not all,
 269           singleprocessor machines. On a singleprocessor machine, the kernel
 270           will run faster if you say N here.
 271
 272           If you don't know what to do here, say N.
 273
 274 config SCHED_SMT
 275         bool "SMT (Hyperthreading) scheduler support"
 276         depends on SMP
 277         default n
 278         help
 279           SMT scheduler support improves the CPU scheduler's decision making
 280           when dealing with Intel Pentium 4 chips with HyperThreading at a
 281           cost of slightly increased overhead in some places. If unsure say
 282           N here.
 283
 284 config SCHED_MC
 285         bool "Multi-core scheduler support"
 286         depends on SMP
 287         default y
 288         help
 289           Multi-core scheduler support improves the CPU scheduler's decision
 290           making when dealing with multi-core CPU chips at a cost of slightly
 291           increased overhead in some places. If unsure say N here.
 292
 293 source "kernel/Kconfig.preempt"
 294
 295 config NUMA
 296        bool "Non Uniform Memory Access (NUMA) Support"
 297        depends on SMP
 298        help
 299          Enable NUMA (Non Uniform Memory Access) support. The kernel
 300          will try to allocate memory used by a CPU on the local memory
 301          controller of the CPU and add some more NUMA awareness to the kernel.
 302          This code is recommended on all multiprocessor Opteron systems.
 303          If the system is EM64T, you should say N unless your system is EM64T
 304          NUMA.
 305
 306 config K8_NUMA
 307        bool "Old style AMD Opteron NUMA detection"
 308        depends on NUMA && PCI
 309        default y
 310        help
 311          Enable K8 NUMA node topology detection.  You should say Y here if
 312          you have a multi processor AMD K8 system. This uses an old
 313          method to read the NUMA configurtion directly from the builtin
 314          Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
 315          instead, which also takes priority if both are compiled in.
 316
 317 config NODES_SHIFT
 318         int
 319         default "6"
 320         depends on NEED_MULTIPLE_NODES
 321
 322 # Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.
 323
 324 config X86_64_ACPI_NUMA
 325        bool "ACPI NUMA detection"
 326        depends on NUMA
 327        select ACPI
 328         select PCI
 329        select ACPI_NUMA
 330        default y
 331        help
 332          Enable ACPI SRAT based node topology detection.
 333
 334 config NUMA_EMU
 335         bool "NUMA emulation"
 336         depends on NUMA
 337         help
 338           Enable NUMA emulation. A flat machine will be split
 339           into virtual nodes when booted with "numa=fake=N", where N is the
 340           number of nodes. This is only useful for debugging.
 341
 342 config ARCH_DISCONTIGMEM_ENABLE
 343        bool
 344        depends on NUMA
 345        default y
 346
 347
 348 config ARCH_DISCONTIGMEM_ENABLE
 349         def_bool y
 350         depends on NUMA
 351
 352 config ARCH_DISCONTIGMEM_DEFAULT
 353         def_bool y
 354         depends on NUMA
 355
 356 config ARCH_SPARSEMEM_ENABLE
 357         def_bool y
 358         depends on (NUMA || EXPERIMENTAL)
 359
 360 config ARCH_MEMORY_PROBE
 361         def_bool y
 362         depends on MEMORY_HOTPLUG
 363
 364 config ARCH_FLATMEM_ENABLE
 365         def_bool y
 366         depends on !NUMA
 367
 368 source "mm/Kconfig"
 369
 370 config MEMORY_HOTPLUG_RESERVE
 371         def_bool y
 372         depends on (MEMORY_HOTPLUG && DISCONTIGMEM)
 373
 374 config HAVE_ARCH_EARLY_PFN_TO_NID
 375         def_bool y
 376         depends on NUMA
 377
 378 config OUT_OF_LINE_PFN_TO_PAGE
 379         def_bool y
 380         depends on DISCONTIGMEM
 381
 382 config NR_CPUS
 383         int "Maximum number of CPUs (2-256)"
 384         range 2 255
 385         depends on SMP
 386         default "8"
 387         help
 388           This allows you to specify the maximum number of CPUs which this
 389           kernel will support. Current maximum is 256 CPUs due to
 390           APIC addressing limits. Less depending on the hardware.
 391
 392           This is purely to save memory - each supported CPU requires
 393           memory in the static kernel configuration.
 394
 395 config HOTPLUG_CPU
 396         bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
 397         depends on SMP && HOTPLUG && EXPERIMENTAL
 398         help
 399                 Say Y here to experiment with turning CPUs off and on.  CPUs
 400                 can be controlled through /sys/devices/system/cpu/cpu#.
 401                 Say N if you want to disable CPU hotplug.
 402
 403 config ARCH_ENABLE_MEMORY_HOTPLUG
 404         def_bool y
 405
 406 config HPET_TIMER
 407         bool
 408         default y
 409         help
 410           Use the IA-PC HPET (High Precision Event Timer) to manage
 411           time in preference to the PIT and RTC, if a HPET is
 412           present.  The HPET provides a stable time base on SMP
 413           systems, unlike the TSC, but it is more expensive to access,
 414           as it is off-chip.  You can find the HPET spec at
 415           <http://www.intel.com/hardwaredesign/hpetspec.htm>.
 416
 417 config HPET_EMULATE_RTC
 418         bool "Provide RTC interrupt"
 419         depends on HPET_TIMER && RTC=y
 420
 421 # Mark as embedded because too many people got it wrong.
 422 # The code disables itself when not needed.
 423 config IOMMU
 424         bool "IOMMU support" if EMBEDDED
 425         default y
 426         select SWIOTLB
 427         select AGP
 428         depends on PCI
 429         help
 430           Support for full DMA access of devices with 32bit memory access only
 431           on systems with more than 3GB. This is usually needed for USB,
 432           sound, many IDE/SATA chipsets and some other devices.
 433           Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
 434           based IOMMU and a software bounce buffer based IOMMU used on Intel
 435           systems and as fallback.
 436           The code is only active when needed (enough memory and limited
 437           device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
 438           too.
 439
 440 config CALGARY_IOMMU
 441         bool "IBM Calgary IOMMU support"
 442         select SWIOTLB
 443         depends on PCI && EXPERIMENTAL
 444         help
 445           Support for hardware IOMMUs in IBM's xSeries x366 and x460
 446           systems. Needed to run systems with more than 3GB of memory
 447           properly with 32-bit PCI devices that do not support DAC
 448           (Double Address Cycle). Calgary also supports bus level
 449           isolation, where all DMAs pass through the IOMMU.  This
 450           prevents them from going anywhere except their intended
 451           destination. This catches hard-to-find kernel bugs and
 452           mis-behaving drivers and devices that do not use the DMA-API
 453           properly to set up their DMA buffers.  The IOMMU can be
 454           turned off at boot time with the iommu=off parameter.
 455           Normally the kernel will make the right choice by itself.
 456           If unsure, say Y.
 457
 458 # need this always selected by IOMMU for the VIA workaround
 459 config SWIOTLB
 460         bool
 461
 462 config X86_MCE
 463         bool "Machine check support" if EMBEDDED
 464         default y
 465         help
 466            Include a machine check error handler to report hardware errors.
 467            This version will require the mcelog utility to decode some
 468            machine check error logs. See
 469            ftp://ftp.x86-64.org/pub/linux/tools/mcelog
 470
 471 config X86_MCE_INTEL
 472         bool "Intel MCE features"
 473         depends on X86_MCE && X86_LOCAL_APIC
 474         default y
 475         help
 476            Additional support for intel specific MCE features such as
 477            the thermal monitor.
 478
 479 config X86_MCE_AMD
 480         bool "AMD MCE features"
 481         depends on X86_MCE && X86_LOCAL_APIC
 482         default y
 483         help
 484            Additional support for AMD specific MCE features such as
 485            the DRAM Error Threshold.
 486
 487 config KEXEC
 488         bool "kexec system call"
 489         help
 490           kexec is a system call that implements the ability to shutdown your
 491           current kernel, and to start another kernel.  It is like a reboot
 492           but it is independent of the system firmware.   And like a reboot
 493           you can start any kernel with it, not just Linux.
 494
 495           The name comes from the similarity to the exec system call.
 496
 497           It is an ongoing process to be certain the hardware in a machine
 498           is properly shutdown, so do not be surprised if this code does not
 499           initially work for you.  It may help to enable device hotplugging
 500           support.  As of this writing the exact hardware interface is
 501           strongly in flux, so no good recommendation can be made.
 502
 503 config CRASH_DUMP
 504         bool "kernel crash dumps (EXPERIMENTAL)"
 505         depends on EXPERIMENTAL
 506         help
 507           Generate crash dump after being started by kexec.
 508           This should be normally only set in special crash dump kernels
 509           which are loaded in the main kernel with kexec-tools into
 510           a specially reserved region and then later executed after
 511           a crash by kdump/kexec. The crash dump kernel must be compiled
 512           to a memory address not used by the main kernel or BIOS using
 513           PHYSICAL_START.
 514           For more details see Documentation/kdump/kdump.txt
 515
 516 config PHYSICAL_START
 517         hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
 518         default "0x1000000" if CRASH_DUMP
 519         default "0x200000"
 520         help
 521           This gives the physical address where the kernel is loaded. Normally
 522           for regular kernels this value is 0x200000 (2MB). But in the case
 523           of kexec on panic the fail safe kernel needs to run at a different
 524           address than the panic-ed kernel. This option is used to set the load
 525           address for kernels used to capture crash dump on being kexec'ed
 526           after panic. The default value for crash dump kernels is
 527           0x1000000 (16MB). This can also be set based on the "X" value as
 528           specified in the "crashkernel=YM@XM" command line boot parameter
 529           passed to the panic-ed kernel. Typically this parameter is set as
 530           crashkernel=64M@16M. Please take a look at
 531           Documentation/kdump/kdump.txt for more details about crash dumps.
 532
 533           Don't change this unless you know what you are doing.
 534
 535 config SECCOMP
 536         bool "Enable seccomp to safely compute untrusted bytecode"
 537         depends on PROC_FS
 538         default y
 539         help
 540           This kernel feature is useful for number crunching applications
 541           that may need to compute untrusted bytecode during their
 542           execution. By using pipes or other transports made available to
 543           the process as file descriptors supporting the read/write
 544           syscalls, it's possible to isolate those applications in
 545           their own address space using seccomp. Once seccomp is
 546           enabled via /proc/<pid>/seccomp, it cannot be disabled
 547           and the task is only allowed to execute a few safe syscalls
 548           defined by each seccomp mode.
 549
 550           If unsure, say Y. Only embedded should say N here.
 551
 552 config CC_STACKPROTECTOR
 553         bool "Enable -fstack-protector buffer overflow detection (EXPRIMENTAL)"
 554         depends on EXPERIMENTAL
 555         help
 556          This option turns on the -fstack-protector GCC feature. This
 557           feature puts, at the beginning of critical functions, a canary
 558           value on the stack just before the return address, and validates
 559           the value just before actually returning.  Stack based buffer
 560           overflows (that need to overwrite this return address) now also
 561           overwrite the canary, which gets detected and the attack is then
 562           neutralized via a kernel panic.
 563
 564           This feature requires gcc version 4.2 or above, or a distribution
 565           gcc with the feature backported. Older versions are automatically
 566           detected and for those versions, this configuration option is ignored.
 567
 568 config CC_STACKPROTECTOR_ALL
 569         bool "Use stack-protector for all functions"
 570         depends on CC_STACKPROTECTOR
 571         help
 572           Normally, GCC only inserts the canary value protection for
 573           functions that use large-ish on-stack buffers. By enabling
 574           this option, GCC will be asked to do this for ALL functions.
 575
 576 source kernel/Kconfig.hz
 577
 578 config REORDER
 579         bool "Function reordering"
 580         default n
 581         help
 582          This option enables the toolchain to reorder functions for a more
 583          optimal TLB usage. If you have pretty much any version of binutils,
 584          this can increase your kernel build time by roughly one minute.
 585
 586 config K8_NB
 587         def_bool y
 588         depends on AGP_AMD64 || IOMMU || (PCI && NUMA)
 589
 590 endmenu
 591
 592 #
 593 # Use the generic interrupt handling code in kernel/irq/:
 594 #
 595 config GENERIC_HARDIRQS
 596         bool
 597         default y
 598
 599 config GENERIC_IRQ_PROBE
 600         bool
 601         default y
 602
 603 # we have no ISA slots, but we do have ISA-style DMA.
 604 config ISA_DMA_API
 605         bool
 606         default y
 607
 608 config GENERIC_PENDING_IRQ
 609         bool
 610         depends on GENERIC_HARDIRQS && SMP
 611         default y
 612
 613 menu "Power management options"
 614
 615 source kernel/power/Kconfig
 616
 617 source "drivers/acpi/Kconfig"
 618
 619 source "arch/x86_64/kernel/cpufreq/Kconfig"
 620
 621 endmenu
 622
 623 menu "Bus options (PCI etc.)"
 624
 625 config PCI
 626         bool "PCI support"
 627
 628 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
 629 config PCI_DIRECT
 630         bool
 631         depends on PCI
 632         default y
 633
 634 config PCI_MMCONFIG
 635         bool "Support mmconfig PCI config space access"
 636         depends on PCI && ACPI
 637
 638 source "drivers/pci/pcie/Kconfig"
 639
 640 source "drivers/pci/Kconfig"
 641
 642 source "drivers/pcmcia/Kconfig"
 643
 644 source "drivers/pci/hotplug/Kconfig"
 645
 646 endmenu
 647
 648
 649 menu "Executable file formats / Emulations"
 650
 651 source "fs/Kconfig.binfmt"
 652
 653 config IA32_EMULATION
 654         bool "IA32 Emulation"
 655         help
 656           Include code to run 32-bit programs under a 64-bit kernel. You should likely
 657           turn this on, unless you're 100% sure that you don't have any 32-bit programs
 658           left.
 659
 660 config IA32_AOUT
 661        tristate "IA32 a.out support"
 662        depends on IA32_EMULATION
 663        help
 664          Support old a.out binaries in the 32bit emulation.
 665
 666 config COMPAT
 667         bool
 668         depends on IA32_EMULATION
 669         default y
 670
 671 config SYSVIPC_COMPAT
 672         bool
 673         depends on COMPAT && SYSVIPC
 674         default y
 675
 676 endmenu
 677
 678 source "net/Kconfig"
 679
 680 source drivers/Kconfig
 681
 682 source "drivers/firmware/Kconfig"
 683
 684 source fs/Kconfig
 685
 686 menu "Instrumentation Support"
 687         depends on EXPERIMENTAL
 688
 689 source "arch/x86_64/oprofile/Kconfig"
 690
 691 config KPROBES
 692         bool "Kprobes (EXPERIMENTAL)"
 693         depends on KALLSYMS && EXPERIMENTAL && MODULES
 694         help
 695           Kprobes allows you to trap at almost any kernel address and
 696           execute a callback function.  register_kprobe() establishes
 697           a probepoint and specifies the callback.  Kprobes is useful
 698           for kernel debugging, non-intrusive instrumentation and testing.
 699           If in doubt, say "N".
 700 endmenu
 701
 702 source "arch/x86_64/Kconfig.debug"
 703
 704 source "security/Kconfig"
 705
 706 source "crypto/Kconfig"
 707
 708 source "lib/Kconfig"