blob: 299d8740177af67e24cdbdcead5ea94de8f46a82 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
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
Benjamin LaHaise52fdd082005-09-03 15:56:52 -070027config SEMAPHORE_SLEEPERS
28 bool
29 default y
30
Linus Torvalds1da177e2005-04-16 15:20:36 -070031config MMU
32 bool
33 default y
34
35config ISA
36 bool
37
38config SBUS
39 bool
40
41config RWSEM_GENERIC_SPINLOCK
42 bool
43 default y
44
45config RWSEM_XCHGADD_ALGORITHM
46 bool
47
Akinobu Mitaf33e2fb2006-03-26 01:39:42 -080048config GENERIC_HWEIGHT
49 bool
50 default y
51
Linus Torvalds1da177e2005-04-16 15:20:36 -070052config GENERIC_CALIBRATE_DELAY
53 bool
54 default y
55
56config X86_CMPXCHG
57 bool
58 default y
59
60config EARLY_PRINTK
61 bool
62 default y
63
64config GENERIC_ISA_DMA
65 bool
66 default y
67
68config GENERIC_IOMAP
69 bool
70 default y
71
viro@ZenIV.linux.org.uka08b6b72005-09-06 01:48:42 +010072config ARCH_MAY_HAVE_PC_FDC
73 bool
74 default y
75
Andi Kleene9928672006-01-11 22:43:33 +010076config DMI
77 bool
78 default y
79
Linus Torvalds1da177e2005-04-16 15:20:36 -070080source "init/Kconfig"
81
82
83menu "Processor type and features"
84
85choice
Ravikiran G Thirumalai79f12612006-01-11 22:46:18 +010086 prompt "Subarchitecture Type"
87 default X86_PC
88
89config X86_PC
90 bool "PC-compatible"
91 help
92 Choose this option if your computer is a standard PC or compatible.
93
94config X86_VSMP
95 bool "Support for ScaleMP vSMP"
96 help
97 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
98 supposed to run on these EM64T-based machines. Only choose this option
99 if you have one of these machines.
100
101endchoice
102
103choice
Linus Torvalds1da177e2005-04-16 15:20:36 -0700104 prompt "Processor family"
105 default MK8
106
107config MK8
108 bool "AMD-Opteron/Athlon64"
109 help
110 Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
111
112config MPSC
113 bool "Intel EM64T"
114 help
115 Optimize for Intel Pentium 4 and Xeon CPUs with Intel
116 Extended Memory 64 Technology(EM64T). For details see
117 <http://www.intel.com/technology/64bitextensions/>.
118
119config GENERIC_CPU
120 bool "Generic-x86-64"
121 help
122 Generic x86-64 CPU.
123
124endchoice
125
126#
127# Define implied options from the CPU selection here
128#
129config X86_L1_CACHE_BYTES
130 int
131 default "128" if GENERIC_CPU || MPSC
132 default "64" if MK8
133
134config X86_L1_CACHE_SHIFT
135 int
136 default "7" if GENERIC_CPU || MPSC
137 default "6" if MK8
138
139config X86_TSC
140 bool
141 default y
142
143config X86_GOOD_APIC
144 bool
145 default y
146
147config MICROCODE
148 tristate "/dev/cpu/microcode - Intel CPU microcode support"
149 ---help---
150 If you say Y here the 'File systems' section, you will be
151 able to update the microcode on Intel processors. You will
152 obviously need the actual microcode binary data itself which is
153 not shipped with the Linux kernel.
154
155 For latest news and information on obtaining all the required
156 ingredients for this driver, check:
157 <http://www.urbanmyth.org/microcode/>.
158
159 To compile this driver as a module, choose M here: the
160 module will be called microcode.
161 If you use modprobe or kmod you may also want to add the line
162 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
163
164config X86_MSR
165 tristate "/dev/cpu/*/msr - Model-specific register support"
166 help
167 This device gives privileged processes access to the x86
168 Model-Specific Registers (MSRs). It is a character device with
169 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
170 MSR accesses are directed to a specific CPU on multi-processor
171 systems.
172
173config X86_CPUID
174 tristate "/dev/cpu/*/cpuid - CPU information support"
175 help
176 This device gives processes access to the x86 CPUID instruction to
177 be executed on a specific processor. It is a character device
178 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
179 /dev/cpu/31/cpuid.
180
Linus Torvalds1da177e2005-04-16 15:20:36 -0700181config X86_HT
182 bool
183 depends on SMP && !MK8
184 default y
185
186config MATH_EMULATION
187 bool
188
189config MCA
190 bool
191
192config EISA
193 bool
194
195config X86_IO_APIC
196 bool
197 default y
198
199config X86_LOCAL_APIC
200 bool
201 default y
202
203config MTRR
204 bool "MTRR (Memory Type Range Register) support"
205 ---help---
206 On Intel P6 family processors (Pentium Pro, Pentium II and later)
207 the Memory Type Range Registers (MTRRs) may be used to control
208 processor access to memory ranges. This is most useful if you have
209 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
210 allows bus write transfers to be combined into a larger transfer
211 before bursting over the PCI/AGP bus. This can increase performance
212 of image write operations 2.5 times or more. Saying Y here creates a
213 /proc/mtrr file which may be used to manipulate your processor's
214 MTRRs. Typically the X server should use this.
215
216 This code has a reasonably generic interface so that similar
217 control registers on other processors can be easily supported
218 as well.
219
220 Saying Y here also fixes a problem with buggy SMP BIOSes which only
221 set the MTRRs for the boot CPU and not for the secondary CPUs. This
222 can lead to all sorts of problems, so it's good to say Y here.
223
224 Just say Y here, all x86-64 machines support MTRRs.
225
226 See <file:Documentation/mtrr.txt> for more information.
227
228config SMP
229 bool "Symmetric multi-processing support"
230 ---help---
231 This enables support for systems with more than one CPU. If you have
232 a system with only one CPU, like most personal computers, say N. If
233 you have a system with more than one CPU, say Y.
234
235 If you say N here, the kernel will run on single and multiprocessor
236 machines, but will use only one CPU of a multiprocessor machine. If
237 you say Y here, the kernel will run on many, but not all,
238 singleprocessor machines. On a singleprocessor machine, the kernel
239 will run faster if you say N here.
240
241 If you don't know what to do here, say N.
242
Linus Torvalds1da177e2005-04-16 15:20:36 -0700243config SCHED_SMT
244 bool "SMT (Hyperthreading) scheduler support"
245 depends on SMP
246 default n
247 help
248 SMT scheduler support improves the CPU scheduler's decision making
249 when dealing with Intel Pentium 4 chips with HyperThreading at a
250 cost of slightly increased overhead in some places. If unsure say
251 N here.
252
Siddha, Suresh B1e9f28f2006-03-27 01:15:22 -0800253config SCHED_MC
254 bool "Multi-core scheduler support"
255 depends on SMP
256 default y
257 help
258 Multi-core scheduler support improves the CPU scheduler's decision
259 making when dealing with multi-core CPU chips at a cost of slightly
260 increased overhead in some places. If unsure say N here.
261
Ingo Molnarcc19ca82005-06-25 14:57:36 -0700262source "kernel/Kconfig.preempt"
263
Ravikiran G Thirumalaib0bd35e2005-11-05 17:25:54 +0100264config NUMA
265 bool "Non Uniform Memory Access (NUMA) Support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700266 depends on SMP
267 help
Ravikiran G Thirumalaib0bd35e2005-11-05 17:25:54 +0100268 Enable NUMA (Non Uniform Memory Access) support. The kernel
269 will try to allocate memory used by a CPU on the local memory
270 controller of the CPU and add some more NUMA awareness to the kernel.
271 This code is recommended on all multiprocessor Opteron systems.
272 If the system is EM64T, you should say N unless your system is EM64T
273 NUMA.
274
275config K8_NUMA
276 bool "Old style AMD Opteron NUMA detection"
277 depends on NUMA
278 default y
279 help
280 Enable K8 NUMA node topology detection. You should say Y here if
281 you have a multi processor AMD K8 system. This uses an old
282 method to read the NUMA configurtion directly from the builtin
283 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
284 instead, which also takes priority if both are compiled in.
285
286# Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.
287
288config X86_64_ACPI_NUMA
289 bool "ACPI NUMA detection"
290 depends on NUMA
291 select ACPI
Adrian Bunk13001242006-03-28 17:04:00 -0500292 select PCI
Ravikiran G Thirumalaib0bd35e2005-11-05 17:25:54 +0100293 select ACPI_NUMA
294 default y
295 help
296 Enable ACPI SRAT based node topology detection.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700297
298config NUMA_EMU
Ravikiran G Thirumalaib0bd35e2005-11-05 17:25:54 +0100299 bool "NUMA emulation"
300 depends on NUMA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700301 help
302 Enable NUMA emulation. A flat machine will be split
303 into virtual nodes when booted with "numa=fake=N", where N is the
304 number of nodes. This is only useful for debugging.
305
Dave Hansen3f22ab22005-06-23 00:07:43 -0700306config ARCH_DISCONTIGMEM_ENABLE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700307 bool
308 depends on NUMA
309 default y
310
Linus Torvalds1da177e2005-04-16 15:20:36 -0700311
Matt Tolentino1035faf2005-06-23 00:08:05 -0700312config ARCH_DISCONTIGMEM_ENABLE
313 def_bool y
314 depends on NUMA
315
316config ARCH_DISCONTIGMEM_DEFAULT
317 def_bool y
318 depends on NUMA
319
320config ARCH_SPARSEMEM_ENABLE
321 def_bool y
Matt Tolentino44df75e2006-01-17 07:03:41 +0100322 depends on (NUMA || EXPERIMENTAL)
323
324config ARCH_MEMORY_PROBE
325 def_bool y
326 depends on MEMORY_HOTPLUG
Matt Tolentino1035faf2005-06-23 00:08:05 -0700327
328config ARCH_FLATMEM_ENABLE
329 def_bool y
330 depends on !NUMA
331
Dave Hansen3f22ab22005-06-23 00:07:43 -0700332source "mm/Kconfig"
333
Matt Tolentino1035faf2005-06-23 00:08:05 -0700334config HAVE_ARCH_EARLY_PFN_TO_NID
335 def_bool y
Matt Tolentino44df75e2006-01-17 07:03:41 +0100336 depends on NUMA
Matt Tolentino1035faf2005-06-23 00:08:05 -0700337
KAMEZAWA Hiroyukidc8ecb42006-03-27 01:15:34 -0800338config OUT_OF_LINE_PFN_TO_PAGE
339 def_bool y
340 depends on DISCONTIGMEM
341
Linus Torvalds1da177e2005-04-16 15:20:36 -0700342config NR_CPUS
343 int "Maximum number of CPUs (2-256)"
Andi Kleen01d4bed2006-03-25 16:30:58 +0100344 range 2 255
Linus Torvalds1da177e2005-04-16 15:20:36 -0700345 depends on SMP
346 default "8"
347 help
348 This allows you to specify the maximum number of CPUs which this
349 kernel will support. Current maximum is 256 CPUs due to
350 APIC addressing limits. Less depending on the hardware.
351
352 This is purely to save memory - each supported CPU requires
353 memory in the static kernel configuration.
354
Ashok Raj76e4f662005-06-25 14:55:00 -0700355config HOTPLUG_CPU
356 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
357 depends on SMP && HOTPLUG && EXPERIMENTAL
358 help
359 Say Y here to experiment with turning CPUs off and on. CPUs
360 can be controlled through /sys/devices/system/cpu/cpu#.
361 Say N if you want to disable CPU hotplug.
362
363
Linus Torvalds1da177e2005-04-16 15:20:36 -0700364config HPET_TIMER
365 bool
366 default y
367 help
368 Use the IA-PC HPET (High Precision Event Timer) to manage
369 time in preference to the PIT and RTC, if a HPET is
370 present. The HPET provides a stable time base on SMP
371 systems, unlike the TSC, but it is more expensive to access,
372 as it is off-chip. You can find the HPET spec at
Randy Dunlap89d7cbf2005-09-21 09:55:44 -0700373 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700374
375config HPET_EMULATE_RTC
376 bool "Provide RTC interrupt"
377 depends on HPET_TIMER && RTC=y
378
379config GART_IOMMU
Muli Ben-Yehuda17a941d2006-01-11 22:44:42 +0100380 bool "K8 GART IOMMU support"
Andi Kleena54649b2005-07-28 21:15:32 -0700381 default y
Muli Ben-Yehuda17a941d2006-01-11 22:44:42 +0100382 select SWIOTLB
Linus Torvalds1da177e2005-04-16 15:20:36 -0700383 depends on PCI
384 help
Jon Mason5d05f4d2006-03-25 16:31:34 +0100385 Support for hardware IOMMU in AMD's Opteron/Athlon64 Processors
386 and for the bounce buffering software IOMMU.
387 Needed to run systems with more than 3GB of memory properly with
388 32-bit PCI devices that do not support DAC (Double Address Cycle).
389 The IOMMU can be turned off at runtime with the iommu=off parameter.
390 Normally the kernel will take the right choice by itself.
391 This option includes a driver for the AMD Opteron/Athlon64 IOMMU
392 northbridge and a software emulation used on other systems without
393 hardware IOMMU. If unsure, say Y.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700394
395# need this always enabled with GART_IOMMU for the VIA workaround
396config SWIOTLB
Linus Torvalds1da177e2005-04-16 15:20:36 -0700397 bool
Linus Torvalds1da177e2005-04-16 15:20:36 -0700398 default y
Muli Ben-Yehuda17a941d2006-01-11 22:44:42 +0100399 depends on GART_IOMMU
Linus Torvalds1da177e2005-04-16 15:20:36 -0700400
401config X86_MCE
402 bool "Machine check support" if EMBEDDED
403 default y
404 help
405 Include a machine check error handler to report hardware errors.
406 This version will require the mcelog utility to decode some
407 machine check error logs. See
408 ftp://ftp.x86-64.org/pub/linux/tools/mcelog
409
410config X86_MCE_INTEL
411 bool "Intel MCE features"
412 depends on X86_MCE && X86_LOCAL_APIC
413 default y
414 help
415 Additional support for intel specific MCE features such as
416 the thermal monitor.
417
Jacob Shin89b831e2005-11-05 17:25:53 +0100418config X86_MCE_AMD
419 bool "AMD MCE features"
420 depends on X86_MCE && X86_LOCAL_APIC
421 default y
422 help
423 Additional support for AMD specific MCE features such as
424 the DRAM Error Threshold.
425
Eric W. Biederman5234f5e2005-06-25 14:58:02 -0700426config KEXEC
427 bool "kexec system call (EXPERIMENTAL)"
428 depends on EXPERIMENTAL
429 help
430 kexec is a system call that implements the ability to shutdown your
431 current kernel, and to start another kernel. It is like a reboot
432 but it is indepedent of the system firmware. And like a reboot
433 you can start any kernel with it, not just Linux.
434
435 The name comes from the similiarity to the exec system call.
436
437 It is an ongoing process to be certain the hardware in a machine
438 is properly shutdown, so do not be surprised if this code does not
439 initially work for you. It may help to enable device hotplugging
440 support. As of this writing the exact hardware interface is
441 strongly in flux, so no good recommendation can be made.
442
Vivek Goyalec9ce0d2006-01-09 20:51:49 -0800443config CRASH_DUMP
444 bool "kernel crash dumps (EXPERIMENTAL)"
Vivek Goyalec9ce0d2006-01-09 20:51:49 -0800445 depends on EXPERIMENTAL
446 help
447 Generate crash dump after being started by kexec.
448
Maneesh Soni05970d42006-01-09 20:51:52 -0800449config PHYSICAL_START
450 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
451 default "0x1000000" if CRASH_DUMP
Andi Kleen04103602006-03-25 16:30:13 +0100452 default "0x200000"
Maneesh Soni05970d42006-01-09 20:51:52 -0800453 help
454 This gives the physical address where the kernel is loaded. Normally
Andi Kleen04103602006-03-25 16:30:13 +0100455 for regular kernels this value is 0x200000 (2MB). But in the case
Maneesh Soni05970d42006-01-09 20:51:52 -0800456 of kexec on panic the fail safe kernel needs to run at a different
457 address than the panic-ed kernel. This option is used to set the load
458 address for kernels used to capture crash dump on being kexec'ed
459 after panic. The default value for crash dump kernels is
460 0x1000000 (16MB). This can also be set based on the "X" value as
461 specified in the "crashkernel=YM@XM" command line boot parameter
462 passed to the panic-ed kernel. Typically this parameter is set as
463 crashkernel=64M@16M. Please take a look at
464 Documentation/kdump/kdump.txt for more details about crash dumps.
465
466 Don't change this unless you know what you are doing.
467
Linus Torvalds1da177e2005-04-16 15:20:36 -0700468config SECCOMP
469 bool "Enable seccomp to safely compute untrusted bytecode"
470 depends on PROC_FS
471 default y
472 help
473 This kernel feature is useful for number crunching applications
474 that may need to compute untrusted bytecode during their
475 execution. By using pipes or other transports made available to
476 the process as file descriptors supporting the read/write
477 syscalls, it's possible to isolate those applications in
478 their own address space using seccomp. Once seccomp is
479 enabled via /proc/<pid>/seccomp, it cannot be disabled
480 and the task is only allowed to execute a few safe syscalls
481 defined by each seccomp mode.
482
483 If unsure, say Y. Only embedded should say N here.
484
Christoph Lameter59121002005-06-23 00:08:25 -0700485source kernel/Kconfig.hz
486
Arjan van de Ven4bdc3b72006-03-25 16:30:49 +0100487config REORDER
488 bool "Function reordering"
489 default n
490 help
491 This option enables the toolchain to reorder functions for a more
492 optimal TLB usage. If you have pretty much any version of binutils,
493 this can increase your kernel build time by roughly one minute.
494
Linus Torvalds1da177e2005-04-16 15:20:36 -0700495endmenu
496
497#
498# Use the generic interrupt handling code in kernel/irq/:
499#
500config GENERIC_HARDIRQS
501 bool
502 default y
503
504config GENERIC_IRQ_PROBE
505 bool
506 default y
507
Al Viro5cae8412005-05-04 05:39:22 +0100508# we have no ISA slots, but we do have ISA-style DMA.
509config ISA_DMA_API
510 bool
511 default y
512
Ashok Raj54d5d422005-09-06 15:16:15 -0700513config GENERIC_PENDING_IRQ
514 bool
515 depends on GENERIC_HARDIRQS && SMP
516 default y
517
Linus Torvalds1da177e2005-04-16 15:20:36 -0700518menu "Power management options"
519
520source kernel/power/Kconfig
521
522source "drivers/acpi/Kconfig"
523
524source "arch/x86_64/kernel/cpufreq/Kconfig"
525
526endmenu
527
528menu "Bus options (PCI etc.)"
529
530config PCI
531 bool "PCI support"
532
533# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
534config PCI_DIRECT
535 bool
536 depends on PCI
537 default y
538
539config PCI_MMCONFIG
540 bool "Support mmconfig PCI config space access"
Alexander Nyberg8aadff72005-05-27 12:48:50 +0200541 depends on PCI && ACPI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700542
Linus Torvalds1da177e2005-04-16 15:20:36 -0700543source "drivers/pci/pcie/Kconfig"
544
545source "drivers/pci/Kconfig"
546
547source "drivers/pcmcia/Kconfig"
548
549source "drivers/pci/hotplug/Kconfig"
550
551endmenu
552
553
554menu "Executable file formats / Emulations"
555
556source "fs/Kconfig.binfmt"
557
558config IA32_EMULATION
559 bool "IA32 Emulation"
560 help
561 Include code to run 32-bit programs under a 64-bit kernel. You should likely
562 turn this on, unless you're 100% sure that you don't have any 32-bit programs
563 left.
564
565config IA32_AOUT
Andi Kleenea0be472005-11-05 17:25:54 +0100566 tristate "IA32 a.out support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700567 depends on IA32_EMULATION
568 help
569 Support old a.out binaries in the 32bit emulation.
570
571config COMPAT
572 bool
573 depends on IA32_EMULATION
574 default y
575
576config SYSVIPC_COMPAT
577 bool
578 depends on COMPAT && SYSVIPC
579 default y
580
Linus Torvalds1da177e2005-04-16 15:20:36 -0700581endmenu
582
Sam Ravnborgd5950b42005-07-11 21:03:49 -0700583source "net/Kconfig"
584
Linus Torvalds1da177e2005-04-16 15:20:36 -0700585source drivers/Kconfig
586
587source "drivers/firmware/Kconfig"
588
589source fs/Kconfig
590
Prasanna S Panchamukhicd6b0762005-11-07 00:59:14 -0800591menu "Instrumentation Support"
592 depends on EXPERIMENTAL
593
Linus Torvalds1da177e2005-04-16 15:20:36 -0700594source "arch/x86_64/oprofile/Kconfig"
595
Prasanna S Panchamukhicd6b0762005-11-07 00:59:14 -0800596config KPROBES
597 bool "Kprobes (EXPERIMENTAL)"
Linus Torvaldsadd2b6f2006-02-26 20:24:40 -0800598 depends on EXPERIMENTAL && MODULES
Prasanna S Panchamukhicd6b0762005-11-07 00:59:14 -0800599 help
600 Kprobes allows you to trap at almost any kernel address and
601 execute a callback function. register_kprobe() establishes
602 a probepoint and specifies the callback. Kprobes is useful
603 for kernel debugging, non-intrusive instrumentation and testing.
604 If in doubt, say "N".
605endmenu
606
Linus Torvalds1da177e2005-04-16 15:20:36 -0700607source "arch/x86_64/Kconfig.debug"
608
609source "security/Kconfig"
610
611source "crypto/Kconfig"
612
613source "lib/Kconfig"