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