ia64/xen-unstable

view linux-2.6-xen-sparse/arch/x86_64/Kconfig @ 9709:14f6d138c61d

Allow PCI-E and PCMCIA config on 64-bit Xenlinux.

Signed-off-by: Keir Fraser <keir@xensource.com>
author kaf24@firebug.cl.cam.ac.uk
date Thu Apr 13 15:15:56 2006 +0100 (2006-04-13)
parents df0ad1c46f10
children 77ec02027c17
line source
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 #
10 mainmenu "Linux Kernel Configuration"
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/>.
20 config 64BIT
21 def_bool y
23 config X86
24 bool
25 default y
27 config SEMAPHORE_SLEEPERS
28 bool
29 default y
31 config MMU
32 bool
33 default y
35 config ISA
36 bool
38 config SBUS
39 bool
41 config RWSEM_GENERIC_SPINLOCK
42 bool
43 default y
45 config RWSEM_XCHGADD_ALGORITHM
46 bool
48 config GENERIC_CALIBRATE_DELAY
49 bool
50 default y
52 config X86_CMPXCHG
53 bool
54 default y
56 config EARLY_PRINTK
57 bool
58 default y
60 config GENERIC_ISA_DMA
61 bool
62 default y
64 config GENERIC_IOMAP
65 bool
66 default y
68 config ARCH_MAY_HAVE_PC_FDC
69 bool
70 default y
72 config DMI
73 bool
74 default y
76 source "init/Kconfig"
79 menu "Processor type and features"
81 choice
82 prompt "Subarchitecture Type"
83 default X86_PC
85 config X86_PC
86 bool "PC-compatible"
87 help
88 Choose this option if your computer is a standard PC or compatible.
90 config X86_VSMP
91 bool "Support for ScaleMP vSMP"
92 help
93 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
94 supposed to run on these EM64T-based machines. Only choose this option
95 if you have one of these machines.
97 endchoice
99 choice
100 prompt "Processor family"
101 default MK8
103 config MK8
104 bool "AMD-Opteron/Athlon64"
105 help
106 Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
108 config MPSC
109 bool "Intel EM64T"
110 help
111 Optimize for Intel Pentium 4 and Xeon CPUs with Intel
112 Extended Memory 64 Technology(EM64T). For details see
113 <http://www.intel.com/technology/64bitextensions/>.
115 config GENERIC_CPU
116 bool "Generic-x86-64"
117 help
118 Generic x86-64 CPU.
120 endchoice
122 config X86_64_XEN
123 bool "Enable Xen compatible kernel"
124 select SWIOTLB
125 help
126 This option will compile a kernel compatible with Xen hypervisor
128 config X86_NO_TSS
129 bool
130 depends on X86_64_XEN
131 default y
133 config X86_NO_IDT
134 bool
135 depends on X86_64_XEN
136 default y
138 #
139 # Define implied options from the CPU selection here
140 #
141 config X86_L1_CACHE_BYTES
142 int
143 default "128" if GENERIC_CPU || MPSC
144 default "64" if MK8
146 config X86_L1_CACHE_SHIFT
147 int
148 default "7" if GENERIC_CPU || MPSC
149 default "6" if MK8
151 config X86_TSC
152 bool
153 depends on !X86_64_XEN
154 default y
156 config X86_GOOD_APIC
157 bool
158 default y
160 config MICROCODE
161 tristate "/dev/cpu/microcode - Intel CPU microcode support"
162 ---help---
163 If you say Y here the 'File systems' section, you will be
164 able to update the microcode on Intel processors. You will
165 obviously need the actual microcode binary data itself which is
166 not shipped with the Linux kernel.
168 For latest news and information on obtaining all the required
169 ingredients for this driver, check:
170 <http://www.urbanmyth.org/microcode/>.
172 To compile this driver as a module, choose M here: the
173 module will be called microcode.
174 If you use modprobe or kmod you may also want to add the line
175 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
177 config X86_MSR
178 tristate "/dev/cpu/*/msr - Model-specific register support"
179 help
180 This device gives privileged processes access to the x86
181 Model-Specific Registers (MSRs). It is a character device with
182 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
183 MSR accesses are directed to a specific CPU on multi-processor
184 systems.
186 config X86_CPUID
187 tristate "/dev/cpu/*/cpuid - CPU information support"
188 help
189 This device gives processes access to the x86 CPUID instruction to
190 be executed on a specific processor. It is a character device
191 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
192 /dev/cpu/31/cpuid.
194 config X86_HT
195 bool
196 depends on SMP && !MK8 && !X86_64_XEN
197 default y
199 config MATH_EMULATION
200 bool
202 config MCA
203 bool
205 config EISA
206 bool
208 config X86_IO_APIC
209 bool
210 depends !XEN_UNPRIVILEGED_GUEST
211 default y
213 config X86_XEN_GENAPIC
214 bool
215 depends X86_64_XEN
216 default XEN_PRIVILEGED_GUEST || SMP
218 config X86_LOCAL_APIC
219 bool
220 depends !XEN_UNPRIVILEGED_GUEST
221 default y
223 config MTRR
224 bool "MTRR (Memory Type Range Register) support"
225 depends on !XEN_UNPRIVILEGED_GUEST
226 ---help---
227 On Intel P6 family processors (Pentium Pro, Pentium II and later)
228 the Memory Type Range Registers (MTRRs) may be used to control
229 processor access to memory ranges. This is most useful if you have
230 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
231 allows bus write transfers to be combined into a larger transfer
232 before bursting over the PCI/AGP bus. This can increase performance
233 of image write operations 2.5 times or more. Saying Y here creates a
234 /proc/mtrr file which may be used to manipulate your processor's
235 MTRRs. Typically the X server should use this.
237 This code has a reasonably generic interface so that similar
238 control registers on other processors can be easily supported
239 as well.
241 Saying Y here also fixes a problem with buggy SMP BIOSes which only
242 set the MTRRs for the boot CPU and not for the secondary CPUs. This
243 can lead to all sorts of problems, so it's good to say Y here.
245 Just say Y here, all x86-64 machines support MTRRs.
247 See <file:Documentation/mtrr.txt> for more information.
249 config SMP
250 bool "Symmetric multi-processing support"
251 ---help---
252 This enables support for systems with more than one CPU. If you have
253 a system with only one CPU, like most personal computers, say N. If
254 you have a system with more than one CPU, say Y.
256 If you say N here, the kernel will run on single and multiprocessor
257 machines, but will use only one CPU of a multiprocessor machine. If
258 you say Y here, the kernel will run on many, but not all,
259 singleprocessor machines. On a singleprocessor machine, the kernel
260 will run faster if you say N here.
262 If you don't know what to do here, say N.
264 config SCHED_SMT
265 bool "SMT (Hyperthreading) scheduler support"
266 depends on SMP && !X86_64_XEN
267 default n
268 help
269 SMT scheduler support improves the CPU scheduler's decision making
270 when dealing with Intel Pentium 4 chips with HyperThreading at a
271 cost of slightly increased overhead in some places. If unsure say
272 N here.
274 source "kernel/Kconfig.preempt"
276 config NUMA
277 bool "Non Uniform Memory Access (NUMA) Support"
278 depends on SMP && !X86_64_XEN
279 help
280 Enable NUMA (Non Uniform Memory Access) support. The kernel
281 will try to allocate memory used by a CPU on the local memory
282 controller of the CPU and add some more NUMA awareness to the kernel.
283 This code is recommended on all multiprocessor Opteron systems.
284 If the system is EM64T, you should say N unless your system is EM64T
285 NUMA.
287 config K8_NUMA
288 bool "Old style AMD Opteron NUMA detection"
289 depends on NUMA
290 default y
291 help
292 Enable K8 NUMA node topology detection. You should say Y here if
293 you have a multi processor AMD K8 system. This uses an old
294 method to read the NUMA configurtion directly from the builtin
295 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
296 instead, which also takes priority if both are compiled in.
298 # Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.
300 config X86_64_ACPI_NUMA
301 bool "ACPI NUMA detection"
302 depends on NUMA
303 select ACPI
304 select ACPI_NUMA
305 default y
306 help
307 Enable ACPI SRAT based node topology detection.
309 config NUMA_EMU
310 bool "NUMA emulation"
311 depends on NUMA
312 help
313 Enable NUMA emulation. A flat machine will be split
314 into virtual nodes when booted with "numa=fake=N", where N is the
315 number of nodes. This is only useful for debugging.
317 config ARCH_DISCONTIGMEM_ENABLE
318 bool
319 depends on NUMA
320 default y
323 config ARCH_DISCONTIGMEM_ENABLE
324 def_bool y
325 depends on NUMA
327 config ARCH_DISCONTIGMEM_DEFAULT
328 def_bool y
329 depends on NUMA
331 config ARCH_SPARSEMEM_ENABLE
332 def_bool y
333 depends on (NUMA || EXPERIMENTAL)
335 config ARCH_MEMORY_PROBE
336 def_bool y
337 depends on MEMORY_HOTPLUG
339 config ARCH_FLATMEM_ENABLE
340 def_bool y
341 depends on !NUMA
343 source "mm/Kconfig"
345 config HAVE_ARCH_EARLY_PFN_TO_NID
346 def_bool y
347 depends on NUMA
349 config NR_CPUS
350 int "Maximum number of CPUs (2-256)"
351 range 2 256
352 depends on SMP
353 default "16" if X86_64_XEN
354 default "8"
355 help
356 This allows you to specify the maximum number of CPUs which this
357 kernel will support. Current maximum is 256 CPUs due to
358 APIC addressing limits. Less depending on the hardware.
360 This is purely to save memory - each supported CPU requires
361 memory in the static kernel configuration.
363 config HOTPLUG_CPU
364 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
365 depends on SMP && HOTPLUG && EXPERIMENTAL
366 help
367 Say Y here to experiment with turning CPUs off and on. CPUs
368 can be controlled through /sys/devices/system/cpu/cpu#.
369 Say N if you want to disable CPU hotplug.
372 config HPET_TIMER
373 bool
374 depends on !X86_64_XEN
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>.
384 config HPET_EMULATE_RTC
385 bool "Provide RTC interrupt"
386 depends on HPET_TIMER && RTC=y
388 config GART_IOMMU
389 bool "K8 GART IOMMU support"
390 default y
391 select SWIOTLB
392 depends on PCI && !X86_64_XEN
393 help
394 Support the IOMMU. Needed to run systems with more than 3GB of memory
395 properly with 32-bit PCI devices that do not support DAC (Double Address
396 Cycle). The IOMMU can be turned off at runtime with the iommu=off parameter.
397 Normally the kernel will take the right choice by itself.
398 This option includes a driver for the AMD Opteron/Athlon64 northbridge IOMMU
399 and a software emulation used on other systems.
400 If unsure, say Y.
402 # need this always enabled with GART_IOMMU for the VIA workaround
403 config SWIOTLB
404 bool
405 default y
406 depends on GART_IOMMU
408 config X86_MCE
409 bool "Machine check support" if EMBEDDED
410 depends on !X86_64_XEN
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
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.
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.
434 config KEXEC
435 bool "kexec system call (EXPERIMENTAL)"
436 depends on EXPERIMENTAL && !X86_64_XEN
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.
443 The name comes from the similiarity to the exec system call.
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.
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.
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 "0x100000"
461 help
462 This gives the physical address where the kernel is loaded. Normally
463 for regular kernels this value is 0x100000 (1MB). 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.
474 Don't change this unless you know what you are doing.
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.
491 If unsure, say Y. Only embedded should say N here.
493 source kernel/Kconfig.hz
495 endmenu
497 #
498 # Use the generic interrupt handling code in kernel/irq/:
499 #
500 config GENERIC_HARDIRQS
501 bool
502 default y
504 config GENERIC_IRQ_PROBE
505 bool
506 default y
508 # we have no ISA slots, but we do have ISA-style DMA.
509 config ISA_DMA_API
510 bool
511 default y
513 config GENERIC_PENDING_IRQ
514 bool
515 depends on GENERIC_HARDIRQS && SMP
516 default y
518 menu "Power management options"
519 depends on !XEN_UNPRIVILEGED_GUEST
521 if !X86_64_XEN
522 source kernel/power/Kconfig
523 endif
525 source "drivers/acpi/Kconfig"
527 source "arch/x86_64/kernel/cpufreq/Kconfig"
529 endmenu
531 menu "Bus options (PCI etc.)"
533 config PCI
534 bool "PCI support"
536 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
537 config PCI_DIRECT
538 bool
539 depends on PCI
540 default y
542 config PCI_MMCONFIG
543 bool "Support mmconfig PCI config space access"
544 depends on PCI && ACPI
546 config XEN_PCIDEV_FRONTEND
547 bool "Xen PCI Frontend"
548 depends on PCI && X86_64_XEN
549 default y
550 help
551 The PCI device frontend driver allows the kernel to import arbitrary
552 PCI devices from a PCI backend to support PCI driver domains.
554 config XEN_PCIDEV_FE_DEBUG
555 bool "Xen PCI Frontend Debugging"
556 depends on XEN_PCIDEV_FRONTEND
557 default n
558 help
559 Enables some debug statements within the PCI Frontend.
561 config UNORDERED_IO
562 bool "Unordered IO mapping access"
563 depends on EXPERIMENTAL
564 help
565 Use unordered stores to access IO memory mappings in device drivers.
566 Still very experimental. When a driver works on IA64/ppc64/pa-risc it should
567 work with this option, but it makes the drivers behave differently
568 from i386. Requires that the driver writer used memory barriers
569 properly.
571 source "drivers/pci/pcie/Kconfig"
573 source "drivers/pci/Kconfig"
575 source "drivers/pcmcia/Kconfig"
577 source "drivers/pci/hotplug/Kconfig"
579 endmenu
582 menu "Executable file formats / Emulations"
584 source "fs/Kconfig.binfmt"
586 config IA32_EMULATION
587 bool "IA32 Emulation"
588 help
589 Include code to run 32-bit programs under a 64-bit kernel. You should likely
590 turn this on, unless you're 100% sure that you don't have any 32-bit programs
591 left.
593 config IA32_AOUT
594 tristate "IA32 a.out support"
595 depends on IA32_EMULATION
596 help
597 Support old a.out binaries in the 32bit emulation.
599 config COMPAT
600 bool
601 depends on IA32_EMULATION
602 default y
604 config SYSVIPC_COMPAT
605 bool
606 depends on COMPAT && SYSVIPC
607 default y
609 endmenu
611 source "net/Kconfig"
613 source drivers/Kconfig
615 source "drivers/firmware/Kconfig"
617 source fs/Kconfig
619 menu "Instrumentation Support"
620 depends on EXPERIMENTAL
622 source "arch/x86_64/oprofile/Kconfig"
624 config KPROBES
625 bool "Kprobes (EXPERIMENTAL)"
626 depends on EXPERIMENTAL && MODULES
627 help
628 Kprobes allows you to trap at almost any kernel address and
629 execute a callback function. register_kprobe() establishes
630 a probepoint and specifies the callback. Kprobes is useful
631 for kernel debugging, non-intrusive instrumentation and testing.
632 If in doubt, say "N".
633 endmenu
635 source "arch/x86_64/Kconfig.debug"
637 source "security/Kconfig"
639 source "crypto/Kconfig"
641 source "drivers/xen/Kconfig"
643 source "lib/Kconfig"