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