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