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