]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blame - arch/x86/Kconfig
Merge branch 'sh/for-2.6.28' of git://git.kernel.org/pub/scm/linux/kernel/git/lethal...
[mirror_ubuntu-bionic-kernel.git] / arch / x86 / Kconfig
CommitLineData
1032c0ba 1# x86 configuration
daa93fab
SR
2mainmenu "Linux Kernel Configuration for x86"
3
4# Select 32 or 64 bit
5config 64BIT
6840999b
SR
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
daa93fab
SR
8 help
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
11
12config X86_32
13 def_bool !64BIT
14
15config X86_64
16 def_bool 64BIT
1032c0ba
SR
17
18### Arch settings
8d5fffb9 19config X86
3c2362e6 20 def_bool y
e17c6d56 21 select HAVE_AOUT if X86_32
a5574cf6 22 select HAVE_UNSTABLE_SCHED_CLOCK
ec7748b5 23 select HAVE_IDE
42d4b839 24 select HAVE_OPROFILE
28b2ee20 25 select HAVE_IOREMAP_PROT
3f550096 26 select HAVE_KPROBES
1f972768 27 select ARCH_WANT_OPTIONAL_GPIOLIB
9edddaa2 28 select HAVE_KRETPROBES
e4b2b886 29 select HAVE_FTRACE_MCOUNT_RECORD
677aa9f7 30 select HAVE_DYNAMIC_FTRACE
606576ce 31 select HAVE_FUNCTION_TRACER
1a4e3f89 32 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
fcbc04c0 33 select HAVE_ARCH_KGDB if !X86_VOYAGER
99bbc4b1 34 select HAVE_ARCH_TRACEHOOK
323ec001 35 select HAVE_GENERIC_DMA_COHERENT if X86_32
58340a07 36 select HAVE_EFFICIENT_UNALIGNED_ACCESS
7d8330a5 37
73531905 38config ARCH_DEFCONFIG
b9b39bfb 39 string
73531905
SR
40 default "arch/x86/configs/i386_defconfig" if X86_32
41 default "arch/x86/configs/x86_64_defconfig" if X86_64
b9b39bfb 42
8d5fffb9 43config GENERIC_TIME
3c2362e6 44 def_bool y
8d5fffb9
SR
45
46config GENERIC_CMOS_UPDATE
3c2362e6 47 def_bool y
8d5fffb9
SR
48
49config CLOCKSOURCE_WATCHDOG
3c2362e6 50 def_bool y
8d5fffb9
SR
51
52config GENERIC_CLOCKEVENTS
3c2362e6 53 def_bool y
8d5fffb9
SR
54
55config GENERIC_CLOCKEVENTS_BROADCAST
3c2362e6 56 def_bool y
8d5fffb9
SR
57 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
58
59config LOCKDEP_SUPPORT
3c2362e6 60 def_bool y
8d5fffb9
SR
61
62config STACKTRACE_SUPPORT
3c2362e6 63 def_bool y
8d5fffb9 64
aa7d9350
HC
65config HAVE_LATENCYTOP_SUPPORT
66 def_bool y
67
1f84260c
CL
68config FAST_CMPXCHG_LOCAL
69 bool
70 default y
71
8d5fffb9 72config MMU
3c2362e6 73 def_bool y
8d5fffb9
SR
74
75config ZONE_DMA
3c2362e6 76 def_bool y
8d5fffb9 77
8d5fffb9
SR
78config SBUS
79 bool
80
81config GENERIC_ISA_DMA
3c2362e6 82 def_bool y
8d5fffb9
SR
83
84config GENERIC_IOMAP
3c2362e6 85 def_bool y
8d5fffb9
SR
86
87config GENERIC_BUG
3c2362e6 88 def_bool y
8d5fffb9
SR
89 depends on BUG
90
91config GENERIC_HWEIGHT
3c2362e6 92 def_bool y
8d5fffb9 93
a6082959 94config GENERIC_GPIO
9ba16087 95 bool
a6082959 96
8d5fffb9 97config ARCH_MAY_HAVE_PC_FDC
3c2362e6 98 def_bool y
8d5fffb9 99
1032c0ba
SR
100config RWSEM_GENERIC_SPINLOCK
101 def_bool !X86_XADD
102
103config RWSEM_XCHGADD_ALGORITHM
104 def_bool X86_XADD
105
a6869cc4
VP
106config ARCH_HAS_CPU_IDLE_WAIT
107 def_bool y
108
1032c0ba
SR
109config GENERIC_CALIBRATE_DELAY
110 def_bool y
111
8d5fffb9
SR
112config GENERIC_TIME_VSYSCALL
113 bool
114 default X86_64
115
9a0b8415 116config ARCH_HAS_CPU_RELAX
117 def_bool y
118
89cedfef
VP
119config ARCH_HAS_DEFAULT_IDLE
120 def_bool y
121
1b27d05b
PE
122config ARCH_HAS_CACHE_LINE_SIZE
123 def_bool y
124
dd5af90a 125config HAVE_SETUP_PER_CPU_AREA
23ca4bba 126 def_bool X86_64_SMP || (X86_SMP && !X86_VOYAGER)
b32ef636 127
9f0e8d04
MT
128config HAVE_CPUMASK_OF_CPU_MAP
129 def_bool X86_64_SMP
130
801e4062
JB
131config ARCH_HIBERNATION_POSSIBLE
132 def_bool y
133 depends on !SMP || !X86_VOYAGER
134
f4cb5700
JB
135config ARCH_SUSPEND_POSSIBLE
136 def_bool y
137 depends on !X86_VOYAGER
138
8d5fffb9
SR
139config ZONE_DMA32
140 bool
141 default X86_64
142
143config ARCH_POPULATES_NODE_MAP
144 def_bool y
145
146config AUDIT_ARCH
147 bool
148 default X86_64
149
765c68bd
IM
150config ARCH_SUPPORTS_OPTIMIZED_INLINING
151 def_bool y
152
8d5fffb9
SR
153# Use the generic interrupt handling code in kernel/irq/:
154config GENERIC_HARDIRQS
155 bool
156 default y
157
158config GENERIC_IRQ_PROBE
159 bool
160 default y
161
162config GENERIC_PENDING_IRQ
163 bool
164 depends on GENERIC_HARDIRQS && SMP
165 default y
166
167config X86_SMP
168 bool
6b0c3d44 169 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
3b16cf87 170 select USE_GENERIC_SMP_HELPERS
8d5fffb9
SR
171 default y
172
6b0c3d44
SR
173config X86_32_SMP
174 def_bool y
175 depends on X86_32 && SMP
176
177config X86_64_SMP
178 def_bool y
179 depends on X86_64 && SMP
180
8d5fffb9
SR
181config X86_HT
182 bool
ee0011a7 183 depends on SMP
efefa6f6 184 depends on (X86_32 && !X86_VOYAGER) || X86_64
8d5fffb9
SR
185 default y
186
187config X86_BIOS_REBOOT
188 bool
31ac409a 189 depends on !X86_VOYAGER
8d5fffb9
SR
190 default y
191
192config X86_TRAMPOLINE
193 bool
e44b7b75 194 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
8d5fffb9
SR
195 default y
196
197config KTIME_SCALAR
198 def_bool X86_32
506f1d07 199source "init/Kconfig"
dc52ddc0 200source "kernel/Kconfig.freezer"
8d5fffb9 201
506f1d07
SR
202menu "Processor type and features"
203
204source "kernel/time/Kconfig"
205
206config 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 Note that if you say Y here and choose architecture "586" or
220 "Pentium" under "Processor family", the kernel will not work on 486
221 architectures. Similarly, multiprocessor kernels for the "PPro"
222 architecture may not work on all Pentium based boards.
223
224 People using multiprocessor machines who say Y here should also say
225 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
226 Management" code will be disabled if you say Y here.
227
03502faa 228 See also <file:Documentation/i386/IO-APIC.txt>,
506f1d07
SR
229 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
230 <http://www.tldp.org/docs.html#howto>.
231
232 If you don't know what to do here, say N.
233
b3572e36
JB
234config X86_HAS_BOOT_CPU_ID
235 def_bool y
236 depends on X86_VOYAGER
237
6695c85b
YL
238config X86_FIND_SMP_CONFIG
239 def_bool y
1b84e1c8 240 depends on X86_MPPARSE || X86_VOYAGER
6695c85b
YL
241
242if ACPI
243config X86_MPPARSE
244 def_bool y
245 bool "Enable MPS table"
5ab74722 246 depends on X86_LOCAL_APIC
6695c85b
YL
247 help
248 For old smp systems that do not have proper acpi support. Newer systems
249 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
250endif
251
252if !ACPI
253config X86_MPPARSE
254 def_bool y
5ab74722 255 depends on X86_LOCAL_APIC
6695c85b
YL
256endif
257
506f1d07
SR
258choice
259 prompt "Subarchitecture Type"
260 default X86_PC
261
262config X86_PC
263 bool "PC-compatible"
264 help
265 Choose this option if your computer is a standard PC or compatible.
266
267config X86_ELAN
268 bool "AMD Elan"
269 depends on X86_32
270 help
271 Select this for an AMD Elan processor.
272
273 Do not use this option for K6/Athlon/Opteron processors!
274
275 If unsure, choose "PC-compatible" instead.
276
277config X86_VOYAGER
278 bool "Voyager (NCR)"
1ac97018 279 depends on X86_32 && (SMP || BROKEN) && !PCI
506f1d07
SR
280 help
281 Voyager is an MCA-based 32-way capable SMP architecture proprietary
282 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
283
284 *** WARNING ***
285
286 If you do not specifically know you have a Voyager based machine,
287 say N here, otherwise the kernel you build will not be bootable.
288
506f1d07 289config X86_GENERICARCH
d49c4288 290 bool "Generic architecture"
506f1d07
SR
291 depends on X86_32
292 help
d49c4288
YL
293 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
294 subarchitectures. It is intended for a generic binary kernel.
295 if you select them all, kernel will probe it one by one. and will
296 fallback to default.
297
298if X86_GENERICARCH
299
506f1d07
SR
300config X86_NUMAQ
301 bool "NUMAQ (IBM/Sequent)"
3de352bb 302 depends on SMP && X86_32 && PCI && X86_MPPARSE
506f1d07 303 select NUMA
506f1d07 304 help
d49c4288
YL
305 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
306 NUMA multiquad box. This changes the way that processors are
307 bootstrapped, and uses Clustered Logical APIC addressing mode instead
308 of Flat Logical. You will need a new lynxer.elf file to flash your
309 firmware with - send email to <Martin.Bligh@us.ibm.com>.
506f1d07
SR
310
311config X86_SUMMIT
312 bool "Summit/EXA (IBM x440)"
313 depends on X86_32 && SMP
314 help
315 This option is needed for IBM systems that use the Summit/EXA chipset.
316 In particular, it is needed for the x440.
317
506f1d07
SR
318config X86_ES7000
319 bool "Support for Unisys ES7000 IA32 series"
320 depends on X86_32 && SMP
321 help
322 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
323 supposed to run on an IA32-based Unisys ES7000 system.
506f1d07
SR
324
325config X86_BIGSMP
d49c4288 326 bool "Support for big SMP systems with more than 8 CPUs"
506f1d07
SR
327 depends on X86_32 && SMP
328 help
329 This option is needed for the systems that have more than 8 CPUs
330 and if the system is not of any sub-arch type above.
331
d49c4288 332endif
506f1d07
SR
333
334config X86_VSMP
335 bool "Support for ScaleMP vSMP"
96597fd2 336 select PARAVIRT
a6784ad7 337 depends on X86_64 && PCI
96597fd2 338 help
506f1d07
SR
339 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
340 supposed to run on these EM64T-based machines. Only choose this option
341 if you have one of these machines.
342
343endchoice
344
1b84e1c8
IM
345config X86_VISWS
346 bool "SGI 320/540 (Visual Workstation)"
39415a44 347 depends on X86_32 && PCI && !X86_VOYAGER && X86_MPPARSE && PCI_GODIRECT
1b84e1c8
IM
348 help
349 The SGI Visual Workstation series is an IA32-based workstation
350 based on SGI systems chips with some legacy PC hardware attached.
351
352 Say Y here to create a kernel to run on the SGI 320 or 540.
353
354 A kernel compiled for the Visual Workstation will run on general
355 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
356
1f972768
IM
357config X86_RDC321X
358 bool "RDC R-321x SoC"
359 depends on X86_32
360 select M486
361 select X86_REBOOTFIXUPS
362 help
363 This option is needed for RDC R-321x system-on-chip, also known
364 as R-8610-(G).
365 If you don't have one of these chips, you should say N here.
366
506f1d07 367config SCHED_NO_NO_OMIT_FRAME_POINTER
3c2362e6
HH
368 def_bool y
369 prompt "Single-depth WCHAN output"
506f1d07
SR
370 depends on X86_32
371 help
372 Calculate simpler /proc/<PID>/wchan values. If this option
373 is disabled then wchan values will recurse back to the
374 caller function. This provides more accurate wchan values,
375 at the expense of slightly more scheduling overhead.
376
377 If in doubt, say "Y".
378
506f1d07
SR
379menuconfig PARAVIRT_GUEST
380 bool "Paravirtualized guest support"
506f1d07
SR
381 help
382 Say Y here to get to see options related to running Linux under
383 various hypervisors. This option alone does not add any kernel code.
384
385 If you say N, all options in this submenu will be skipped and disabled.
386
387if PARAVIRT_GUEST
388
389source "arch/x86/xen/Kconfig"
390
391config VMI
392 bool "VMI Guest support"
393 select PARAVIRT
42d545c9 394 depends on X86_32
efefa6f6 395 depends on !X86_VOYAGER
506f1d07
SR
396 help
397 VMI provides a paravirtualized interface to the VMware ESX server
398 (it could be used by other hypervisors in theory too, but is not
399 at the moment), by linking the kernel to a GPL-ed ROM module
400 provided by the hypervisor.
401
790c73f6
GOC
402config KVM_CLOCK
403 bool "KVM paravirtualized clock"
404 select PARAVIRT
f6e16d5a 405 select PARAVIRT_CLOCK
efefa6f6 406 depends on !X86_VOYAGER
790c73f6
GOC
407 help
408 Turning on this option will allow you to run a paravirtualized clock
409 when running over the KVM hypervisor. Instead of relying on a PIT
410 (or probably other) emulation by the underlying device model, the host
411 provides the guest with timing infrastructure such as time of day, and
412 system time
413
0cf1bfd2
MT
414config KVM_GUEST
415 bool "KVM Guest support"
416 select PARAVIRT
efefa6f6 417 depends on !X86_VOYAGER
0cf1bfd2
MT
418 help
419 This option enables various optimizations for running under the KVM
420 hypervisor.
421
506f1d07
SR
422source "arch/x86/lguest/Kconfig"
423
e61bd94a
EPH
424config PARAVIRT
425 bool "Enable paravirtualization code"
efefa6f6 426 depends on !X86_VOYAGER
e61bd94a
EPH
427 help
428 This changes the kernel so it can modify itself when it is run
429 under a hypervisor, potentially improving performance significantly
430 over full virtualization. However, when run without a hypervisor
431 the kernel is theoretically slower and slightly larger.
432
7af192c9
GH
433config PARAVIRT_CLOCK
434 bool
435 default n
436
506f1d07
SR
437endif
438
97349135
JF
439config PARAVIRT_DEBUG
440 bool "paravirt-ops debugging"
441 depends on PARAVIRT && DEBUG_KERNEL
442 help
443 Enable to debug paravirt_ops internals. Specifically, BUG if
444 a paravirt_op is missing when it is called.
445
03273184
YL
446config MEMTEST
447 bool "Memtest"
c64df707
YL
448 help
449 This option adds a kernel parameter 'memtest', which allows memtest
03273184
YL
450 to be set.
451 memtest=0, mean disabled; -- default
452 memtest=1, mean do 1 test pattern;
453 ...
454 memtest=4, mean do 4 test patterns.
aba3728c 455 If you are unsure how to answer this question, answer N.
506f1d07
SR
456
457config X86_SUMMIT_NUMA
3c2362e6 458 def_bool y
0699eae1 459 depends on X86_32 && NUMA && X86_GENERICARCH
506f1d07
SR
460
461config X86_CYCLONE_TIMER
3c2362e6 462 def_bool y
0699eae1 463 depends on X86_GENERICARCH
506f1d07
SR
464
465config ES7000_CLUSTERED_APIC
3c2362e6 466 def_bool y
506f1d07
SR
467 depends on SMP && X86_ES7000 && MPENTIUMIII
468
469source "arch/x86/Kconfig.cpu"
470
471config HPET_TIMER
3c2362e6 472 def_bool X86_64
506f1d07 473 prompt "HPET Timer Support" if X86_32
506f1d07
SR
474 help
475 Use the IA-PC HPET (High Precision Event Timer) to manage
476 time in preference to the PIT and RTC, if a HPET is
477 present.
478 HPET is the next generation timer replacing legacy 8254s.
479 The HPET provides a stable time base on SMP
480 systems, unlike the TSC, but it is more expensive to access,
481 as it is off-chip. You can find the HPET spec at
482 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
483
484 You can safely choose Y here. However, HPET will only be
485 activated if the platform and the BIOS support this feature.
486 Otherwise the 8254 will be used for timing services.
487
488 Choose N to continue using the legacy 8254 timer.
489
490config HPET_EMULATE_RTC
3c2362e6 491 def_bool y
9d8af78b 492 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
506f1d07
SR
493
494# Mark as embedded because too many people got it wrong.
495# The code disables itself when not needed.
7ae9392c
TP
496config DMI
497 default y
498 bool "Enable DMI scanning" if EMBEDDED
499 help
500 Enabled scanning of DMI to identify machine quirks. Say Y
501 here unless you have verified that your setup is not
502 affected by entries in the DMI blacklist. Required by PNP
503 BIOS code.
504
506f1d07
SR
505config GART_IOMMU
506 bool "GART IOMMU support" if EMBEDDED
507 default y
508 select SWIOTLB
509 select AGP
510 depends on X86_64 && PCI
511 help
512 Support for full DMA access of devices with 32bit memory access only
513 on systems with more than 3GB. This is usually needed for USB,
514 sound, many IDE/SATA chipsets and some other devices.
515 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
516 based hardware IOMMU and a software bounce buffer based IOMMU used
517 on Intel systems and as fallback.
518 The code is only active when needed (enough memory and limited
519 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
520 too.
521
522config CALGARY_IOMMU
523 bool "IBM Calgary IOMMU support"
524 select SWIOTLB
525 depends on X86_64 && PCI && EXPERIMENTAL
526 help
527 Support for hardware IOMMUs in IBM's xSeries x366 and x460
528 systems. Needed to run systems with more than 3GB of memory
529 properly with 32-bit PCI devices that do not support DAC
530 (Double Address Cycle). Calgary also supports bus level
531 isolation, where all DMAs pass through the IOMMU. This
532 prevents them from going anywhere except their intended
533 destination. This catches hard-to-find kernel bugs and
534 mis-behaving drivers and devices that do not use the DMA-API
535 properly to set up their DMA buffers. The IOMMU can be
536 turned off at boot time with the iommu=off parameter.
537 Normally the kernel will make the right choice by itself.
538 If unsure, say Y.
539
540config CALGARY_IOMMU_ENABLED_BY_DEFAULT
3c2362e6
HH
541 def_bool y
542 prompt "Should Calgary be enabled by default?"
506f1d07
SR
543 depends on CALGARY_IOMMU
544 help
545 Should Calgary be enabled by default? if you choose 'y', Calgary
546 will be used (if it exists). If you choose 'n', Calgary will not be
547 used even if it exists. If you choose 'n' and would like to use
548 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
549 If unsure, say Y.
550
2b188723
JR
551config AMD_IOMMU
552 bool "AMD IOMMU support"
07c40e8a 553 select SWIOTLB
a80dc3e0 554 select PCI_MSI
24d2ba0a 555 depends on X86_64 && PCI && ACPI
2b188723 556 help
18d22200
JR
557 With this option you can enable support for AMD IOMMU hardware in
558 your system. An IOMMU is a hardware component which provides
559 remapping of DMA memory accesses from devices. With an AMD IOMMU you
560 can isolate the the DMA memory of different devices and protect the
561 system from misbehaving device drivers or hardware.
562
563 You can find out if your system has an AMD IOMMU if you look into
564 your BIOS for an option to enable it or if you have an IVRS ACPI
565 table.
2b188723 566
506f1d07
SR
567# need this always selected by IOMMU for the VIA workaround
568config SWIOTLB
569 bool
570 help
571 Support for software bounce buffers used on x86-64 systems
572 which don't have a hardware IOMMU (e.g. the current generation
573 of Intel's x86-64 CPUs). Using this PCI devices which can only
574 access 32-bits of memory can be used on systems with more than
575 3 GB of memory. If unsure, say Y.
576
a8522509 577config IOMMU_HELPER
18b743dc 578 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
d25e26b6 579
1184dc2f
MT
580config MAXSMP
581 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
d25e26b6 582 depends on X86_64 && SMP && BROKEN
1184dc2f
MT
583 default n
584 help
585 Configure maximum number of CPUS and NUMA Nodes for this architecture.
586 If unsure, say N.
506f1d07
SR
587
588config NR_CPUS
d25e26b6
LT
589 int "Maximum number of CPUs (2-512)" if !MAXSMP
590 range 2 512
506f1d07 591 depends on SMP
d25e26b6 592 default "4096" if MAXSMP
506f1d07
SR
593 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
594 default "8"
595 help
596 This allows you to specify the maximum number of CPUs which this
d25e26b6 597 kernel will support. The maximum supported value is 512 and the
506f1d07
SR
598 minimum value which makes sense is 2.
599
600 This is purely to save memory - each supported CPU adds
601 approximately eight kilobytes to the kernel image.
602
603config SCHED_SMT
604 bool "SMT (Hyperthreading) scheduler support"
b089c12b 605 depends on X86_HT
506f1d07
SR
606 help
607 SMT scheduler support improves the CPU scheduler's decision making
608 when dealing with Intel Pentium 4 chips with HyperThreading at a
609 cost of slightly increased overhead in some places. If unsure say
610 N here.
611
612config SCHED_MC
3c2362e6
HH
613 def_bool y
614 prompt "Multi-core scheduler support"
b089c12b 615 depends on X86_HT
506f1d07
SR
616 help
617 Multi-core scheduler support improves the CPU scheduler's decision
618 making when dealing with multi-core CPU chips at a cost of slightly
619 increased overhead in some places. If unsure say N here.
620
621source "kernel/Kconfig.preempt"
622
623config X86_UP_APIC
624 bool "Local APIC support on uniprocessors"
efefa6f6 625 depends on X86_32 && !SMP && !(X86_VOYAGER || X86_GENERICARCH)
506f1d07
SR
626 help
627 A local APIC (Advanced Programmable Interrupt Controller) is an
628 integrated interrupt controller in the CPU. If you have a single-CPU
629 system which has a processor with a local APIC, you can say Y here to
630 enable and use it. If you say Y here even though your machine doesn't
631 have a local APIC, then the kernel will still run with no slowdown at
632 all. The local APIC supports CPU-generated self-interrupts (timer,
633 performance counters), and the NMI watchdog which detects hard
634 lockups.
635
636config X86_UP_IOAPIC
637 bool "IO-APIC support on uniprocessors"
638 depends on X86_UP_APIC
639 help
640 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
641 SMP-capable replacement for PC-style interrupt controllers. Most
642 SMP systems and many recent uniprocessor systems have one.
643
644 If you have a single-CPU system with an IO-APIC, you can say Y here
645 to use it. If you say Y here even though your machine doesn't have
646 an IO-APIC, then the kernel will still run with no slowdown at all.
647
648config X86_LOCAL_APIC
3c2362e6 649 def_bool y
efefa6f6 650 depends on X86_64 || (X86_32 && (X86_UP_APIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
506f1d07
SR
651
652config X86_IO_APIC
3c2362e6 653 def_bool y
efefa6f6 654 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
506f1d07
SR
655
656config X86_VISWS_APIC
3c2362e6 657 def_bool y
506f1d07 658 depends on X86_32 && X86_VISWS
506f1d07
SR
659
660config X86_MCE
661 bool "Machine Check Exception"
662 depends on !X86_VOYAGER
663 ---help---
664 Machine Check Exception support allows the processor to notify the
665 kernel if it detects a problem (e.g. overheating, component failure).
666 The action the kernel takes depends on the severity of the problem,
667 ranging from a warning message on the console, to halting the machine.
668 Your processor must be a Pentium or newer to support this - check the
669 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
670 have a design flaw which leads to false MCE events - hence MCE is
671 disabled on all P5 processors, unless explicitly enabled with "mce"
672 as a boot argument. Similarly, if MCE is built in and creates a
673 problem on some new non-standard machine, you can boot with "nomce"
674 to disable it. MCE support simply ignores non-MCE processors like
675 the 386 and 486, so nearly everyone can say Y here.
676
677config X86_MCE_INTEL
3c2362e6
HH
678 def_bool y
679 prompt "Intel MCE features"
506f1d07 680 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
506f1d07
SR
681 help
682 Additional support for intel specific MCE features such as
683 the thermal monitor.
684
685config X86_MCE_AMD
3c2362e6
HH
686 def_bool y
687 prompt "AMD MCE features"
506f1d07 688 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
506f1d07
SR
689 help
690 Additional support for AMD specific MCE features such as
691 the DRAM Error Threshold.
692
693config X86_MCE_NONFATAL
694 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
695 depends on X86_32 && X86_MCE
696 help
697 Enabling this feature starts a timer that triggers every 5 seconds which
698 will look at the machine check registers to see if anything happened.
699 Non-fatal problems automatically get corrected (but still logged).
700 Disable this if you don't want to see these messages.
701 Seeing the messages this option prints out may be indicative of dying
702 or out-of-spec (ie, overclocked) hardware.
703 This option only does something on certain CPUs.
704 (AMD Athlon/Duron and Intel Pentium 4)
705
706config X86_MCE_P4THERMAL
707 bool "check for P4 thermal throttling interrupt."
efefa6f6 708 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP)
506f1d07
SR
709 help
710 Enabling this feature will cause a message to be printed when the P4
711 enters thermal throttling.
712
713config VM86
714 bool "Enable VM86 support" if EMBEDDED
715 default y
716 depends on X86_32
717 help
718 This option is required by programs like DOSEMU to run 16-bit legacy
719 code on X86 processors. It also may be needed by software like
720 XFree86 to initialize some video cards via BIOS. Disabling this
721 option saves about 6k.
722
723config TOSHIBA
724 tristate "Toshiba Laptop support"
725 depends on X86_32
726 ---help---
727 This adds a driver to safely access the System Management Mode of
728 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
729 not work on models with a Phoenix BIOS. The System Management Mode
730 is used to set the BIOS and power saving options on Toshiba portables.
731
732 For information on utilities to make use of this driver see the
733 Toshiba Linux utilities web site at:
734 <http://www.buzzard.org.uk/toshiba/>.
735
736 Say Y if you intend to run this kernel on a Toshiba portable.
737 Say N otherwise.
738
739config I8K
740 tristate "Dell laptop support"
506f1d07
SR
741 ---help---
742 This adds a driver to safely access the System Management Mode
743 of the CPU on the Dell Inspiron 8000. The System Management Mode
744 is used to read cpu temperature and cooling fan status and to
745 control the fans on the I8K portables.
746
747 This driver has been tested only on the Inspiron 8000 but it may
748 also work with other Dell laptops. You can force loading on other
749 models by passing the parameter `force=1' to the module. Use at
750 your own risk.
751
752 For information on utilities to make use of this driver see the
753 I8K Linux utilities web site at:
754 <http://people.debian.org/~dz/i8k/>
755
756 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
757 Say N otherwise.
758
759config X86_REBOOTFIXUPS
9ba16087
JB
760 bool "Enable X86 board specific fixups for reboot"
761 depends on X86_32
506f1d07
SR
762 ---help---
763 This enables chipset and/or board specific fixups to be done
764 in order to get reboot to work correctly. This is only needed on
765 some combinations of hardware and BIOS. The symptom, for which
766 this config is intended, is when reboot ends with a stalled/hung
767 system.
768
769 Currently, the only fixup is for the Geode machines using
5e3a77e9 770 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
506f1d07
SR
771
772 Say Y if you want to enable the fixup. Currently, it's safe to
773 enable this option even if you don't need it.
774 Say N otherwise.
775
776config MICROCODE
8d86f390 777 tristate "/dev/cpu/microcode - microcode support"
506f1d07
SR
778 select FW_LOADER
779 ---help---
780 If you say Y here, you will be able to update the microcode on
80cc9f10
PO
781 certain Intel and AMD processors. The Intel support is for the
782 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
783 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
784 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
785 You will obviously need the actual microcode binary data itself
786 which is not shipped with the Linux kernel.
506f1d07 787
8d86f390
PO
788 This option selects the general module only, you need to select
789 at least one vendor specific module as well.
506f1d07
SR
790
791 To compile this driver as a module, choose M here: the
792 module will be called microcode.
793
8d86f390 794config MICROCODE_INTEL
18dbc916 795 bool "Intel microcode patch loading support"
8d86f390
PO
796 depends on MICROCODE
797 default MICROCODE
798 select FW_LOADER
799 --help---
800 This options enables microcode patch loading support for Intel
801 processors.
802
803 For latest news and information on obtaining all the required
804 Intel ingredients for this driver, check:
805 <http://www.urbanmyth.org/microcode/>.
806
80cc9f10 807config MICROCODE_AMD
18dbc916 808 bool "AMD microcode patch loading support"
80cc9f10
PO
809 depends on MICROCODE
810 select FW_LOADER
811 --help---
812 If you select this option, microcode patch loading support for AMD
813 processors will be enabled.
814
8d86f390 815 config MICROCODE_OLD_INTERFACE
3c2362e6 816 def_bool y
506f1d07 817 depends on MICROCODE
506f1d07
SR
818
819config X86_MSR
820 tristate "/dev/cpu/*/msr - Model-specific register support"
821 help
822 This device gives privileged processes access to the x86
823 Model-Specific Registers (MSRs). It is a character device with
824 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
825 MSR accesses are directed to a specific CPU on multi-processor
826 systems.
827
828config X86_CPUID
829 tristate "/dev/cpu/*/cpuid - CPU information support"
830 help
831 This device gives processes access to the x86 CPUID instruction to
832 be executed on a specific processor. It is a character device
833 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
834 /dev/cpu/31/cpuid.
835
836choice
837 prompt "High Memory Support"
838 default HIGHMEM4G if !X86_NUMAQ
839 default HIGHMEM64G if X86_NUMAQ
840 depends on X86_32
841
842config NOHIGHMEM
843 bool "off"
844 depends on !X86_NUMAQ
845 ---help---
846 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
847 However, the address space of 32-bit x86 processors is only 4
848 Gigabytes large. That means that, if you have a large amount of
849 physical memory, not all of it can be "permanently mapped" by the
850 kernel. The physical memory that's not permanently mapped is called
851 "high memory".
852
853 If you are compiling a kernel which will never run on a machine with
854 more than 1 Gigabyte total physical RAM, answer "off" here (default
855 choice and suitable for most users). This will result in a "3GB/1GB"
856 split: 3GB are mapped so that each process sees a 3GB virtual memory
857 space and the remaining part of the 4GB virtual memory space is used
858 by the kernel to permanently map as much physical memory as
859 possible.
860
861 If the machine has between 1 and 4 Gigabytes physical RAM, then
862 answer "4GB" here.
863
864 If more than 4 Gigabytes is used then answer "64GB" here. This
865 selection turns Intel PAE (Physical Address Extension) mode on.
866 PAE implements 3-level paging on IA32 processors. PAE is fully
867 supported by Linux, PAE mode is implemented on all recent Intel
868 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
869 then the kernel will not boot on CPUs that don't support PAE!
870
871 The actual amount of total physical memory will either be
872 auto detected or can be forced by using a kernel command line option
873 such as "mem=256M". (Try "man bootparam" or see the documentation of
874 your boot loader (lilo or loadlin) about how to pass options to the
875 kernel at boot time.)
876
877 If unsure, say "off".
878
879config HIGHMEM4G
880 bool "4GB"
881 depends on !X86_NUMAQ
882 help
883 Select this if you have a 32-bit processor and between 1 and 4
884 gigabytes of physical RAM.
885
886config HIGHMEM64G
887 bool "64GB"
888 depends on !M386 && !M486
889 select X86_PAE
890 help
891 Select this if you have a 32-bit processor and more than 4
892 gigabytes of physical RAM.
893
894endchoice
895
896choice
897 depends on EXPERIMENTAL
898 prompt "Memory split" if EMBEDDED
899 default VMSPLIT_3G
900 depends on X86_32
901 help
902 Select the desired split between kernel and user memory.
903
904 If the address range available to the kernel is less than the
905 physical memory installed, the remaining memory will be available
906 as "high memory". Accessing high memory is a little more costly
907 than low memory, as it needs to be mapped into the kernel first.
908 Note that increasing the kernel address space limits the range
909 available to user programs, making the address space there
910 tighter. Selecting anything other than the default 3G/1G split
911 will also likely make your kernel incompatible with binary-only
912 kernel modules.
913
914 If you are not absolutely sure what you are doing, leave this
915 option alone!
916
917 config VMSPLIT_3G
918 bool "3G/1G user/kernel split"
919 config VMSPLIT_3G_OPT
920 depends on !X86_PAE
921 bool "3G/1G user/kernel split (for full 1G low memory)"
922 config VMSPLIT_2G
923 bool "2G/2G user/kernel split"
924 config VMSPLIT_2G_OPT
925 depends on !X86_PAE
926 bool "2G/2G user/kernel split (for full 2G low memory)"
927 config VMSPLIT_1G
928 bool "1G/3G user/kernel split"
929endchoice
930
931config PAGE_OFFSET
932 hex
933 default 0xB0000000 if VMSPLIT_3G_OPT
934 default 0x80000000 if VMSPLIT_2G
935 default 0x78000000 if VMSPLIT_2G_OPT
936 default 0x40000000 if VMSPLIT_1G
937 default 0xC0000000
938 depends on X86_32
939
940config HIGHMEM
3c2362e6 941 def_bool y
506f1d07 942 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
506f1d07
SR
943
944config X86_PAE
9ba16087 945 bool "PAE (Physical Address Extension) Support"
506f1d07 946 depends on X86_32 && !HIGHMEM4G
506f1d07
SR
947 help
948 PAE is required for NX support, and furthermore enables
949 larger swapspace support for non-overcommit purposes. It
950 has the cost of more pagetable lookup overhead, and also
951 consumes more pagetable space per process.
952
600715dc
JF
953config ARCH_PHYS_ADDR_T_64BIT
954 def_bool X86_64 || X86_PAE
955
506f1d07
SR
956# Common NUMA Features
957config NUMA
958 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
959 depends on SMP
4694516d 960 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && BROKEN)
506f1d07 961 default n if X86_PC
0699eae1 962 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
506f1d07
SR
963 help
964 Enable NUMA (Non Uniform Memory Access) support.
965 The kernel will try to allocate memory used by a CPU on the
966 local memory controller of the CPU and add some more
967 NUMA awareness to the kernel.
968
04b69447 969 For 32-bit this is currently highly experimental and should be only
506f1d07 970 used for kernel development. It might also cause boot failures.
04b69447 971 For 64-bit this is recommended on all multiprocessor Opteron systems.
506f1d07
SR
972 If the system is EM64T, you should say N unless your system is
973 EM64T NUMA.
974
975comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
976 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
977
978config K8_NUMA
3c2362e6
HH
979 def_bool y
980 prompt "Old style AMD Opteron NUMA detection"
981 depends on X86_64 && NUMA && PCI
982 help
506f1d07
SR
983 Enable K8 NUMA node topology detection. You should say Y here if
984 you have a multi processor AMD K8 system. This uses an old
985 method to read the NUMA configuration directly from the builtin
986 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
987 instead, which also takes priority if both are compiled in.
988
989config X86_64_ACPI_NUMA
3c2362e6
HH
990 def_bool y
991 prompt "ACPI NUMA detection"
506f1d07
SR
992 depends on X86_64 && NUMA && ACPI && PCI
993 select ACPI_NUMA
506f1d07
SR
994 help
995 Enable ACPI SRAT based node topology detection.
996
6ec6e0d9
SS
997# Some NUMA nodes have memory ranges that span
998# other nodes. Even though a pfn is valid and
999# between a node's start and end pfns, it may not
1000# reside on that node. See memmap_init_zone()
1001# for details.
1002config NODES_SPAN_OTHER_NODES
1003 def_bool y
1004 depends on X86_64_ACPI_NUMA
1005
506f1d07
SR
1006config NUMA_EMU
1007 bool "NUMA emulation"
1008 depends on X86_64 && NUMA
1009 help
1010 Enable NUMA emulation. A flat machine will be split
1011 into virtual nodes when booted with "numa=fake=N", where N is the
1012 number of nodes. This is only useful for debugging.
1013
1014config NODES_SHIFT
d25e26b6 1015 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1184dc2f 1016 range 1 9 if X86_64
d25e26b6 1017 default "9" if MAXSMP
506f1d07
SR
1018 default "6" if X86_64
1019 default "4" if X86_NUMAQ
1020 default "3"
1021 depends on NEED_MULTIPLE_NODES
1184dc2f
MT
1022 help
1023 Specify the maximum number of NUMA Nodes available on the target
1024 system. Increases memory reserved to accomodate various tables.
506f1d07
SR
1025
1026config HAVE_ARCH_BOOTMEM_NODE
3c2362e6 1027 def_bool y
506f1d07 1028 depends on X86_32 && NUMA
506f1d07
SR
1029
1030config ARCH_HAVE_MEMORY_PRESENT
3c2362e6 1031 def_bool y
506f1d07 1032 depends on X86_32 && DISCONTIGMEM
506f1d07
SR
1033
1034config NEED_NODE_MEMMAP_SIZE
3c2362e6 1035 def_bool y
506f1d07 1036 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
506f1d07
SR
1037
1038config HAVE_ARCH_ALLOC_REMAP
3c2362e6 1039 def_bool y
506f1d07 1040 depends on X86_32 && NUMA
506f1d07
SR
1041
1042config ARCH_FLATMEM_ENABLE
1043 def_bool y
99809963 1044 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA
506f1d07
SR
1045
1046config ARCH_DISCONTIGMEM_ENABLE
1047 def_bool y
b263295d 1048 depends on NUMA && X86_32
506f1d07
SR
1049
1050config ARCH_DISCONTIGMEM_DEFAULT
1051 def_bool y
b263295d
CL
1052 depends on NUMA && X86_32
1053
1054config ARCH_SPARSEMEM_DEFAULT
1055 def_bool y
1056 depends on X86_64
506f1d07
SR
1057
1058config ARCH_SPARSEMEM_ENABLE
1059 def_bool y
99809963 1060 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC) || X86_GENERICARCH
506f1d07
SR
1061 select SPARSEMEM_STATIC if X86_32
1062 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1063
1064config ARCH_SELECT_MEMORY_MODEL
1065 def_bool y
b263295d 1066 depends on ARCH_SPARSEMEM_ENABLE
506f1d07
SR
1067
1068config ARCH_MEMORY_PROBE
1069 def_bool X86_64
1070 depends on MEMORY_HOTPLUG
1071
1072source "mm/Kconfig"
1073
1074config HIGHPTE
1075 bool "Allocate 3rd-level pagetables from highmem"
1076 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1077 help
1078 The VM uses one page table entry for each page of physical memory.
1079 For systems with a lot of RAM, this can be wasteful of precious
1080 low memory. Setting this option will put user-space page table
1081 entries in high memory.
1082
9f077871
JF
1083config X86_CHECK_BIOS_CORRUPTION
1084 bool "Check for low memory corruption"
9f077871
JF
1085 help
1086 Periodically check for memory corruption in low memory, which
1087 is suspected to be caused by BIOS. Even when enabled in the
1088 configuration, it is disabled at runtime. Enable it by
1089 setting "memory_corruption_check=1" on the kernel command
1090 line. By default it scans the low 64k of memory every 60
1091 seconds; see the memory_corruption_check_size and
1092 memory_corruption_check_period parameters in
1093 Documentation/kernel-parameters.txt to adjust this.
1094
1095 When enabled with the default parameters, this option has
1096 almost no overhead, as it reserves a relatively small amount
1097 of memory and scans it infrequently. It both detects corruption
1098 and prevents it from affecting the running system.
1099
1100 It is, however, intended as a diagnostic tool; if repeatable
1101 BIOS-originated corruption always affects the same memory,
1102 you can use memmap= to prevent the kernel from using that
1103 memory.
1104
c885df50
JF
1105config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1106 bool "Set the default setting of memory_corruption_check"
1107 depends on X86_CHECK_BIOS_CORRUPTION
1108 default y
1109 help
1110 Set whether the default state of memory_corruption_check is
1111 on or off.
1112
fc381519
IM
1113config X86_RESERVE_LOW_64K
1114 bool "Reserve low 64K of RAM on AMI/Phoenix BIOSen"
1115 default y
1116 help
1117 Reserve the first 64K of physical RAM on BIOSes that are known
1118 to potentially corrupt that memory range. A numbers of BIOSes are
1119 known to utilize this area during suspend/resume, so it must not
1120 be used by the kernel.
1121
1122 Set this to N if you are absolutely sure that you trust the BIOS
1123 to get all its memory reservations and usages right.
1124
1125 If you have doubts about the BIOS (e.g. suspend/resume does not
1126 work or there's kernel crashes after certain hardware hotplug
1127 events) and it's not AMI or Phoenix, then you might want to enable
1128 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
1129 corruption patterns.
1130
1131 Say Y if unsure.
1132
506f1d07
SR
1133config MATH_EMULATION
1134 bool
1135 prompt "Math emulation" if X86_32
1136 ---help---
1137 Linux can emulate a math coprocessor (used for floating point
1138 operations) if you don't have one. 486DX and Pentium processors have
1139 a math coprocessor built in, 486SX and 386 do not, unless you added
1140 a 487DX or 387, respectively. (The messages during boot time can
1141 give you some hints here ["man dmesg"].) Everyone needs either a
1142 coprocessor or this emulation.
1143
1144 If you don't have a math coprocessor, you need to say Y here; if you
1145 say Y here even though you have a coprocessor, the coprocessor will
1146 be used nevertheless. (This behavior can be changed with the kernel
1147 command line option "no387", which comes handy if your coprocessor
1148 is broken. Try "man bootparam" or see the documentation of your boot
1149 loader (lilo or loadlin) about how to pass options to the kernel at
1150 boot time.) This means that it is a good idea to say Y here if you
1151 intend to use this kernel on different machines.
1152
1153 More information about the internals of the Linux math coprocessor
1154 emulation can be found in <file:arch/x86/math-emu/README>.
1155
1156 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1157 kernel, it won't hurt.
1158
1159config MTRR
1160 bool "MTRR (Memory Type Range Register) support"
1161 ---help---
1162 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1163 the Memory Type Range Registers (MTRRs) may be used to control
1164 processor access to memory ranges. This is most useful if you have
1165 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1166 allows bus write transfers to be combined into a larger transfer
1167 before bursting over the PCI/AGP bus. This can increase performance
1168 of image write operations 2.5 times or more. Saying Y here creates a
1169 /proc/mtrr file which may be used to manipulate your processor's
1170 MTRRs. Typically the X server should use this.
1171
1172 This code has a reasonably generic interface so that similar
1173 control registers on other processors can be easily supported
1174 as well:
1175
1176 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1177 Registers (ARRs) which provide a similar functionality to MTRRs. For
1178 these, the ARRs are used to emulate the MTRRs.
1179 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1180 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1181 write-combining. All of these processors are supported by this code
1182 and it makes sense to say Y here if you have one of them.
1183
1184 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1185 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1186 can lead to all sorts of problems, so it's good to say Y here.
1187
1188 You can safely say Y even if your machine doesn't have MTRRs, you'll
1189 just add about 9 KB to your kernel.
1190
7225e751 1191 See <file:Documentation/x86/mtrr.txt> for more information.
506f1d07 1192
95ffa243 1193config MTRR_SANITIZER
2ffb3501 1194 def_bool y
95ffa243
YL
1195 prompt "MTRR cleanup support"
1196 depends on MTRR
1197 help
aba3728c
TG
1198 Convert MTRR layout from continuous to discrete, so X drivers can
1199 add writeback entries.
95ffa243 1200
aba3728c
TG
1201 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1202 The largest mtrr entry size for a continous block can be set with
1203 mtrr_chunk_size.
95ffa243 1204
2ffb3501 1205 If unsure, say Y.
95ffa243
YL
1206
1207config MTRR_SANITIZER_ENABLE_DEFAULT
f5098d62
YL
1208 int "MTRR cleanup enable value (0-1)"
1209 range 0 1
1210 default "0"
95ffa243
YL
1211 depends on MTRR_SANITIZER
1212 help
f5098d62 1213 Enable mtrr cleanup default value
95ffa243 1214
12031a62
YL
1215config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1216 int "MTRR cleanup spare reg num (0-7)"
1217 range 0 7
1218 default "1"
1219 depends on MTRR_SANITIZER
1220 help
1221 mtrr cleanup spare entries default, it can be changed via
aba3728c 1222 mtrr_spare_reg_nr=N on the kernel command line.
12031a62 1223
2e5d9c85 1224config X86_PAT
2a8a2719 1225 bool
2e5d9c85 1226 prompt "x86 PAT support"
2a8a2719 1227 depends on MTRR
2e5d9c85 1228 help
1229 Use PAT attributes to setup page level cache control.
042b78e4 1230
2e5d9c85 1231 PATs are the modern equivalents of MTRRs and are much more
1232 flexible than MTRRs.
1233
1234 Say N here if you see bootup problems (boot crash, boot hang,
042b78e4 1235 spontaneous reboots) or a non-working video driver.
2e5d9c85 1236
1237 If unsure, say Y.
1238
506f1d07 1239config EFI
9ba16087 1240 bool "EFI runtime service support"
5b83683f 1241 depends on ACPI
506f1d07 1242 ---help---
8b2cb7a8 1243 This enables the kernel to use EFI runtime services that are
506f1d07
SR
1244 available (such as the EFI variable services).
1245
8b2cb7a8
HY
1246 This option is only useful on systems that have EFI firmware.
1247 In addition, you should use the latest ELILO loader available
1248 at <http://elilo.sourceforge.net> in order to take advantage
1249 of EFI runtime services. However, even with this option, the
1250 resultant kernel should continue to boot on existing non-EFI
1251 platforms.
506f1d07 1252
506f1d07 1253config SECCOMP
3c2362e6
HH
1254 def_bool y
1255 prompt "Enable seccomp to safely compute untrusted bytecode"
506f1d07
SR
1256 help
1257 This kernel feature is useful for number crunching applications
1258 that may need to compute untrusted bytecode during their
1259 execution. By using pipes or other transports made available to
1260 the process as file descriptors supporting the read/write
1261 syscalls, it's possible to isolate those applications in
1262 their own address space using seccomp. Once seccomp is
9c0bbee8 1263 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
506f1d07
SR
1264 and the task is only allowed to execute a few safe syscalls
1265 defined by each seccomp mode.
1266
1267 If unsure, say Y. Only embedded should say N here.
1268
1269config CC_STACKPROTECTOR
1270 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
2c020a99 1271 depends on X86_64 && EXPERIMENTAL && BROKEN
506f1d07
SR
1272 help
1273 This option turns on the -fstack-protector GCC feature. This
1274 feature puts, at the beginning of critical functions, a canary
1275 value on the stack just before the return address, and validates
1276 the value just before actually returning. Stack based buffer
1277 overflows (that need to overwrite this return address) now also
1278 overwrite the canary, which gets detected and the attack is then
1279 neutralized via a kernel panic.
1280
1281 This feature requires gcc version 4.2 or above, or a distribution
1282 gcc with the feature backported. Older versions are automatically
1283 detected and for those versions, this configuration option is ignored.
1284
1285config CC_STACKPROTECTOR_ALL
1286 bool "Use stack-protector for all functions"
1287 depends on CC_STACKPROTECTOR
1288 help
1289 Normally, GCC only inserts the canary value protection for
1290 functions that use large-ish on-stack buffers. By enabling
1291 this option, GCC will be asked to do this for ALL functions.
1292
1293source kernel/Kconfig.hz
1294
1295config KEXEC
1296 bool "kexec system call"
3e8f7e35 1297 depends on X86_BIOS_REBOOT
506f1d07
SR
1298 help
1299 kexec is a system call that implements the ability to shutdown your
1300 current kernel, and to start another kernel. It is like a reboot
1301 but it is independent of the system firmware. And like a reboot
1302 you can start any kernel with it, not just Linux.
1303
1304 The name comes from the similarity to the exec system call.
1305
1306 It is an ongoing process to be certain the hardware in a machine
1307 is properly shutdown, so do not be surprised if this code does not
1308 initially work for you. It may help to enable device hotplugging
1309 support. As of this writing the exact hardware interface is
1310 strongly in flux, so no good recommendation can be made.
1311
1312config CRASH_DUMP
04b69447 1313 bool "kernel crash dumps"
506f1d07
SR
1314 depends on X86_64 || (X86_32 && HIGHMEM)
1315 help
1316 Generate crash dump after being started by kexec.
1317 This should be normally only set in special crash dump kernels
1318 which are loaded in the main kernel with kexec-tools into
1319 a specially reserved region and then later executed after
1320 a crash by kdump/kexec. The crash dump kernel must be compiled
1321 to a memory address not used by the main kernel or BIOS using
1322 PHYSICAL_START, or it must be built as a relocatable image
1323 (CONFIG_RELOCATABLE=y).
1324 For more details see Documentation/kdump/kdump.txt
1325
3ab83521
HY
1326config KEXEC_JUMP
1327 bool "kexec jump (EXPERIMENTAL)"
1328 depends on EXPERIMENTAL
89081d17 1329 depends on KEXEC && HIBERNATION && X86_32
3ab83521 1330 help
89081d17
HY
1331 Jump between original kernel and kexeced kernel and invoke
1332 code in physical address mode via KEXEC
3ab83521 1333
506f1d07
SR
1334config PHYSICAL_START
1335 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1336 default "0x1000000" if X86_NUMAQ
1337 default "0x200000" if X86_64
1338 default "0x100000"
1339 help
1340 This gives the physical address where the kernel is loaded.
1341
1342 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1343 bzImage will decompress itself to above physical address and
1344 run from there. Otherwise, bzImage will run from the address where
1345 it has been loaded by the boot loader and will ignore above physical
1346 address.
1347
1348 In normal kdump cases one does not have to set/change this option
1349 as now bzImage can be compiled as a completely relocatable image
1350 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1351 address. This option is mainly useful for the folks who don't want
1352 to use a bzImage for capturing the crash dump and want to use a
1353 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1354 to be specifically compiled to run from a specific memory area
1355 (normally a reserved region) and this option comes handy.
1356
1357 So if you are using bzImage for capturing the crash dump, leave
1358 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1359 Otherwise if you plan to use vmlinux for capturing the crash dump
1360 change this value to start of the reserved region (Typically 16MB
1361 0x1000000). In other words, it can be set based on the "X" value as
1362 specified in the "crashkernel=YM@XM" command line boot parameter
1363 passed to the panic-ed kernel. Typically this parameter is set as
1364 crashkernel=64M@16M. Please take a look at
1365 Documentation/kdump/kdump.txt for more details about crash dumps.
1366
1367 Usage of bzImage for capturing the crash dump is recommended as
1368 one does not have to build two kernels. Same kernel can be used
1369 as production kernel and capture kernel. Above option should have
1370 gone away after relocatable bzImage support is introduced. But it
1371 is present because there are users out there who continue to use
1372 vmlinux for dump capture. This option should go away down the
1373 line.
1374
1375 Don't change this unless you know what you are doing.
1376
1377config RELOCATABLE
1378 bool "Build a relocatable kernel (EXPERIMENTAL)"
1379 depends on EXPERIMENTAL
1380 help
1381 This builds a kernel image that retains relocation information
1382 so it can be loaded someplace besides the default 1MB.
1383 The relocations tend to make the kernel binary about 10% larger,
1384 but are discarded at runtime.
1385
1386 One use is for the kexec on panic case where the recovery kernel
1387 must live at a different physical address than the primary
1388 kernel.
1389
1390 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1391 it has been loaded at and the compile time physical address
1392 (CONFIG_PHYSICAL_START) is ignored.
1393
1394config PHYSICAL_ALIGN
1395 hex
1396 prompt "Alignment value to which kernel should be aligned" if X86_32
1397 default "0x100000" if X86_32
1398 default "0x200000" if X86_64
1399 range 0x2000 0x400000
1400 help
1401 This value puts the alignment restrictions on physical address
1402 where kernel is loaded and run from. Kernel is compiled for an
1403 address which meets above alignment restriction.
1404
1405 If bootloader loads the kernel at a non-aligned address and
1406 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1407 address aligned to above value and run from there.
1408
1409 If bootloader loads the kernel at a non-aligned address and
1410 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1411 load address and decompress itself to the address it has been
1412 compiled for and run from there. The address for which kernel is
1413 compiled already meets above alignment restrictions. Hence the
1414 end result is that kernel runs from a physical address meeting
1415 above alignment restrictions.
1416
1417 Don't change this unless you know what you are doing.
1418
1419config HOTPLUG_CPU
7c13e6a3
DS
1420 bool "Support for hot-pluggable CPUs"
1421 depends on SMP && HOTPLUG && !X86_VOYAGER
506f1d07 1422 ---help---
7c13e6a3
DS
1423 Say Y here to allow turning CPUs off and on. CPUs can be
1424 controlled through /sys/devices/system/cpu.
1425 ( Note: power management support will enable this option
1426 automatically on SMP systems. )
1427 Say N if you want to disable CPU hotplug.
506f1d07
SR
1428
1429config COMPAT_VDSO
3c2362e6
HH
1430 def_bool y
1431 prompt "Compat VDSO support"
af65d648 1432 depends on X86_32 || IA32_EMULATION
506f1d07 1433 help
af65d648 1434 Map the 32-bit VDSO to the predictable old-style address too.
506f1d07
SR
1435 ---help---
1436 Say N here if you are running a sufficiently recent glibc
1437 version (2.3.3 or later), to remove the high-mapped
1438 VDSO mapping and to exclusively use the randomized VDSO.
1439
1440 If unsure, say Y.
1441
516cbf37
TB
1442config CMDLINE_BOOL
1443 bool "Built-in kernel command line"
1444 default n
1445 help
1446 Allow for specifying boot arguments to the kernel at
1447 build time. On some systems (e.g. embedded ones), it is
1448 necessary or convenient to provide some or all of the
1449 kernel boot arguments with the kernel itself (that is,
1450 to not rely on the boot loader to provide them.)
1451
1452 To compile command line arguments into the kernel,
1453 set this option to 'Y', then fill in the
1454 the boot arguments in CONFIG_CMDLINE.
1455
1456 Systems with fully functional boot loaders (i.e. non-embedded)
1457 should leave this option set to 'N'.
1458
1459config CMDLINE
1460 string "Built-in kernel command string"
1461 depends on CMDLINE_BOOL
1462 default ""
1463 help
1464 Enter arguments here that should be compiled into the kernel
1465 image and used at boot time. If the boot loader provides a
1466 command line at boot time, it is appended to this string to
1467 form the full kernel command line, when the system boots.
1468
1469 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1470 change this behavior.
1471
1472 In most cases, the command line (whether built-in or provided
1473 by the boot loader) should specify the device for the root
1474 file system.
1475
1476config CMDLINE_OVERRIDE
1477 bool "Built-in command line overrides boot loader arguments"
1478 default n
1479 depends on CMDLINE_BOOL
1480 help
1481 Set this option to 'Y' to have the kernel ignore the boot loader
1482 command line, and use ONLY the built-in command line.
1483
1484 This is used to work around broken boot loaders. This should
1485 be set to 'N' under normal conditions.
1486
506f1d07
SR
1487endmenu
1488
1489config ARCH_ENABLE_MEMORY_HOTPLUG
1490 def_bool y
1491 depends on X86_64 || (X86_32 && HIGHMEM)
1492
506f1d07
SR
1493config HAVE_ARCH_EARLY_PFN_TO_NID
1494 def_bool X86_64
1495 depends on NUMA
1496
da85f865 1497menu "Power management and ACPI options"
e279b6c1
SR
1498 depends on !X86_VOYAGER
1499
1500config ARCH_HIBERNATION_HEADER
3c2362e6 1501 def_bool y
e279b6c1 1502 depends on X86_64 && HIBERNATION
e279b6c1
SR
1503
1504source "kernel/power/Kconfig"
1505
1506source "drivers/acpi/Kconfig"
1507
a6b68076
AK
1508config X86_APM_BOOT
1509 bool
1510 default y
1511 depends on APM || APM_MODULE
1512
e279b6c1
SR
1513menuconfig APM
1514 tristate "APM (Advanced Power Management) BIOS support"
efefa6f6 1515 depends on X86_32 && PM_SLEEP
e279b6c1
SR
1516 ---help---
1517 APM is a BIOS specification for saving power using several different
1518 techniques. This is mostly useful for battery powered laptops with
1519 APM compliant BIOSes. If you say Y here, the system time will be
1520 reset after a RESUME operation, the /proc/apm device will provide
1521 battery status information, and user-space programs will receive
1522 notification of APM "events" (e.g. battery status change).
1523
1524 If you select "Y" here, you can disable actual use of the APM
1525 BIOS by passing the "apm=off" option to the kernel at boot time.
1526
1527 Note that the APM support is almost completely disabled for
1528 machines with more than one CPU.
1529
1530 In order to use APM, you will need supporting software. For location
53471121 1531 and more information, read <file:Documentation/power/pm.txt> and the
e279b6c1
SR
1532 Battery Powered Linux mini-HOWTO, available from
1533 <http://www.tldp.org/docs.html#howto>.
1534
1535 This driver does not spin down disk drives (see the hdparm(8)
1536 manpage ("man 8 hdparm") for that), and it doesn't turn off
1537 VESA-compliant "green" monitors.
1538
1539 This driver does not support the TI 4000M TravelMate and the ACER
1540 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1541 desktop machines also don't have compliant BIOSes, and this driver
1542 may cause those machines to panic during the boot phase.
1543
1544 Generally, if you don't have a battery in your machine, there isn't
1545 much point in using this driver and you should say N. If you get
1546 random kernel OOPSes or reboots that don't seem to be related to
1547 anything, try disabling/enabling this option (or disabling/enabling
1548 APM in your BIOS).
1549
1550 Some other things you should try when experiencing seemingly random,
1551 "weird" problems:
1552
1553 1) make sure that you have enough swap space and that it is
1554 enabled.
1555 2) pass the "no-hlt" option to the kernel
1556 3) switch on floating point emulation in the kernel and pass
1557 the "no387" option to the kernel
1558 4) pass the "floppy=nodma" option to the kernel
1559 5) pass the "mem=4M" option to the kernel (thereby disabling
1560 all but the first 4 MB of RAM)
1561 6) make sure that the CPU is not over clocked.
1562 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1563 8) disable the cache from your BIOS settings
1564 9) install a fan for the video card or exchange video RAM
1565 10) install a better fan for the CPU
1566 11) exchange RAM chips
1567 12) exchange the motherboard.
1568
1569 To compile this driver as a module, choose M here: the
1570 module will be called apm.
1571
1572if APM
1573
1574config APM_IGNORE_USER_SUSPEND
1575 bool "Ignore USER SUSPEND"
1576 help
1577 This option will ignore USER SUSPEND requests. On machines with a
1578 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1579 series notebooks, it is necessary to say Y because of a BIOS bug.
1580
1581config APM_DO_ENABLE
1582 bool "Enable PM at boot time"
1583 ---help---
1584 Enable APM features at boot time. From page 36 of the APM BIOS
1585 specification: "When disabled, the APM BIOS does not automatically
1586 power manage devices, enter the Standby State, enter the Suspend
1587 State, or take power saving steps in response to CPU Idle calls."
1588 This driver will make CPU Idle calls when Linux is idle (unless this
1589 feature is turned off -- see "Do CPU IDLE calls", below). This
1590 should always save battery power, but more complicated APM features
1591 will be dependent on your BIOS implementation. You may need to turn
1592 this option off if your computer hangs at boot time when using APM
1593 support, or if it beeps continuously instead of suspending. Turn
1594 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1595 T400CDT. This is off by default since most machines do fine without
1596 this feature.
1597
1598config APM_CPU_IDLE
1599 bool "Make CPU Idle calls when idle"
1600 help
1601 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1602 On some machines, this can activate improved power savings, such as
1603 a slowed CPU clock rate, when the machine is idle. These idle calls
1604 are made after the idle loop has run for some length of time (e.g.,
1605 333 mS). On some machines, this will cause a hang at boot time or
1606 whenever the CPU becomes idle. (On machines with more than one CPU,
1607 this option does nothing.)
1608
1609config APM_DISPLAY_BLANK
1610 bool "Enable console blanking using APM"
1611 help
1612 Enable console blanking using the APM. Some laptops can use this to
1613 turn off the LCD backlight when the screen blanker of the Linux
1614 virtual console blanks the screen. Note that this is only used by
1615 the virtual console screen blanker, and won't turn off the backlight
1616 when using the X Window system. This also doesn't have anything to
1617 do with your VESA-compliant power-saving monitor. Further, this
1618 option doesn't work for all laptops -- it might not turn off your
1619 backlight at all, or it might print a lot of errors to the console,
1620 especially if you are using gpm.
1621
1622config APM_ALLOW_INTS
1623 bool "Allow interrupts during APM BIOS calls"
1624 help
1625 Normally we disable external interrupts while we are making calls to
1626 the APM BIOS as a measure to lessen the effects of a badly behaving
1627 BIOS implementation. The BIOS should reenable interrupts if it
1628 needs to. Unfortunately, some BIOSes do not -- especially those in
1629 many of the newer IBM Thinkpads. If you experience hangs when you
1630 suspend, try setting this to Y. Otherwise, say N.
1631
1632config APM_REAL_MODE_POWER_OFF
1633 bool "Use real mode APM BIOS call to power off"
1634 help
1635 Use real mode APM BIOS calls to switch off the computer. This is
1636 a work-around for a number of buggy BIOSes. Switch this option on if
1637 your computer crashes instead of powering off properly.
1638
1639endif # APM
1640
1641source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1642
1643source "drivers/cpuidle/Kconfig"
1644
27471fdb
AH
1645source "drivers/idle/Kconfig"
1646
e279b6c1
SR
1647endmenu
1648
1649
1650menu "Bus options (PCI etc.)"
1651
1652config PCI
1ac97018 1653 bool "PCI support"
1c858087 1654 default y
e279b6c1
SR
1655 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1656 help
1657 Find out whether you have a PCI motherboard. PCI is the name of a
1658 bus system, i.e. the way the CPU talks to the other stuff inside
1659 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1660 VESA. If you have PCI, say Y, otherwise N.
1661
e279b6c1
SR
1662choice
1663 prompt "PCI access mode"
efefa6f6 1664 depends on X86_32 && PCI
e279b6c1
SR
1665 default PCI_GOANY
1666 ---help---
1667 On PCI systems, the BIOS can be used to detect the PCI devices and
1668 determine their configuration. However, some old PCI motherboards
1669 have BIOS bugs and may crash if this is done. Also, some embedded
1670 PCI-based systems don't have any BIOS at all. Linux can also try to
1671 detect the PCI hardware directly without using the BIOS.
1672
1673 With this option, you can specify how Linux should detect the
1674 PCI devices. If you choose "BIOS", the BIOS will be used,
1675 if you choose "Direct", the BIOS won't be used, and if you
1676 choose "MMConfig", then PCI Express MMCONFIG will be used.
1677 If you choose "Any", the kernel will try MMCONFIG, then the
1678 direct access method and falls back to the BIOS if that doesn't
1679 work. If unsure, go with the default, which is "Any".
1680
1681config PCI_GOBIOS
1682 bool "BIOS"
1683
1684config PCI_GOMMCONFIG
1685 bool "MMConfig"
1686
1687config PCI_GODIRECT
1688 bool "Direct"
1689
3ef0e1f8
AS
1690config PCI_GOOLPC
1691 bool "OLPC"
1692 depends on OLPC
1693
2bdd1b03
AS
1694config PCI_GOANY
1695 bool "Any"
1696
e279b6c1
SR
1697endchoice
1698
1699config PCI_BIOS
3c2362e6 1700 def_bool y
efefa6f6 1701 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
e279b6c1
SR
1702
1703# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1704config PCI_DIRECT
3c2362e6 1705 def_bool y
efefa6f6 1706 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
e279b6c1
SR
1707
1708config PCI_MMCONFIG
3c2362e6 1709 def_bool y
e279b6c1 1710 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
e279b6c1 1711
3ef0e1f8 1712config PCI_OLPC
2bdd1b03
AS
1713 def_bool y
1714 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
3ef0e1f8 1715
e279b6c1 1716config PCI_DOMAINS
3c2362e6 1717 def_bool y
e279b6c1 1718 depends on PCI
e279b6c1
SR
1719
1720config PCI_MMCONFIG
1721 bool "Support mmconfig PCI config space access"
1722 depends on X86_64 && PCI && ACPI
1723
1724config DMAR
1725 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1726 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1727 help
1728 DMA remapping (DMAR) devices support enables independent address
1729 translations for Direct Memory Access (DMA) from devices.
1730 These DMA remapping devices are reported via ACPI tables
1731 and include PCI device scope covered by these DMA
1732 remapping devices.
1733
1734config DMAR_GFX_WA
3c2362e6
HH
1735 def_bool y
1736 prompt "Support for Graphics workaround"
e279b6c1 1737 depends on DMAR
e279b6c1
SR
1738 help
1739 Current Graphics drivers tend to use physical address
1740 for DMA and avoid using DMA APIs. Setting this config
1741 option permits the IOMMU driver to set a unity map for
1742 all the OS-visible memory. Hence the driver can continue
1743 to use physical addresses for DMA.
1744
1745config DMAR_FLOPPY_WA
3c2362e6 1746 def_bool y
e279b6c1 1747 depends on DMAR
e279b6c1
SR
1748 help
1749 Floppy disk drivers are know to bypass DMA API calls
1750 thereby failing to work when IOMMU is enabled. This
1751 workaround will setup a 1:1 mapping for the first
1752 16M to make floppy (an ISA device) work.
1753
9fa8c481
SS
1754config INTR_REMAP
1755 bool "Support for Interrupt Remapping (EXPERIMENTAL)"
1756 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
1757 help
1758 Supports Interrupt remapping for IO-APIC and MSI devices.
1759 To use x2apic mode in the CPU's which support x2APIC enhancements or
1760 to support platforms with CPU's having > 8 bit APIC ID, say Y.
1761
e279b6c1
SR
1762source "drivers/pci/pcie/Kconfig"
1763
1764source "drivers/pci/Kconfig"
1765
1766# x86_64 have no ISA slots, but do have ISA-style DMA.
1767config ISA_DMA_API
3c2362e6 1768 def_bool y
e279b6c1
SR
1769
1770if X86_32
1771
1772config ISA
1773 bool "ISA support"
efefa6f6 1774 depends on !X86_VOYAGER
e279b6c1
SR
1775 help
1776 Find out whether you have ISA slots on your motherboard. ISA is the
1777 name of a bus system, i.e. the way the CPU talks to the other stuff
1778 inside your box. Other bus systems are PCI, EISA, MicroChannel
1779 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1780 newer boards don't support it. If you have ISA, say Y, otherwise N.
1781
1782config EISA
1783 bool "EISA support"
1784 depends on ISA
1785 ---help---
1786 The Extended Industry Standard Architecture (EISA) bus was
1787 developed as an open alternative to the IBM MicroChannel bus.
1788
1789 The EISA bus provided some of the features of the IBM MicroChannel
1790 bus while maintaining backward compatibility with cards made for
1791 the older ISA bus. The EISA bus saw limited use between 1988 and
1792 1995 when it was made obsolete by the PCI bus.
1793
1794 Say Y here if you are building a kernel for an EISA-based machine.
1795
1796 Otherwise, say N.
1797
1798source "drivers/eisa/Kconfig"
1799
1800config MCA
efefa6f6 1801 bool "MCA support" if !X86_VOYAGER
e279b6c1
SR
1802 default y if X86_VOYAGER
1803 help
1804 MicroChannel Architecture is found in some IBM PS/2 machines and
1805 laptops. It is a bus system similar to PCI or ISA. See
1806 <file:Documentation/mca.txt> (and especially the web page given
1807 there) before attempting to build an MCA bus kernel.
1808
1809source "drivers/mca/Kconfig"
1810
1811config SCx200
1812 tristate "NatSemi SCx200 support"
1813 depends on !X86_VOYAGER
1814 help
1815 This provides basic support for National Semiconductor's
1816 (now AMD's) Geode processors. The driver probes for the
1817 PCI-IDs of several on-chip devices, so its a good dependency
1818 for other scx200_* drivers.
1819
1820 If compiled as a module, the driver is named scx200.
1821
1822config SCx200HR_TIMER
1823 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1824 depends on SCx200 && GENERIC_TIME
1825 default y
1826 help
1827 This driver provides a clocksource built upon the on-chip
1828 27MHz high-resolution timer. Its also a workaround for
1829 NSC Geode SC-1100's buggy TSC, which loses time when the
1830 processor goes idle (as is done by the scheduler). The
1831 other workaround is idle=poll boot option.
1832
1833config GEODE_MFGPT_TIMER
3c2362e6
HH
1834 def_bool y
1835 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
e279b6c1 1836 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
e279b6c1
SR
1837 help
1838 This driver provides a clock event source based on the MFGPT
1839 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1840 MFGPTs have a better resolution and max interval than the
1841 generic PIT, and are suitable for use as high-res timers.
1842
3ef0e1f8
AS
1843config OLPC
1844 bool "One Laptop Per Child support"
1845 default n
1846 help
1847 Add support for detecting the unique features of the OLPC
1848 XO hardware.
1849
bc0120fd
SR
1850endif # X86_32
1851
e279b6c1
SR
1852config K8_NB
1853 def_bool y
bc0120fd 1854 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
e279b6c1
SR
1855
1856source "drivers/pcmcia/Kconfig"
1857
1858source "drivers/pci/hotplug/Kconfig"
1859
1860endmenu
1861
1862
1863menu "Executable file formats / Emulations"
1864
1865source "fs/Kconfig.binfmt"
1866
1867config IA32_EMULATION
1868 bool "IA32 Emulation"
1869 depends on X86_64
a97f52e6 1870 select COMPAT_BINFMT_ELF
e279b6c1
SR
1871 help
1872 Include code to run 32-bit programs under a 64-bit kernel. You should
1873 likely turn this on, unless you're 100% sure that you don't have any
1874 32-bit programs left.
1875
1876config IA32_AOUT
1877 tristate "IA32 a.out support"
6b213e1b 1878 depends on IA32_EMULATION
e279b6c1
SR
1879 help
1880 Support old a.out binaries in the 32bit emulation.
1881
1882config COMPAT
3c2362e6 1883 def_bool y
e279b6c1 1884 depends on IA32_EMULATION
e279b6c1
SR
1885
1886config COMPAT_FOR_U64_ALIGNMENT
1887 def_bool COMPAT
1888 depends on X86_64
1889
1890config SYSVIPC_COMPAT
3c2362e6 1891 def_bool y
b8992195 1892 depends on COMPAT && SYSVIPC
e279b6c1
SR
1893
1894endmenu
1895
1896
e5beae16
KP
1897config HAVE_ATOMIC_IOMAP
1898 def_bool y
1899 depends on X86_32
1900
e279b6c1
SR
1901source "net/Kconfig"
1902
1903source "drivers/Kconfig"
1904
1905source "drivers/firmware/Kconfig"
1906
1907source "fs/Kconfig"
1908
e279b6c1
SR
1909source "arch/x86/Kconfig.debug"
1910
1911source "security/Kconfig"
1912
1913source "crypto/Kconfig"
1914
edf88417
AK
1915source "arch/x86/kvm/Kconfig"
1916
e279b6c1 1917source "lib/Kconfig"