2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
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.
10 mainmenu "Linux Kernel Configuration"
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/>.
27 config SEMAPHORE_SLEEPERS
41 config RWSEM_GENERIC_SPINLOCK
45 config RWSEM_XCHGADD_ALGORITHM
48 config GENERIC_CALIBRATE_DELAY
60 config GENERIC_ISA_DMA
68 config ARCH_MAY_HAVE_PC_FDC
79 menu "Processor type and features"
82 prompt "Subarchitecture Type"
88 Choose this option if your computer is a standard PC or compatible.
91 bool "Support for ScaleMP vSMP"
93 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
94 supposed to run on these EM64T-based machines. Only choose this option
95 if you have one of these machines.
100 prompt "Processor family"
104 bool "AMD-Opteron/Athlon64"
106 Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
111 Optimize for Intel Pentium 4 and Xeon CPUs with Intel
112 Extended Memory 64 Technology(EM64T). For details see
113 <http://www.intel.com/technology/64bitextensions/>.
116 bool "Generic-x86-64"
123 # Define implied options from the CPU selection here
125 config X86_L1_CACHE_BYTES
127 default "128" if GENERIC_CPU || MPSC
130 config X86_L1_CACHE_SHIFT
132 default "7" if GENERIC_CPU || MPSC
144 tristate "/dev/cpu/microcode - Intel CPU microcode support"
146 If you say Y here the 'File systems' section, you will be
147 able to update the microcode on Intel processors. You will
148 obviously need the actual microcode binary data itself which is
149 not shipped with the Linux kernel.
151 For latest news and information on obtaining all the required
152 ingredients for this driver, check:
153 <http://www.urbanmyth.org/microcode/>.
155 To compile this driver as a module, choose M here: the
156 module will be called microcode.
157 If you use modprobe or kmod you may also want to add the line
158 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
161 tristate "/dev/cpu/*/msr - Model-specific register support"
163 This device gives privileged processes access to the x86
164 Model-Specific Registers (MSRs). It is a character device with
165 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
166 MSR accesses are directed to a specific CPU on multi-processor
170 tristate "/dev/cpu/*/cpuid - CPU information support"
172 This device gives processes access to the x86 CPUID instruction to
173 be executed on a specific processor. It is a character device
174 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
179 depends on SMP && !MK8
182 config MATH_EMULATION
195 config X86_LOCAL_APIC
200 bool "MTRR (Memory Type Range Register) support"
202 On Intel P6 family processors (Pentium Pro, Pentium II and later)
203 the Memory Type Range Registers (MTRRs) may be used to control
204 processor access to memory ranges. This is most useful if you have
205 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
206 allows bus write transfers to be combined into a larger transfer
207 before bursting over the PCI/AGP bus. This can increase performance
208 of image write operations 2.5 times or more. Saying Y here creates a
209 /proc/mtrr file which may be used to manipulate your processor's
210 MTRRs. Typically the X server should use this.
212 This code has a reasonably generic interface so that similar
213 control registers on other processors can be easily supported
216 Saying Y here also fixes a problem with buggy SMP BIOSes which only
217 set the MTRRs for the boot CPU and not for the secondary CPUs. This
218 can lead to all sorts of problems, so it's good to say Y here.
220 Just say Y here, all x86-64 machines support MTRRs.
222 See <file:Documentation/mtrr.txt> for more information.
225 bool "Symmetric multi-processing support"
227 This enables support for systems with more than one CPU. If you have
228 a system with only one CPU, like most personal computers, say N. If
229 you have a system with more than one CPU, say Y.
231 If you say N here, the kernel will run on single and multiprocessor
232 machines, but will use only one CPU of a multiprocessor machine. If
233 you say Y here, the kernel will run on many, but not all,
234 singleprocessor machines. On a singleprocessor machine, the kernel
235 will run faster if you say N here.
237 If you don't know what to do here, say N.
240 bool "SMT (Hyperthreading) scheduler support"
244 SMT scheduler support improves the CPU scheduler's decision making
245 when dealing with Intel Pentium 4 chips with HyperThreading at a
246 cost of slightly increased overhead in some places. If unsure say
249 source "kernel/Kconfig.preempt"
252 bool "Non Uniform Memory Access (NUMA) Support"
255 Enable NUMA (Non Uniform Memory Access) support. The kernel
256 will try to allocate memory used by a CPU on the local memory
257 controller of the CPU and add some more NUMA awareness to the kernel.
258 This code is recommended on all multiprocessor Opteron systems.
259 If the system is EM64T, you should say N unless your system is EM64T
263 bool "Old style AMD Opteron NUMA detection"
267 Enable K8 NUMA node topology detection. You should say Y here if
268 you have a multi processor AMD K8 system. This uses an old
269 method to read the NUMA configurtion directly from the builtin
270 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
271 instead, which also takes priority if both are compiled in.
273 # Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.
275 config X86_64_ACPI_NUMA
276 bool "ACPI NUMA detection"
282 Enable ACPI SRAT based node topology detection.
285 bool "NUMA emulation"
288 Enable NUMA emulation. A flat machine will be split
289 into virtual nodes when booted with "numa=fake=N", where N is the
290 number of nodes. This is only useful for debugging.
292 config ARCH_DISCONTIGMEM_ENABLE
298 config ARCH_DISCONTIGMEM_ENABLE
302 config ARCH_DISCONTIGMEM_DEFAULT
306 config ARCH_SPARSEMEM_ENABLE
308 depends on (NUMA || EXPERIMENTAL)
310 config ARCH_MEMORY_PROBE
312 depends on MEMORY_HOTPLUG
314 config ARCH_FLATMEM_ENABLE
320 config HAVE_ARCH_EARLY_PFN_TO_NID
325 int "Maximum number of CPUs (2-256)"
330 This allows you to specify the maximum number of CPUs which this
331 kernel will support. Current maximum is 256 CPUs due to
332 APIC addressing limits. Less depending on the hardware.
334 This is purely to save memory - each supported CPU requires
335 memory in the static kernel configuration.
338 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
339 depends on SMP && HOTPLUG && EXPERIMENTAL
341 Say Y here to experiment with turning CPUs off and on. CPUs
342 can be controlled through /sys/devices/system/cpu/cpu#.
343 Say N if you want to disable CPU hotplug.
350 Use the IA-PC HPET (High Precision Event Timer) to manage
351 time in preference to the PIT and RTC, if a HPET is
352 present. The HPET provides a stable time base on SMP
353 systems, unlike the TSC, but it is more expensive to access,
354 as it is off-chip. You can find the HPET spec at
355 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
358 bool "PM timer" if EMBEDDED
362 Support the ACPI PM timer for time keeping. This is slow,
363 but is useful on some chipsets without HPET on systems with more
364 than one CPU. On a single processor or single socket multi core
365 system it is normally not required.
366 When the PM timer is active 64bit vsyscalls are disabled
367 and should not be enabled (/proc/sys/kernel/vsyscall64 should
369 The kernel selects the PM timer only as a last resort, so it is
370 useful to enable just in case.
372 config HPET_EMULATE_RTC
373 bool "Provide RTC interrupt"
374 depends on HPET_TIMER && RTC=y
377 bool "K8 GART IOMMU support"
382 Support the IOMMU. Needed to run systems with more than 3GB of memory
383 properly with 32-bit PCI devices that do not support DAC (Double Address
384 Cycle). The IOMMU can be turned off at runtime with the iommu=off parameter.
385 Normally the kernel will take the right choice by itself.
386 This option includes a driver for the AMD Opteron/Athlon64 northbridge IOMMU
387 and a software emulation used on other systems.
390 # need this always enabled with GART_IOMMU for the VIA workaround
394 depends on GART_IOMMU
397 bool "Machine check support" if EMBEDDED
400 Include a machine check error handler to report hardware errors.
401 This version will require the mcelog utility to decode some
402 machine check error logs. See
403 ftp://ftp.x86-64.org/pub/linux/tools/mcelog
406 bool "Intel MCE features"
407 depends on X86_MCE && X86_LOCAL_APIC
410 Additional support for intel specific MCE features such as
414 bool "AMD MCE features"
415 depends on X86_MCE && X86_LOCAL_APIC
418 Additional support for AMD specific MCE features such as
419 the DRAM Error Threshold.
422 bool "kexec system call (EXPERIMENTAL)"
423 depends on EXPERIMENTAL
425 kexec is a system call that implements the ability to shutdown your
426 current kernel, and to start another kernel. It is like a reboot
427 but it is indepedent of the system firmware. And like a reboot
428 you can start any kernel with it, not just Linux.
430 The name comes from the similiarity to the exec system call.
432 It is an ongoing process to be certain the hardware in a machine
433 is properly shutdown, so do not be surprised if this code does not
434 initially work for you. It may help to enable device hotplugging
435 support. As of this writing the exact hardware interface is
436 strongly in flux, so no good recommendation can be made.
439 bool "kernel crash dumps (EXPERIMENTAL)"
440 depends on EXPERIMENTAL
442 Generate crash dump after being started by kexec.
444 config PHYSICAL_START
445 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
446 default "0x1000000" if CRASH_DUMP
449 This gives the physical address where the kernel is loaded. Normally
450 for regular kernels this value is 0x100000 (1MB). But in the case
451 of kexec on panic the fail safe kernel needs to run at a different
452 address than the panic-ed kernel. This option is used to set the load
453 address for kernels used to capture crash dump on being kexec'ed
454 after panic. The default value for crash dump kernels is
455 0x1000000 (16MB). This can also be set based on the "X" value as
456 specified in the "crashkernel=YM@XM" command line boot parameter
457 passed to the panic-ed kernel. Typically this parameter is set as
458 crashkernel=64M@16M. Please take a look at
459 Documentation/kdump/kdump.txt for more details about crash dumps.
461 Don't change this unless you know what you are doing.
464 bool "Enable seccomp to safely compute untrusted bytecode"
468 This kernel feature is useful for number crunching applications
469 that may need to compute untrusted bytecode during their
470 execution. By using pipes or other transports made available to
471 the process as file descriptors supporting the read/write
472 syscalls, it's possible to isolate those applications in
473 their own address space using seccomp. Once seccomp is
474 enabled via /proc/<pid>/seccomp, it cannot be disabled
475 and the task is only allowed to execute a few safe syscalls
476 defined by each seccomp mode.
478 If unsure, say Y. Only embedded should say N here.
480 source kernel/Kconfig.hz
485 # Use the generic interrupt handling code in kernel/irq/:
487 config GENERIC_HARDIRQS
491 config GENERIC_IRQ_PROBE
495 # we have no ISA slots, but we do have ISA-style DMA.
500 config GENERIC_PENDING_IRQ
502 depends on GENERIC_HARDIRQS && SMP
505 menu "Power management options"
507 source kernel/power/Kconfig
509 source "drivers/acpi/Kconfig"
511 source "arch/x86_64/kernel/cpufreq/Kconfig"
515 menu "Bus options (PCI etc.)"
520 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
527 bool "Support mmconfig PCI config space access"
528 depends on PCI && ACPI
531 bool "Unordered IO mapping access"
532 depends on EXPERIMENTAL
534 Use unordered stores to access IO memory mappings in device drivers.
535 Still very experimental. When a driver works on IA64/ppc64/pa-risc it should
536 work with this option, but it makes the drivers behave differently
537 from i386. Requires that the driver writer used memory barriers
540 source "drivers/pci/pcie/Kconfig"
542 source "drivers/pci/Kconfig"
544 source "drivers/pcmcia/Kconfig"
546 source "drivers/pci/hotplug/Kconfig"
551 menu "Executable file formats / Emulations"
553 source "fs/Kconfig.binfmt"
555 config IA32_EMULATION
556 bool "IA32 Emulation"
558 Include code to run 32-bit programs under a 64-bit kernel. You should likely
559 turn this on, unless you're 100% sure that you don't have any 32-bit programs
563 tristate "IA32 a.out support"
564 depends on IA32_EMULATION
566 Support old a.out binaries in the 32bit emulation.
570 depends on IA32_EMULATION
573 config SYSVIPC_COMPAT
575 depends on COMPAT && SYSVIPC
582 source drivers/Kconfig
584 source "drivers/firmware/Kconfig"
588 menu "Instrumentation Support"
589 depends on EXPERIMENTAL
591 source "arch/x86_64/oprofile/Kconfig"
594 bool "Kprobes (EXPERIMENTAL)"
596 Kprobes allows you to trap at almost any kernel address and
597 execute a callback function. register_kprobe() establishes
598 a probepoint and specifies the callback. Kprobes is useful
599 for kernel debugging, non-intrusive instrumentation and testing.
600 If in doubt, say "N".
603 source "arch/x86_64/Kconfig.debug"
605 source "security/Kconfig"
607 source "crypto/Kconfig"