ia64/linux-2.6.18-xen.hg

view arch/x86_64/Kconfig @ 854:950b9eb27661

usbback: fix urb interval value for interrupt urbs.

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