blob: db259757dc8a4f97af912c8d56f5e0ae8d4ab81a [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
27config MMU
28 bool
29 default y
30
31config ISA
32 bool
33
34config SBUS
35 bool
36
37config RWSEM_GENERIC_SPINLOCK
38 bool
39 default y
40
41config RWSEM_XCHGADD_ALGORITHM
42 bool
43
44config GENERIC_CALIBRATE_DELAY
45 bool
46 default y
47
48config X86_CMPXCHG
49 bool
50 default y
51
52config EARLY_PRINTK
53 bool
54 default y
55
56config GENERIC_ISA_DMA
57 bool
58 default y
59
60config GENERIC_IOMAP
61 bool
62 default y
63
64source "init/Kconfig"
65
66
67menu "Processor type and features"
68
69choice
70 prompt "Processor family"
71 default MK8
72
73config MK8
74 bool "AMD-Opteron/Athlon64"
75 help
76 Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
77
78config MPSC
79 bool "Intel EM64T"
80 help
81 Optimize for Intel Pentium 4 and Xeon CPUs with Intel
82 Extended Memory 64 Technology(EM64T). For details see
83 <http://www.intel.com/technology/64bitextensions/>.
84
85config GENERIC_CPU
86 bool "Generic-x86-64"
87 help
88 Generic x86-64 CPU.
89
90endchoice
91
92#
93# Define implied options from the CPU selection here
94#
95config X86_L1_CACHE_BYTES
96 int
97 default "128" if GENERIC_CPU || MPSC
98 default "64" if MK8
99
100config X86_L1_CACHE_SHIFT
101 int
102 default "7" if GENERIC_CPU || MPSC
103 default "6" if MK8
104
105config X86_TSC
106 bool
107 default y
108
109config X86_GOOD_APIC
110 bool
111 default y
112
113config MICROCODE
114 tristate "/dev/cpu/microcode - Intel CPU microcode support"
115 ---help---
116 If you say Y here the 'File systems' section, you will be
117 able to update the microcode on Intel processors. You will
118 obviously need the actual microcode binary data itself which is
119 not shipped with the Linux kernel.
120
121 For latest news and information on obtaining all the required
122 ingredients for this driver, check:
123 <http://www.urbanmyth.org/microcode/>.
124
125 To compile this driver as a module, choose M here: the
126 module will be called microcode.
127 If you use modprobe or kmod you may also want to add the line
128 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
129
130config X86_MSR
131 tristate "/dev/cpu/*/msr - Model-specific register support"
132 help
133 This device gives privileged processes access to the x86
134 Model-Specific Registers (MSRs). It is a character device with
135 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
136 MSR accesses are directed to a specific CPU on multi-processor
137 systems.
138
139config X86_CPUID
140 tristate "/dev/cpu/*/cpuid - CPU information support"
141 help
142 This device gives processes access to the x86 CPUID instruction to
143 be executed on a specific processor. It is a character device
144 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
145 /dev/cpu/31/cpuid.
146
147# disable it for opteron optimized builds because it pulls in ACPI_BOOT
148config X86_HT
149 bool
150 depends on SMP && !MK8
151 default y
152
153config MATH_EMULATION
154 bool
155
156config MCA
157 bool
158
159config EISA
160 bool
161
162config X86_IO_APIC
163 bool
164 default y
165
166config X86_LOCAL_APIC
167 bool
168 default y
169
170config MTRR
171 bool "MTRR (Memory Type Range Register) support"
172 ---help---
173 On Intel P6 family processors (Pentium Pro, Pentium II and later)
174 the Memory Type Range Registers (MTRRs) may be used to control
175 processor access to memory ranges. This is most useful if you have
176 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
177 allows bus write transfers to be combined into a larger transfer
178 before bursting over the PCI/AGP bus. This can increase performance
179 of image write operations 2.5 times or more. Saying Y here creates a
180 /proc/mtrr file which may be used to manipulate your processor's
181 MTRRs. Typically the X server should use this.
182
183 This code has a reasonably generic interface so that similar
184 control registers on other processors can be easily supported
185 as well.
186
187 Saying Y here also fixes a problem with buggy SMP BIOSes which only
188 set the MTRRs for the boot CPU and not for the secondary CPUs. This
189 can lead to all sorts of problems, so it's good to say Y here.
190
191 Just say Y here, all x86-64 machines support MTRRs.
192
193 See <file:Documentation/mtrr.txt> for more information.
194
195config SMP
196 bool "Symmetric multi-processing support"
197 ---help---
198 This enables support for systems with more than one CPU. If you have
199 a system with only one CPU, like most personal computers, say N. If
200 you have a system with more than one CPU, say Y.
201
202 If you say N here, the kernel will run on single and multiprocessor
203 machines, but will use only one CPU of a multiprocessor machine. If
204 you say Y here, the kernel will run on many, but not all,
205 singleprocessor machines. On a singleprocessor machine, the kernel
206 will run faster if you say N here.
207
208 If you don't know what to do here, say N.
209
210config PREEMPT
211 bool "Preemptible Kernel"
212 ---help---
213 This option reduces the latency of the kernel when reacting to
214 real-time or interactive events by allowing a low priority process to
215 be preempted even if it is in kernel mode executing a system call.
216 This allows applications to run more reliably even when the system is
217 under load. On contrary it may also break your drivers and add
218 priority inheritance problems to your system. Don't select it if
219 you rely on a stable system or have slightly obscure hardware.
220 It's also not very well tested on x86-64 currently.
221 You have been warned.
222
223 Say Y here if you are feeling brave and building a kernel for a
224 desktop, embedded or real-time system. Say N if you are unsure.
225
226config PREEMPT_BKL
227 bool "Preempt The Big Kernel Lock"
228 depends on PREEMPT
229 default y
230 help
231 This option reduces the latency of the kernel by making the
232 big kernel lock preemptible.
233
234 Say Y here if you are building a kernel for a desktop system.
235 Say N if you are unsure.
236
237config SCHED_SMT
238 bool "SMT (Hyperthreading) scheduler support"
239 depends on SMP
240 default n
241 help
242 SMT scheduler support improves the CPU scheduler's decision making
243 when dealing with Intel Pentium 4 chips with HyperThreading at a
244 cost of slightly increased overhead in some places. If unsure say
245 N here.
246
247config K8_NUMA
248 bool "K8 NUMA support"
249 select NUMA
250 depends on SMP
251 help
252 Enable NUMA (Non Unified Memory Architecture) support for
253 AMD Opteron Multiprocessor systems. The kernel will try to allocate
254 memory used by a CPU on the local memory controller of the CPU
255 and add some more NUMA awareness to the kernel.
256 This code is recommended on all multiprocessor Opteron systems
257 and normally doesn't hurt on others.
258
259config NUMA_EMU
260 bool "NUMA emulation support"
261 select NUMA
262 depends on SMP
263 help
264 Enable NUMA emulation. A flat machine will be split
265 into virtual nodes when booted with "numa=fake=N", where N is the
266 number of nodes. This is only useful for debugging.
267
Dave Hansen3f22ab22005-06-23 00:07:43 -0700268config ARCH_DISCONTIGMEM_ENABLE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700269 bool
270 depends on NUMA
271 default y
272
273config NUMA
274 bool
275 default n
276
Matt Tolentino1035faf2005-06-23 00:08:05 -0700277config ARCH_DISCONTIGMEM_ENABLE
278 def_bool y
279 depends on NUMA
280
281config ARCH_DISCONTIGMEM_DEFAULT
282 def_bool y
283 depends on NUMA
284
285config ARCH_SPARSEMEM_ENABLE
286 def_bool y
287 depends on NUMA
288
289config ARCH_FLATMEM_ENABLE
290 def_bool y
291 depends on !NUMA
292
Dave Hansen3f22ab22005-06-23 00:07:43 -0700293source "mm/Kconfig"
294
Matt Tolentino1035faf2005-06-23 00:08:05 -0700295config HAVE_ARCH_EARLY_PFN_TO_NID
296 def_bool y
297
Linus Torvalds1da177e2005-04-16 15:20:36 -0700298config HAVE_DEC_LOCK
299 bool
300 depends on SMP
301 default y
302
303config NR_CPUS
304 int "Maximum number of CPUs (2-256)"
305 range 2 256
306 depends on SMP
307 default "8"
308 help
309 This allows you to specify the maximum number of CPUs which this
310 kernel will support. Current maximum is 256 CPUs due to
311 APIC addressing limits. Less depending on the hardware.
312
313 This is purely to save memory - each supported CPU requires
314 memory in the static kernel configuration.
315
316config HPET_TIMER
317 bool
318 default y
319 help
320 Use the IA-PC HPET (High Precision Event Timer) to manage
321 time in preference to the PIT and RTC, if a HPET is
322 present. The HPET provides a stable time base on SMP
323 systems, unlike the TSC, but it is more expensive to access,
324 as it is off-chip. You can find the HPET spec at
325 <http://www.intel.com/labs/platcomp/hpet/hpetspec.htm>.
326
Andi Kleen312df5f2005-05-16 21:53:28 -0700327config X86_PM_TIMER
328 bool "PM timer"
Andi Kleen9c2be6a2005-05-31 14:39:26 -0700329 depends on ACPI
Andi Kleen312df5f2005-05-16 21:53:28 -0700330 default y
331 help
332 Support the ACPI PM timer for time keeping. This is slow,
333 but is useful on some chipsets without HPET on systems with more
334 than one CPU. On a single processor or single socket multi core
335 system it is normally not required.
336 When the PM timer is active 64bit vsyscalls are disabled
337 and should not be enabled (/proc/sys/kernel/vsyscall64 should
338 not be changed).
339 The kernel selects the PM timer only as a last resort, so it is
340 useful to enable just in case.
341
Linus Torvalds1da177e2005-04-16 15:20:36 -0700342config HPET_EMULATE_RTC
343 bool "Provide RTC interrupt"
344 depends on HPET_TIMER && RTC=y
345
346config GART_IOMMU
347 bool "IOMMU support"
348 depends on PCI
349 help
350 Support the K8 IOMMU. Needed to run systems with more than 4GB of memory
351 properly with 32-bit PCI devices that do not support DAC (Double Address
352 Cycle). The IOMMU can be turned off at runtime with the iommu=off parameter.
353 Normally the kernel will take the right choice by itself.
354 If unsure, say Y.
355
356# need this always enabled with GART_IOMMU for the VIA workaround
357config SWIOTLB
358 bool
359 depends on GART_IOMMU
360 default y
361
362config DUMMY_IOMMU
363 bool
364 depends on !GART_IOMMU && !SWIOTLB
365 default y
366 help
367 Don't use IOMMU code. This will cause problems when you have more than 4GB
368 of memory and any 32-bit devices. Don't turn on unless you know what you
369 are doing.
370
371config X86_MCE
372 bool "Machine check support" if EMBEDDED
373 default y
374 help
375 Include a machine check error handler to report hardware errors.
376 This version will require the mcelog utility to decode some
377 machine check error logs. See
378 ftp://ftp.x86-64.org/pub/linux/tools/mcelog
379
380config X86_MCE_INTEL
381 bool "Intel MCE features"
382 depends on X86_MCE && X86_LOCAL_APIC
383 default y
384 help
385 Additional support for intel specific MCE features such as
386 the thermal monitor.
387
388config SECCOMP
389 bool "Enable seccomp to safely compute untrusted bytecode"
390 depends on PROC_FS
391 default y
392 help
393 This kernel feature is useful for number crunching applications
394 that may need to compute untrusted bytecode during their
395 execution. By using pipes or other transports made available to
396 the process as file descriptors supporting the read/write
397 syscalls, it's possible to isolate those applications in
398 their own address space using seccomp. Once seccomp is
399 enabled via /proc/<pid>/seccomp, it cannot be disabled
400 and the task is only allowed to execute a few safe syscalls
401 defined by each seccomp mode.
402
403 If unsure, say Y. Only embedded should say N here.
404
Christoph Lameter59121002005-06-23 00:08:25 -0700405source kernel/Kconfig.hz
406
Linus Torvalds1da177e2005-04-16 15:20:36 -0700407endmenu
408
409#
410# Use the generic interrupt handling code in kernel/irq/:
411#
412config GENERIC_HARDIRQS
413 bool
414 default y
415
416config GENERIC_IRQ_PROBE
417 bool
418 default y
419
Al Viro5cae8412005-05-04 05:39:22 +0100420# we have no ISA slots, but we do have ISA-style DMA.
421config ISA_DMA_API
422 bool
423 default y
424
Linus Torvalds1da177e2005-04-16 15:20:36 -0700425menu "Power management options"
426
427source kernel/power/Kconfig
428
429source "drivers/acpi/Kconfig"
430
431source "arch/x86_64/kernel/cpufreq/Kconfig"
432
433endmenu
434
435menu "Bus options (PCI etc.)"
436
437config PCI
438 bool "PCI support"
439
440# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
441config PCI_DIRECT
442 bool
443 depends on PCI
444 default y
445
446config PCI_MMCONFIG
447 bool "Support mmconfig PCI config space access"
Alexander Nyberg8aadff72005-05-27 12:48:50 +0200448 depends on PCI && ACPI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700449 select ACPI_BOOT
450
451config UNORDERED_IO
452 bool "Unordered IO mapping access"
453 depends on EXPERIMENTAL
454 help
455 Use unordered stores to access IO memory mappings in device drivers.
456 Still very experimental. When a driver works on IA64/ppc64/pa-risc it should
457 work with this option, but it makes the drivers behave differently
458 from i386. Requires that the driver writer used memory barriers
459 properly.
460
461source "drivers/pci/pcie/Kconfig"
462
463source "drivers/pci/Kconfig"
464
465source "drivers/pcmcia/Kconfig"
466
467source "drivers/pci/hotplug/Kconfig"
468
469endmenu
470
471
472menu "Executable file formats / Emulations"
473
474source "fs/Kconfig.binfmt"
475
476config IA32_EMULATION
477 bool "IA32 Emulation"
478 help
479 Include code to run 32-bit programs under a 64-bit kernel. You should likely
480 turn this on, unless you're 100% sure that you don't have any 32-bit programs
481 left.
482
483config IA32_AOUT
484 bool "IA32 a.out support"
485 depends on IA32_EMULATION
486 help
487 Support old a.out binaries in the 32bit emulation.
488
489config COMPAT
490 bool
491 depends on IA32_EMULATION
492 default y
493
494config SYSVIPC_COMPAT
495 bool
496 depends on COMPAT && SYSVIPC
497 default y
498
499config UID16
500 bool
501 depends on IA32_EMULATION
502 default y
503
504endmenu
505
506source drivers/Kconfig
507
508source "drivers/firmware/Kconfig"
509
510source fs/Kconfig
511
512source "arch/x86_64/oprofile/Kconfig"
513
514source "arch/x86_64/Kconfig.debug"
515
516source "security/Kconfig"
517
518source "crypto/Kconfig"
519
520source "lib/Kconfig"