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