Kconfig 69.1 KB
Newer Older
S
Sam Ravnborg 已提交
1 2
# Select 32 or 64 bit
config 64BIT
3 4
	bool "64-bit kernel" if ARCH = "x86"
	default ARCH = "x86_64"
I
Ingo Molnar 已提交
5
	---help---
S
Sam Ravnborg 已提交
6 7 8 9 10
	  Say yes to build a 64-bit kernel - formerly known as x86_64
	  Say no to build a 32-bit kernel - formerly known as i386

config X86_32
	def_bool !64BIT
11
	select CLKSRC_I8253
S
Sam Ravnborg 已提交
12 13 14

config X86_64
	def_bool 64BIT
15 16

### Arch settings
17
config X86
18
	def_bool y
19
	select HAVE_AOUT if X86_32
20
	select HAVE_UNSTABLE_SCHED_CLOCK
S
Sam Ravnborg 已提交
21
	select HAVE_IDE
M
Mathieu Desnoyers 已提交
22
	select HAVE_OPROFILE
P
Peter Zijlstra 已提交
23
	select HAVE_PERF_EVENTS
24
	select HAVE_IRQ_WORK
25
	select HAVE_IOREMAP_PROT
M
Mathieu Desnoyers 已提交
26
	select HAVE_KPROBES
27
	select HAVE_MEMBLOCK
I
Ingo Molnar 已提交
28
	select ARCH_WANT_OPTIONAL_GPIOLIB
29
	select ARCH_WANT_FRAME_POINTERS
30
	select HAVE_DMA_ATTRS
31
	select HAVE_KRETPROBES
32
	select HAVE_OPTPROBES
33
	select HAVE_FTRACE_MCOUNT_RECORD
34
	select HAVE_C_RECORDMCOUNT
35
	select HAVE_DYNAMIC_FTRACE
36
	select HAVE_FUNCTION_TRACER
37
	select HAVE_FUNCTION_GRAPH_TRACER
38
	select HAVE_FUNCTION_GRAPH_FP_TEST
39
	select HAVE_FUNCTION_TRACE_MCOUNT_TEST
40
	select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE
41
	select HAVE_SYSCALL_TRACEPOINTS
42
	select HAVE_KVM
43
	select HAVE_ARCH_KGDB
44
	select HAVE_ARCH_TRACEHOOK
45
	select HAVE_GENERIC_DMA_COHERENT if X86_32
46
	select HAVE_EFFICIENT_UNALIGNED_ACCESS
47
	select USER_STACKTRACE_SUPPORT
48
	select HAVE_REGS_AND_STACK_ACCESS_API
49
	select HAVE_DMA_API_DEBUG
50 51 52
	select HAVE_KERNEL_GZIP
	select HAVE_KERNEL_BZIP2
	select HAVE_KERNEL_LZMA
L
Lasse Collin 已提交
53
	select HAVE_KERNEL_XZ
54
	select HAVE_KERNEL_LZO
55
	select HAVE_HW_BREAKPOINT
56
	select HAVE_MIXED_BREAKPOINTS_REGS
57
	select PERF_EVENTS
58
	select HAVE_PERF_EVENTS_NMI
59
	select ANON_INODES
60
	select HAVE_ARCH_KMEMCHECK
A
Avi Kivity 已提交
61
	select HAVE_USER_RETURN_NOTIFIER
62
	select HAVE_ARCH_JUMP_LABEL
63
	select HAVE_TEXT_POKE_SMP
T
Thomas Gleixner 已提交
64 65
	select HAVE_GENERIC_HARDIRQS
	select HAVE_SPARSE_IRQ
66
	select GENERIC_FIND_FIRST_BIT
T
Thomas Gleixner 已提交
67 68
	select GENERIC_IRQ_PROBE
	select GENERIC_PENDING_IRQ if SMP
69
	select GENERIC_IRQ_SHOW
70
	select IRQ_FORCED_THREADING
71
	select USE_GENERIC_SMP_HELPERS if SMP
72
	select HAVE_BPF_JIT if (X86_64 && NET)
73

74 75 76
config INSTRUCTION_DECODER
	def_bool (KPROBES || PERF_EVENTS)

77 78 79 80 81
config OUTPUT_FORMAT
	string
	default "elf32-i386" if X86_32
	default "elf64-x86-64" if X86_64

82
config ARCH_DEFCONFIG
83
	string
84 85
	default "arch/x86/configs/i386_defconfig" if X86_32
	default "arch/x86/configs/x86_64_defconfig" if X86_64
86

87
config GENERIC_CMOS_UPDATE
88
	def_bool y
89 90

config CLOCKSOURCE_WATCHDOG
91
	def_bool y
92 93

config GENERIC_CLOCKEVENTS
94
	def_bool y
95 96

config GENERIC_CLOCKEVENTS_BROADCAST
97
	def_bool y
98 99 100
	depends on X86_64 || (X86_32 && X86_LOCAL_APIC)

config LOCKDEP_SUPPORT
101
	def_bool y
102 103

config STACKTRACE_SUPPORT
104
	def_bool y
105

106 107 108
config HAVE_LATENCYTOP_SUPPORT
	def_bool y

109
config MMU
110
	def_bool y
111 112

config ZONE_DMA
113 114 115 116 117 118 119 120
	bool "DMA memory allocation support" if EXPERT
	default y
	help
	  DMA memory allocation support allows devices with less than 32-bit
	  addressing to allocate within the first 16MB of address space.
	  Disable if no such devices will be used.

	  If unsure, say Y.
121 122 123 124

config SBUS
	bool

125 126 127
config NEED_DMA_MAP_STATE
       def_bool (X86_64 || DMAR || DMA_API_DEBUG)

128
config NEED_SG_DMA_LENGTH
129
	def_bool y
130

131
config GENERIC_ISA_DMA
132
	def_bool ISA_DMA_API
133 134

config GENERIC_IOMAP
135
	def_bool y
136 137

config GENERIC_BUG
138
	def_bool y
139
	depends on BUG
140 141 142 143
	select GENERIC_BUG_RELATIVE_POINTERS if X86_64

config GENERIC_BUG_RELATIVE_POINTERS
	bool
144 145

config GENERIC_HWEIGHT
146
	def_bool y
147

148
config GENERIC_GPIO
149
	bool
150

151
config ARCH_MAY_HAVE_PC_FDC
152
	def_bool ISA_DMA_API
153

154 155 156 157 158 159
config RWSEM_GENERIC_SPINLOCK
	def_bool !X86_XADD

config RWSEM_XCHGADD_ALGORITHM
	def_bool X86_XADD

V
Venki Pallipadi 已提交
160 161 162
config ARCH_HAS_CPU_IDLE_WAIT
	def_bool y

163 164 165
config GENERIC_CALIBRATE_DELAY
	def_bool y

166 167 168 169
config GENERIC_TIME_VSYSCALL
	bool
	default X86_64

170 171 172
config ARCH_HAS_CPU_RELAX
	def_bool y

173 174 175
config ARCH_HAS_DEFAULT_IDLE
	def_bool y

176 177 178
config ARCH_HAS_CACHE_LINE_SIZE
	def_bool y

179
config HAVE_SETUP_PER_CPU_AREA
180
	def_bool y
181

182 183 184 185
config NEED_PER_CPU_EMBED_FIRST_CHUNK
	def_bool y

config NEED_PER_CPU_PAGE_FIRST_CHUNK
186 187
	def_bool y

188 189 190
config HAVE_CPUMASK_OF_CPU_MAP
	def_bool X86_64_SMP

191 192 193
config ARCH_HIBERNATION_POSSIBLE
	def_bool y

J
Johannes Berg 已提交
194 195 196
config ARCH_SUSPEND_POSSIBLE
	def_bool y

197 198 199 200 201 202 203 204 205 206 207
config ZONE_DMA32
	bool
	default X86_64

config ARCH_POPULATES_NODE_MAP
	def_bool y

config AUDIT_ARCH
	bool
	default X86_64

208 209 210
config ARCH_SUPPORTS_OPTIMIZED_INLINING
	def_bool y

A
Akinobu Mita 已提交
211 212 213
config ARCH_SUPPORTS_DEBUG_PAGEALLOC
	def_bool y

214 215 216 217
config HAVE_INTEL_TXT
	def_bool y
	depends on EXPERIMENTAL && DMAR && ACPI

218 219 220 221 222 223 224 225
config X86_32_SMP
	def_bool y
	depends on X86_32 && SMP

config X86_64_SMP
	def_bool y
	depends on X86_64 && SMP

226
config X86_HT
J
Jan Beulich 已提交
227
	def_bool y
228
	depends on SMP
229

230 231
config X86_32_LAZY_GS
	def_bool y
232
	depends on X86_32 && !CC_STACKPROTECTOR
233

234 235 236 237 238
config ARCH_HWEIGHT_CFLAGS
	string
	default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
	default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64

239 240
config KTIME_SCALAR
	def_bool X86_32
241 242 243 244 245

config ARCH_CPU_PROBE_RELEASE
	def_bool y
	depends on HOTPLUG_CPU

246
source "init/Kconfig"
247
source "kernel/Kconfig.freezer"
248

249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274
menu "Processor type and features"

source "kernel/time/Kconfig"

config SMP
	bool "Symmetric multi-processing support"
	---help---
	  This enables support for systems with more than one CPU. If you have
	  a system with only one CPU, like most personal computers, say N. If
	  you have a system with more than one CPU, say Y.

	  If you say N here, the kernel will run on single and multiprocessor
	  machines, but will use only one CPU of a multiprocessor machine. If
	  you say Y here, the kernel will run on many, but not all,
	  singleprocessor machines. On a singleprocessor machine, the kernel
	  will run faster if you say N here.

	  Note that if you say Y here and choose architecture "586" or
	  "Pentium" under "Processor family", the kernel will not work on 486
	  architectures. Similarly, multiprocessor kernels for the "PPro"
	  architecture may not work on all Pentium based boards.

	  People using multiprocessor machines who say Y here should also say
	  Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
	  Management" code will be disabled if you say Y here.

A
Adrian Bunk 已提交
275
	  See also <file:Documentation/i386/IO-APIC.txt>,
276 277 278 279 280
	  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
	  <http://www.tldp.org/docs.html#howto>.

	  If you don't know what to do here, say N.

Y
Yinghai Lu 已提交
281 282
config X86_X2APIC
	bool "Support x2apic"
283
	depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
Y
Yinghai Lu 已提交
284 285 286 287 288 289 290 291
	---help---
	  This enables x2apic support on CPUs that have this feature.

	  This allows 32-bit apic IDs (so it can support very large systems),
	  and accesses the local apic via MSRs not via mmio.

	  If you don't know what to do here, say N.

292
config X86_MPPARSE
293 294
	bool "Enable MPS table" if ACPI
	default y
295
	depends on X86_LOCAL_APIC
I
Ingo Molnar 已提交
296
	---help---
297 298 299
	  For old smp systems that do not have proper acpi support. Newer systems
	  (esp with 64bit cpus) with acpi support, MADT and DSDT will override it

300 301 302
config X86_BIGSMP
	bool "Support for big SMP systems with more than 8 CPUs"
	depends on X86_32 && SMP
I
Ingo Molnar 已提交
303
	---help---
304
	  This option is needed for the systems that have more than 8 CPUs
305

306
if X86_32
307 308 309
config X86_EXTENDED_PLATFORM
	bool "Support for extended (non-PC) x86 platforms"
	default y
I
Ingo Molnar 已提交
310
	---help---
311 312 313 314
	  If you disable this option then the kernel will only support
	  standard PC platforms. (which covers the vast majority of
	  systems out there.)

315 316 317 318 319 320 321 322
	  If you enable this option then you'll be able to select support
	  for the following (non-PC) 32 bit x86 platforms:
		AMD Elan
		NUMAQ (IBM/Sequent)
		RDC R-321x SoC
		SGI 320/540 (Visual Workstation)
		Summit/EXA (IBM x440)
		Unisys ES7000 IA32 series
323
		Moorestown MID devices
324 325 326

	  If you have one of these systems, or if you want to build a
	  generic distribution kernel, say Y here - otherwise say N.
327
endif
328

329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345
if X86_64
config X86_EXTENDED_PLATFORM
	bool "Support for extended (non-PC) x86 platforms"
	default y
	---help---
	  If you disable this option then the kernel will only support
	  standard PC platforms. (which covers the vast majority of
	  systems out there.)

	  If you enable this option then you'll be able to select support
	  for the following (non-PC) 64 bit x86 platforms:
		ScaleMP vSMP
		SGI Ultraviolet

	  If you have one of these systems, or if you want to build a
	  generic distribution kernel, say Y here - otherwise say N.
endif
346 347
# This is an alphabetically sorted list of 64 bit extended platforms
# Please maintain the alphabetic order if and when there are additions
348

349 350
config X86_VSMP
	bool "ScaleMP vSMP"
351
	select PARAVIRT_GUEST
352 353 354
	select PARAVIRT
	depends on X86_64 && PCI
	depends on X86_EXTENDED_PLATFORM
I
Ingo Molnar 已提交
355
	---help---
356 357 358
	  Support for ScaleMP vSMP systems.  Say 'Y' here if this kernel is
	  supposed to run on these EM64T-based machines.  Only choose this option
	  if you have one of these machines.
359

N
Nick Piggin 已提交
360 361 362
config X86_UV
	bool "SGI Ultraviolet"
	depends on X86_64
363
	depends on X86_EXTENDED_PLATFORM
364
	depends on NUMA
365
	depends on X86_X2APIC
I
Ingo Molnar 已提交
366
	---help---
N
Nick Piggin 已提交
367 368 369
	  This option is needed in order to support SGI Ultraviolet systems.
	  If you don't have one of these, you should say N here.

370 371
# Following is an alphabetically sorted list of 32 bit extended platforms
# Please maintain the alphabetic order if and when there are additions
372

T
Thomas Gleixner 已提交
373 374 375 376 377 378
config X86_INTEL_CE
	bool "CE4100 TV platform"
	depends on PCI
	depends on PCI_GODIRECT
	depends on X86_32
	depends on X86_EXTENDED_PLATFORM
379
	select X86_REBOOTFIXUPS
380 381
	select OF
	select OF_EARLY_FLATTREE
T
Thomas Gleixner 已提交
382 383 384 385 386
	---help---
	  Select for the Intel CE media processor (CE4100) SOC.
	  This option compiles in support for the CE4100 SOC for settop
	  boxes and media devices.

387 388
config X86_MRST
       bool "Moorestown MID platform"
389 390
	depends on PCI
	depends on PCI_GOANY
391 392
	depends on X86_32
	depends on X86_EXTENDED_PLATFORM
393
	depends on X86_IO_APIC
394
	select APB_TIMER
395 396
	select I2C
	select SPI
397
	select INTEL_SCU_IPC
398
	select X86_PLATFORM_DEVICES
399 400 401 402 403 404 405 406
	---help---
	  Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin
	  Internet Device(MID) platform. Moorestown consists of two chips:
	  Lincroft (CPU core, graphics, and memory controller) and Langwell IOH.
	  Unlike standard x86 PCs, Moorestown does not have many legacy devices
	  nor standard legacy replacement devices/features. e.g. Moorestown does
	  not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.

407 408
config X86_RDC321X
	bool "RDC R-321x SoC"
409
	depends on X86_32
410 411 412 413 414 415 416 417
	depends on X86_EXTENDED_PLATFORM
	select M486
	select X86_REBOOTFIXUPS
	---help---
	  This option is needed for RDC R-321x system-on-chip, also known
	  as R-8610-(G).
	  If you don't have one of these chips, you should say N here.

418
config X86_32_NON_STANDARD
419 420
	bool "Support non-standard 32-bit SMP architectures"
	depends on X86_32 && SMP
421
	depends on X86_EXTENDED_PLATFORM
I
Ingo Molnar 已提交
422 423
	---help---
	  This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
424 425 426 427
	  subarchitectures.  It is intended for a generic binary kernel.
	  if you select them all, kernel will probe it one by one. and will
	  fallback to default.

428
# Alphabetically sorted list of Non standard 32 bit platforms
429

430 431
config X86_NUMAQ
	bool "NUMAQ (IBM/Sequent)"
432
	depends on X86_32_NON_STANDARD
433
	depends on PCI
434
	select NUMA
435
	select X86_MPPARSE
I
Ingo Molnar 已提交
436
	---help---
437 438 439 440 441
	  This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
	  NUMA multiquad box. This changes the way that processors are
	  bootstrapped, and uses Clustered Logical APIC addressing mode instead
	  of Flat Logical.  You will need a new lynxer.elf file to flash your
	  firmware with - send email to <Martin.Bligh@us.ibm.com>.
442

443
config X86_SUPPORTS_MEMORY_FAILURE
J
Jan Beulich 已提交
444
	def_bool y
445 446 447 448 449 450 451 452
	# MCE code calls memory_failure():
	depends on X86_MCE
	# On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
	depends on !X86_NUMAQ
	# On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
	depends on X86_64 || !SPARSEMEM
	select ARCH_SUPPORTS_MEMORY_FAILURE

453 454
config X86_VISWS
	bool "SGI 320/540 (Visual Workstation)"
455 456 457
	depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
	depends on X86_32_NON_STANDARD
	---help---
458 459 460 461 462 463 464 465
	  The SGI Visual Workstation series is an IA32-based workstation
	  based on SGI systems chips with some legacy PC hardware attached.

	  Say Y here to create a kernel to run on the SGI 320 or 540.

	  A kernel compiled for the Visual Workstation will run on general
	  PCs as well. See <file:Documentation/sgi-visws.txt> for details.

466 467
config X86_SUMMIT
	bool "Summit/EXA (IBM x440)"
468
	depends on X86_32_NON_STANDARD
I
Ingo Molnar 已提交
469
	---help---
470 471
	  This option is needed for IBM systems that use the Summit/EXA chipset.
	  In particular, it is needed for the x440.
I
Ingo Molnar 已提交
472

473
config X86_ES7000
474
	bool "Unisys ES7000 IA32 series"
475
	depends on X86_32_NON_STANDARD && X86_BIGSMP
I
Ingo Molnar 已提交
476
	---help---
477 478 479
	  Support for Unisys ES7000 systems.  Say 'Y' here if this kernel is
	  supposed to run on an IA32-based Unisys ES7000 system.

480 481 482 483 484 485 486 487 488 489 490 491 492
config X86_32_IRIS
	tristate "Eurobraille/Iris poweroff module"
	depends on X86_32
	---help---
	  The Iris machines from EuroBraille do not have APM or ACPI support
	  to shut themselves down properly.  A special I/O sequence is
	  needed to do so, which is what this module does at
	  kernel shutdown.

	  This is only for Iris machines from EuroBraille.

	  If unused, say N.

493
config SCHED_OMIT_FRAME_POINTER
494 495
	def_bool y
	prompt "Single-depth WCHAN output"
496
	depends on X86
I
Ingo Molnar 已提交
497
	---help---
498 499 500 501 502 503 504 505 506
	  Calculate simpler /proc/<PID>/wchan values. If this option
	  is disabled then wchan values will recurse back to the
	  caller function. This provides more accurate wchan values,
	  at the expense of slightly more scheduling overhead.

	  If in doubt, say "Y".

menuconfig PARAVIRT_GUEST
	bool "Paravirtualized guest support"
I
Ingo Molnar 已提交
507
	---help---
508 509 510 511 512 513 514 515 516
	  Say Y here to get to see options related to running Linux under
	  various hypervisors.  This option alone does not add any kernel code.

	  If you say N, all options in this submenu will be skipped and disabled.

if PARAVIRT_GUEST

source "arch/x86/xen/Kconfig"

517 518 519
config KVM_CLOCK
	bool "KVM paravirtualized clock"
	select PARAVIRT
520
	select PARAVIRT_CLOCK
I
Ingo Molnar 已提交
521
	---help---
522 523 524 525 526 527
	  Turning on this option will allow you to run a paravirtualized clock
	  when running over the KVM hypervisor. Instead of relying on a PIT
	  (or probably other) emulation by the underlying device model, the host
	  provides the guest with timing infrastructure such as time of day, and
	  system time

528 529 530
config KVM_GUEST
	bool "KVM Guest support"
	select PARAVIRT
I
Ingo Molnar 已提交
531 532 533
	---help---
	  This option enables various optimizations for running under the KVM
	  hypervisor.
534

535 536
source "arch/x86/lguest/Kconfig"

537 538
config PARAVIRT
	bool "Enable paravirtualization code"
I
Ingo Molnar 已提交
539
	---help---
540 541 542 543 544
	  This changes the kernel so it can modify itself when it is run
	  under a hypervisor, potentially improving performance significantly
	  over full virtualization.  However, when run without a hypervisor
	  the kernel is theoretically slower and slightly larger.

545 546 547 548 549 550 551 552 553 554 555 556 557
config PARAVIRT_SPINLOCKS
	bool "Paravirtualization layer for spinlocks"
	depends on PARAVIRT && SMP && EXPERIMENTAL
	---help---
	  Paravirtualized spinlocks allow a pvops backend to replace the
	  spinlock implementation with something virtualization-friendly
	  (for example, block the virtual CPU rather than spinning).

	  Unfortunately the downside is an up to 5% performance hit on
	  native kernels, with various workloads.

	  If you are unsure how to answer this question, answer N.

558 559 560
config PARAVIRT_CLOCK
	bool

561 562
endif

563
config PARAVIRT_DEBUG
I
Ingo Molnar 已提交
564 565 566 567 568
	bool "paravirt-ops debugging"
	depends on PARAVIRT && DEBUG_KERNEL
	---help---
	  Enable to debug paravirt_ops internals.  Specifically, BUG if
	  a paravirt_op is missing when it is called.
569

570
config NO_BOOTMEM
Y
Yinghai Lu 已提交
571
	def_bool y
572

573 574
config MEMTEST
	bool "Memtest"
I
Ingo Molnar 已提交
575
	---help---
Y
Yinghai Lu 已提交
576
	  This option adds a kernel parameter 'memtest', which allows memtest
577
	  to be set.
I
Ingo Molnar 已提交
578 579 580 581
	        memtest=0, mean disabled; -- default
	        memtest=1, mean do 1 test pattern;
	        ...
	        memtest=4, mean do 4 test patterns.
T
Thomas Gleixner 已提交
582
	  If you are unsure how to answer this question, answer N.
583 584

config X86_SUMMIT_NUMA
585
	def_bool y
586
	depends on X86_32 && NUMA && X86_32_NON_STANDARD
587 588

config X86_CYCLONE_TIMER
589
	def_bool y
590
	depends on X86_32_NON_STANDARD
591 592 593 594

source "arch/x86/Kconfig.cpu"

config HPET_TIMER
595
	def_bool X86_64
596
	prompt "HPET Timer Support" if X86_32
I
Ingo Molnar 已提交
597 598 599 600 601 602 603 604 605
	---help---
	  Use the IA-PC HPET (High Precision Event Timer) to manage
	  time in preference to the PIT and RTC, if a HPET is
	  present.
	  HPET is the next generation timer replacing legacy 8254s.
	  The HPET provides a stable time base on SMP
	  systems, unlike the TSC, but it is more expensive to access,
	  as it is off-chip.  You can find the HPET spec at
	  <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
606

I
Ingo Molnar 已提交
607 608 609
	  You can safely choose Y here.  However, HPET will only be
	  activated if the platform and the BIOS support this feature.
	  Otherwise the 8254 will be used for timing services.
610

I
Ingo Molnar 已提交
611
	  Choose N to continue using the legacy 8254 timer.
612 613

config HPET_EMULATE_RTC
614
	def_bool y
615
	depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
616

617 618 619 620 621 622 623 624 625 626
config APB_TIMER
       def_bool y if MRST
       prompt "Langwell APB Timer Support" if X86_MRST
       help
         APB timer is the replacement for 8254, HPET on X86 MID platforms.
         The APBT provides a stable time base on SMP
         systems, unlike the TSC, but it is more expensive to access,
         as it is off-chip. APB timers are always running regardless of CPU
         C states, they are used as per CPU clockevent device when possible.

627
# Mark as expert because too many people got it wrong.
628
# The code disables itself when not needed.
629 630
config DMI
	default y
631
	bool "Enable DMI scanning" if EXPERT
I
Ingo Molnar 已提交
632
	---help---
633 634 635 636 637
	  Enabled scanning of DMI to identify machine quirks. Say Y
	  here unless you have verified that your setup is not
	  affected by entries in the DMI blacklist. Required by PNP
	  BIOS code.

638
config GART_IOMMU
639
	bool "GART IOMMU support" if EXPERT
640 641
	default y
	select SWIOTLB
642
	depends on X86_64 && PCI && AMD_NB
I
Ingo Molnar 已提交
643
	---help---
644 645 646 647 648 649 650 651 652 653 654 655 656 657
	  Support for full DMA access of devices with 32bit memory access only
	  on systems with more than 3GB. This is usually needed for USB,
	  sound, many IDE/SATA chipsets and some other devices.
	  Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
	  based hardware IOMMU and a software bounce buffer based IOMMU used
	  on Intel systems and as fallback.
	  The code is only active when needed (enough memory and limited
	  device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
	  too.

config CALGARY_IOMMU
	bool "IBM Calgary IOMMU support"
	select SWIOTLB
	depends on X86_64 && PCI && EXPERIMENTAL
I
Ingo Molnar 已提交
658
	---help---
659 660 661 662 663 664 665 666 667 668 669 670 671 672
	  Support for hardware IOMMUs in IBM's xSeries x366 and x460
	  systems. Needed to run systems with more than 3GB of memory
	  properly with 32-bit PCI devices that do not support DAC
	  (Double Address Cycle). Calgary also supports bus level
	  isolation, where all DMAs pass through the IOMMU.  This
	  prevents them from going anywhere except their intended
	  destination. This catches hard-to-find kernel bugs and
	  mis-behaving drivers and devices that do not use the DMA-API
	  properly to set up their DMA buffers.  The IOMMU can be
	  turned off at boot time with the iommu=off parameter.
	  Normally the kernel will make the right choice by itself.
	  If unsure, say Y.

config CALGARY_IOMMU_ENABLED_BY_DEFAULT
673 674
	def_bool y
	prompt "Should Calgary be enabled by default?"
675
	depends on CALGARY_IOMMU
I
Ingo Molnar 已提交
676
	---help---
677 678 679 680 681 682
	  Should Calgary be enabled by default? if you choose 'y', Calgary
	  will be used (if it exists). If you choose 'n', Calgary will not be
	  used even if it exists. If you choose 'n' and would like to use
	  Calgary anyway, pass 'iommu=calgary' on the kernel command line.
	  If unsure, say Y.

J
Joerg Roedel 已提交
683 684
config AMD_IOMMU
	bool "AMD IOMMU support"
I
Ingo Molnar 已提交
685
	select SWIOTLB
686
	select PCI_MSI
687
	select PCI_IOV
I
Ingo Molnar 已提交
688
	depends on X86_64 && PCI && ACPI
I
Ingo Molnar 已提交
689
	---help---
690 691 692 693 694 695 696 697 698
	  With this option you can enable support for AMD IOMMU hardware in
	  your system. An IOMMU is a hardware component which provides
	  remapping of DMA memory accesses from devices. With an AMD IOMMU you
	  can isolate the the DMA memory of different devices and protect the
	  system from misbehaving device drivers or hardware.

	  You can find out if your system has an AMD IOMMU if you look into
	  your BIOS for an option to enable it or if you have an IVRS ACPI
	  table.
J
Joerg Roedel 已提交
699

700 701 702 703
config AMD_IOMMU_STATS
	bool "Export AMD IOMMU statistics to debugfs"
	depends on AMD_IOMMU
	select DEBUG_FS
I
Ingo Molnar 已提交
704
	---help---
705 706 707 708 709
	  This option enables code in the AMD IOMMU driver to collect various
	  statistics about whats happening in the driver and exports that
	  information to userspace via debugfs.
	  If unsure, say N.

710 711
# need this always selected by IOMMU for the VIA workaround
config SWIOTLB
J
Joerg Roedel 已提交
712
	def_bool y if X86_64
I
Ingo Molnar 已提交
713
	---help---
714 715 716 717 718 719
	  Support for software bounce buffers used on x86-64 systems
	  which don't have a hardware IOMMU (e.g. the current generation
	  of Intel's x86-64 CPUs). Using this PCI devices which can only
	  access 32-bits of memory can be used on systems with more than
	  3 GB of memory. If unsure, say Y.

720
config IOMMU_HELPER
721
	def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
722

723 724 725
config IOMMU_API
	def_bool (AMD_IOMMU || DMAR)

726
config MAXSMP
727
	bool "Enable Maximum number of SMP Processors and NUMA Nodes"
M
Mike Travis 已提交
728 729
	depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
	select CPUMASK_OFFSTACK
I
Ingo Molnar 已提交
730
	---help---
731
	  Enable maximum number of CPUS and NUMA Nodes for this architecture.
732
	  If unsure, say N.
733 734

config NR_CPUS
M
Mike Travis 已提交
735
	int "Maximum number of CPUs" if SMP && !MAXSMP
736
	range 2 8 if SMP && X86_32 && !X86_BIGSMP
M
Mike Travis 已提交
737
	range 2 512 if SMP && !MAXSMP
M
Mike Travis 已提交
738
	default "1" if !SMP
739
	default "4096" if MAXSMP
M
Mike Travis 已提交
740 741
	default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
	default "8" if SMP
I
Ingo Molnar 已提交
742
	---help---
743
	  This allows you to specify the maximum number of CPUs which this
744
	  kernel will support.  The maximum supported value is 512 and the
745 746 747 748 749 750 751
	  minimum value which makes sense is 2.

	  This is purely to save memory - each supported CPU adds
	  approximately eight kilobytes to the kernel image.

config SCHED_SMT
	bool "SMT (Hyperthreading) scheduler support"
752
	depends on X86_HT
I
Ingo Molnar 已提交
753
	---help---
754 755 756 757 758 759
	  SMT scheduler support improves the CPU scheduler's decision making
	  when dealing with Intel Pentium 4 chips with HyperThreading at a
	  cost of slightly increased overhead in some places. If unsure say
	  N here.

config SCHED_MC
760 761
	def_bool y
	prompt "Multi-core scheduler support"
762
	depends on X86_HT
I
Ingo Molnar 已提交
763
	---help---
764 765 766 767
	  Multi-core scheduler support improves the CPU scheduler's decision
	  making when dealing with multi-core CPU chips at a cost of slightly
	  increased overhead in some places. If unsure say N here.

V
Venkatesh Pallipadi 已提交
768 769 770 771 772 773 774 775 776 777 778
config IRQ_TIME_ACCOUNTING
	bool "Fine granularity task level IRQ time accounting"
	default n
	---help---
	  Select this option to enable fine granularity task irq time
	  accounting. This is done by reading a timestamp on each
	  transitions between softirq and hardirq state, so there can be a
	  small performance impact.

	  If in doubt, say N here.

779 780 781 782
source "kernel/Kconfig.preempt"

config X86_UP_APIC
	bool "Local APIC support on uniprocessors"
783
	depends on X86_32 && !SMP && !X86_32_NON_STANDARD
I
Ingo Molnar 已提交
784
	---help---
785 786 787 788 789 790 791 792 793 794 795 796
	  A local APIC (Advanced Programmable Interrupt Controller) is an
	  integrated interrupt controller in the CPU. If you have a single-CPU
	  system which has a processor with a local APIC, you can say Y here to
	  enable and use it. If you say Y here even though your machine doesn't
	  have a local APIC, then the kernel will still run with no slowdown at
	  all. The local APIC supports CPU-generated self-interrupts (timer,
	  performance counters), and the NMI watchdog which detects hard
	  lockups.

config X86_UP_IOAPIC
	bool "IO-APIC support on uniprocessors"
	depends on X86_UP_APIC
I
Ingo Molnar 已提交
797
	---help---
798 799 800 801 802 803 804 805 806
	  An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
	  SMP-capable replacement for PC-style interrupt controllers. Most
	  SMP systems and many recent uniprocessor systems have one.

	  If you have a single-CPU system with an IO-APIC, you can say Y here
	  to use it. If you say Y here even though your machine doesn't have
	  an IO-APIC, then the kernel will still run with no slowdown at all.

config X86_LOCAL_APIC
807
	def_bool y
808
	depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
809 810

config X86_IO_APIC
811
	def_bool y
812
	depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC
813 814

config X86_VISWS_APIC
815
	def_bool y
816 817
	depends on X86_32 && X86_VISWS

818 819 820
config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
	bool "Reroute for broken boot IRQs"
	depends on X86_IO_APIC
I
Ingo Molnar 已提交
821
	---help---
822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840
	  This option enables a workaround that fixes a source of
	  spurious interrupts. This is recommended when threaded
	  interrupt handling is used on systems where the generation of
	  superfluous "boot interrupts" cannot be disabled.

	  Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
	  entry in the chipset's IO-APIC is masked (as, e.g. the RT
	  kernel does during interrupt handling). On chipsets where this
	  boot IRQ generation cannot be disabled, this workaround keeps
	  the original IRQ line masked so that only the equivalent "boot
	  IRQ" is delivered to the CPUs. The workaround also tells the
	  kernel to set up the IRQ handler on the boot IRQ line. In this
	  way only one interrupt is delivered to the kernel. Otherwise
	  the spurious second interrupt may cause the kernel to bring
	  down (vital) interrupt lines.

	  Only affects "broken" chipsets. Interrupt sharing may be
	  increased on these systems.

841
config X86_MCE
842
	bool "Machine Check / overheating reporting"
843
	---help---
844 845
	  Machine Check support allows the processor to notify the
	  kernel if it detects a problem (e.g. overheating, data corruption).
846
	  The action the kernel takes depends on the severity of the problem,
847
	  ranging from warning messages to halting the machine.
848

849
config X86_MCE_INTEL
850 851
	def_bool y
	prompt "Intel MCE features"
852
	depends on X86_MCE && X86_LOCAL_APIC
I
Ingo Molnar 已提交
853
	---help---
854 855 856 857
	   Additional support for intel specific MCE features such as
	   the thermal monitor.

config X86_MCE_AMD
858 859
	def_bool y
	prompt "AMD MCE features"
860
	depends on X86_MCE && X86_LOCAL_APIC
I
Ingo Molnar 已提交
861
	---help---
862 863 864
	   Additional support for AMD specific MCE features such as
	   the DRAM Error Threshold.

865
config X86_ANCIENT_MCE
J
Jan Beulich 已提交
866
	bool "Support for old Pentium 5 / WinChip machine checks"
867
	depends on X86_32 && X86_MCE
868 869 870 871
	---help---
	  Include support for machine check handling on old Pentium 5 or WinChip
	  systems. These typically need to be enabled explicitely on the command
	  line.
872

873 874
config X86_MCE_THRESHOLD
	depends on X86_MCE_AMD || X86_MCE_INTEL
J
Jan Beulich 已提交
875
	def_bool y
876

877
config X86_MCE_INJECT
878
	depends on X86_MCE
879 880 881 882 883 884
	tristate "Machine check injector support"
	---help---
	  Provide support for injecting machine checks for testing purposes.
	  If you don't know what a machine check is and you don't do kernel
	  QA it is safe to say n.

885 886
config X86_THERMAL_VECTOR
	def_bool y
887
	depends on X86_MCE_INTEL
888

889
config VM86
890
	bool "Enable VM86 support" if EXPERT
891 892
	default y
	depends on X86_32
I
Ingo Molnar 已提交
893 894
	---help---
	  This option is required by programs like DOSEMU to run 16-bit legacy
895
	  code on X86 processors. It also may be needed by software like
I
Ingo Molnar 已提交
896 897
	  XFree86 to initialize some video cards via BIOS. Disabling this
	  option saves about 6k.
898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916

config TOSHIBA
	tristate "Toshiba Laptop support"
	depends on X86_32
	---help---
	  This adds a driver to safely access the System Management Mode of
	  the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
	  not work on models with a Phoenix BIOS. The System Management Mode
	  is used to set the BIOS and power saving options on Toshiba portables.

	  For information on utilities to make use of this driver see the
	  Toshiba Linux utilities web site at:
	  <http://www.buzzard.org.uk/toshiba/>.

	  Say Y if you intend to run this kernel on a Toshiba portable.
	  Say N otherwise.

config I8K
	tristate "Dell laptop support"
917
	select HWMON
918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936
	---help---
	  This adds a driver to safely access the System Management Mode
	  of the CPU on the Dell Inspiron 8000. The System Management Mode
	  is used to read cpu temperature and cooling fan status and to
	  control the fans on the I8K portables.

	  This driver has been tested only on the Inspiron 8000 but it may
	  also work with other Dell laptops. You can force loading on other
	  models by passing the parameter `force=1' to the module. Use at
	  your own risk.

	  For information on utilities to make use of this driver see the
	  I8K Linux utilities web site at:
	  <http://people.debian.org/~dz/i8k/>

	  Say Y if you intend to run this kernel on a Dell Inspiron 8000.
	  Say N otherwise.

config X86_REBOOTFIXUPS
937 938
	bool "Enable X86 board specific fixups for reboot"
	depends on X86_32
939 940 941 942 943 944 945 946
	---help---
	  This enables chipset and/or board specific fixups to be done
	  in order to get reboot to work correctly. This is only needed on
	  some combinations of hardware and BIOS. The symptom, for which
	  this config is intended, is when reboot ends with a stalled/hung
	  system.

	  Currently, the only fixup is for the Geode machines using
947
	  CS5530A and CS5536 chipsets and the RDC R-321x SoC.
948 949 950 951 952 953

	  Say Y if you want to enable the fixup. Currently, it's safe to
	  enable this option even if you don't need it.
	  Say N otherwise.

config MICROCODE
P
Peter Oruba 已提交
954
	tristate "/dev/cpu/microcode - microcode support"
955 956 957
	select FW_LOADER
	---help---
	  If you say Y here, you will be able to update the microcode on
958 959 960 961 962 963
	  certain Intel and AMD processors. The Intel support is for the
	  IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
	  Pentium 4, Xeon etc. The AMD support is for family 0x10 and
	  0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
	  You will obviously need the actual microcode binary data itself
	  which is not shipped with the Linux kernel.
964

P
Peter Oruba 已提交
965 966
	  This option selects the general module only, you need to select
	  at least one vendor specific module as well.
967 968 969 970

	  To compile this driver as a module, choose M here: the
	  module will be called microcode.

P
Peter Oruba 已提交
971
config MICROCODE_INTEL
I
Ingo Molnar 已提交
972 973 974 975 976 977 978 979 980 981 982
	bool "Intel microcode patch loading support"
	depends on MICROCODE
	default MICROCODE
	select FW_LOADER
	---help---
	  This options enables microcode patch loading support for Intel
	  processors.

	  For latest news and information on obtaining all the required
	  Intel ingredients for this driver, check:
	  <http://www.urbanmyth.org/microcode/>.
P
Peter Oruba 已提交
983

984
config MICROCODE_AMD
I
Ingo Molnar 已提交
985 986 987 988 989 990
	bool "AMD microcode patch loading support"
	depends on MICROCODE
	select FW_LOADER
	---help---
	  If you select this option, microcode patch loading support for AMD
	  processors will be enabled.
991

I
Ingo Molnar 已提交
992
config MICROCODE_OLD_INTERFACE
993
	def_bool y
994 995 996 997
	depends on MICROCODE

config X86_MSR
	tristate "/dev/cpu/*/msr - Model-specific register support"
I
Ingo Molnar 已提交
998
	---help---
999 1000 1001 1002 1003 1004 1005 1006
	  This device gives privileged processes access to the x86
	  Model-Specific Registers (MSRs).  It is a character device with
	  major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
	  MSR accesses are directed to a specific CPU on multi-processor
	  systems.

config X86_CPUID
	tristate "/dev/cpu/*/cpuid - CPU information support"
I
Ingo Molnar 已提交
1007
	---help---
1008 1009 1010 1011 1012 1013 1014 1015
	  This device gives processes access to the x86 CPUID instruction to
	  be executed on a specific processor.  It is a character device
	  with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
	  /dev/cpu/31/cpuid.

choice
	prompt "High Memory Support"
	default HIGHMEM64G if X86_NUMAQ
J
Jan Beulich 已提交
1016
	default HIGHMEM4G
1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058
	depends on X86_32

config NOHIGHMEM
	bool "off"
	depends on !X86_NUMAQ
	---help---
	  Linux can use up to 64 Gigabytes of physical memory on x86 systems.
	  However, the address space of 32-bit x86 processors is only 4
	  Gigabytes large. That means that, if you have a large amount of
	  physical memory, not all of it can be "permanently mapped" by the
	  kernel. The physical memory that's not permanently mapped is called
	  "high memory".

	  If you are compiling a kernel which will never run on a machine with
	  more than 1 Gigabyte total physical RAM, answer "off" here (default
	  choice and suitable for most users). This will result in a "3GB/1GB"
	  split: 3GB are mapped so that each process sees a 3GB virtual memory
	  space and the remaining part of the 4GB virtual memory space is used
	  by the kernel to permanently map as much physical memory as
	  possible.

	  If the machine has between 1 and 4 Gigabytes physical RAM, then
	  answer "4GB" here.

	  If more than 4 Gigabytes is used then answer "64GB" here. This
	  selection turns Intel PAE (Physical Address Extension) mode on.
	  PAE implements 3-level paging on IA32 processors. PAE is fully
	  supported by Linux, PAE mode is implemented on all recent Intel
	  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
	  then the kernel will not boot on CPUs that don't support PAE!

	  The actual amount of total physical memory will either be
	  auto detected or can be forced by using a kernel command line option
	  such as "mem=256M". (Try "man bootparam" or see the documentation of
	  your boot loader (lilo or loadlin) about how to pass options to the
	  kernel at boot time.)

	  If unsure, say "off".

config HIGHMEM4G
	bool "4GB"
	depends on !X86_NUMAQ
I
Ingo Molnar 已提交
1059
	---help---
1060 1061 1062 1063 1064 1065 1066
	  Select this if you have a 32-bit processor and between 1 and 4
	  gigabytes of physical RAM.

config HIGHMEM64G
	bool "64GB"
	depends on !M386 && !M486
	select X86_PAE
I
Ingo Molnar 已提交
1067
	---help---
1068 1069 1070 1071 1072 1073 1074
	  Select this if you have a 32-bit processor and more than 4
	  gigabytes of physical RAM.

endchoice

choice
	depends on EXPERIMENTAL
1075
	prompt "Memory split" if EXPERT
1076 1077
	default VMSPLIT_3G
	depends on X86_32
I
Ingo Molnar 已提交
1078
	---help---
1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117
	  Select the desired split between kernel and user memory.

	  If the address range available to the kernel is less than the
	  physical memory installed, the remaining memory will be available
	  as "high memory". Accessing high memory is a little more costly
	  than low memory, as it needs to be mapped into the kernel first.
	  Note that increasing the kernel address space limits the range
	  available to user programs, making the address space there
	  tighter.  Selecting anything other than the default 3G/1G split
	  will also likely make your kernel incompatible with binary-only
	  kernel modules.

	  If you are not absolutely sure what you are doing, leave this
	  option alone!

	config VMSPLIT_3G
		bool "3G/1G user/kernel split"
	config VMSPLIT_3G_OPT
		depends on !X86_PAE
		bool "3G/1G user/kernel split (for full 1G low memory)"
	config VMSPLIT_2G
		bool "2G/2G user/kernel split"
	config VMSPLIT_2G_OPT
		depends on !X86_PAE
		bool "2G/2G user/kernel split (for full 2G low memory)"
	config VMSPLIT_1G
		bool "1G/3G user/kernel split"
endchoice

config PAGE_OFFSET
	hex
	default 0xB0000000 if VMSPLIT_3G_OPT
	default 0x80000000 if VMSPLIT_2G
	default 0x78000000 if VMSPLIT_2G_OPT
	default 0x40000000 if VMSPLIT_1G
	default 0xC0000000
	depends on X86_32

config HIGHMEM
1118
	def_bool y
1119 1120 1121
	depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)

config X86_PAE
1122
	bool "PAE (Physical Address Extension) Support"
1123
	depends on X86_32 && !HIGHMEM4G
I
Ingo Molnar 已提交
1124
	---help---
1125 1126 1127 1128 1129
	  PAE is required for NX support, and furthermore enables
	  larger swapspace support for non-overcommit purposes. It
	  has the cost of more pagetable lookup overhead, and also
	  consumes more pagetable space per process.

1130
config ARCH_PHYS_ADDR_T_64BIT
I
Ingo Molnar 已提交
1131
	def_bool X86_64 || X86_PAE
1132

1133 1134 1135
config ARCH_DMA_ADDR_T_64BIT
	def_bool X86_64 || HIGHMEM64G

1136
config DIRECT_GBPAGES
1137
	bool "Enable 1GB pages for kernel pagetables" if EXPERT
1138 1139
	default y
	depends on X86_64
I
Ingo Molnar 已提交
1140
	---help---
1141 1142 1143 1144
	  Allow the kernel linear mapping to use 1GB pages on CPUs that
	  support it. This can improve the kernel's performance a tiny bit by
	  reducing TLB pressure. If in doubt, say "Y".

1145 1146
# Common NUMA Features
config NUMA
1147
	bool "Numa Memory Allocation and Scheduler Support"
1148
	depends on SMP
1149
	depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1150
	default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
I
Ingo Molnar 已提交
1151
	---help---
1152
	  Enable NUMA (Non Uniform Memory Access) support.
1153

1154 1155 1156 1157
	  The kernel will try to allocate memory used by a CPU on the
	  local memory controller of the CPU and add some more
	  NUMA awareness to the kernel.

1158
	  For 64-bit this is recommended if the system is Intel Core i7
1159 1160 1161 1162 1163 1164 1165
	  (or later), AMD Opteron, or EM64T NUMA.

	  For 32-bit this is only needed on (rare) 32-bit-only platforms
	  that support NUMA topologies, such as NUMAQ / Summit, or if you
	  boot a 32-bit kernel on a 64-bit NUMA platform.

	  Otherwise, you should say N.
1166 1167 1168 1169

comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
	depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)

1170
config AMD_NUMA
1171 1172
	def_bool y
	prompt "Old style AMD Opteron NUMA detection"
1173
	depends on NUMA && PCI
I
Ingo Molnar 已提交
1174
	---help---
1175 1176 1177 1178 1179
	  Enable AMD NUMA node topology detection.  You should say Y here if
	  you have a multi processor AMD system. This uses an old method to
	  read the NUMA configuration directly from the builtin Northbridge
	  of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
	  which also takes priority if both are compiled in.
1180 1181

config X86_64_ACPI_NUMA
1182 1183
	def_bool y
	prompt "ACPI NUMA detection"
1184 1185
	depends on X86_64 && NUMA && ACPI && PCI
	select ACPI_NUMA
I
Ingo Molnar 已提交
1186
	---help---
1187 1188
	  Enable ACPI SRAT based node topology detection.

1189 1190 1191 1192 1193 1194 1195 1196 1197
# Some NUMA nodes have memory ranges that span
# other nodes.  Even though a pfn is valid and
# between a node's start and end pfns, it may not
# reside on that node.  See memmap_init_zone()
# for details.
config NODES_SPAN_OTHER_NODES
	def_bool y
	depends on X86_64_ACPI_NUMA

1198 1199
config NUMA_EMU
	bool "NUMA emulation"
1200
	depends on NUMA
I
Ingo Molnar 已提交
1201
	---help---
1202 1203 1204 1205 1206
	  Enable NUMA emulation. A flat machine will be split
	  into virtual nodes when booted with "numa=fake=N", where N is the
	  number of nodes. This is only useful for debugging.

config NODES_SHIFT
1207
	int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1208 1209
	range 1 10
	default "10" if MAXSMP
1210 1211 1212 1213
	default "6" if X86_64
	default "4" if X86_NUMAQ
	default "3"
	depends on NEED_MULTIPLE_NODES
I
Ingo Molnar 已提交
1214
	---help---
1215
	  Specify the maximum number of NUMA Nodes available on the target
1216
	  system.  Increases memory reserved to accommodate various tables.
1217

1218
config HAVE_ARCH_BOOTMEM
1219
	def_bool y
1220 1221
	depends on X86_32 && NUMA

1222 1223 1224 1225
config HAVE_ARCH_ALLOC_REMAP
	def_bool y
	depends on X86_32 && NUMA

1226
config ARCH_HAVE_MEMORY_PRESENT
1227
	def_bool y
1228 1229 1230
	depends on X86_32 && DISCONTIGMEM

config NEED_NODE_MEMMAP_SIZE
1231
	def_bool y
1232 1233 1234 1235
	depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)

config ARCH_FLATMEM_ENABLE
	def_bool y
1236
	depends on X86_32 && !NUMA
1237 1238 1239

config ARCH_DISCONTIGMEM_ENABLE
	def_bool y
1240
	depends on NUMA && X86_32
1241 1242 1243

config ARCH_DISCONTIGMEM_DEFAULT
	def_bool y
1244 1245
	depends on NUMA && X86_32

1246 1247
config ARCH_SPARSEMEM_ENABLE
	def_bool y
1248
	depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1249 1250 1251
	select SPARSEMEM_STATIC if X86_32
	select SPARSEMEM_VMEMMAP_ENABLE if X86_64

1252 1253 1254 1255
config ARCH_SPARSEMEM_DEFAULT
	def_bool y
	depends on X86_64

1256 1257
config ARCH_SELECT_MEMORY_MODEL
	def_bool y
1258
	depends on ARCH_SPARSEMEM_ENABLE
1259 1260 1261 1262 1263

config ARCH_MEMORY_PROBE
	def_bool X86_64
	depends on MEMORY_HOTPLUG

1264 1265 1266 1267
config ARCH_PROC_KCORE_TEXT
	def_bool y
	depends on X86_64 && PROC_KCORE

1268 1269 1270 1271 1272
config ILLEGAL_POINTER_VALUE
       hex
       default 0 if X86_32
       default 0xdead000000000000 if X86_64

1273 1274 1275 1276
source "mm/Kconfig"

config HIGHPTE
	bool "Allocate 3rd-level pagetables from highmem"
J
Jan Beulich 已提交
1277
	depends on HIGHMEM
I
Ingo Molnar 已提交
1278
	---help---
1279 1280 1281 1282 1283
	  The VM uses one page table entry for each page of physical memory.
	  For systems with a lot of RAM, this can be wasteful of precious
	  low memory.  Setting this option will put user-space page table
	  entries in high memory.

1284
config X86_CHECK_BIOS_CORRUPTION
I
Ingo Molnar 已提交
1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304
	bool "Check for low memory corruption"
	---help---
	  Periodically check for memory corruption in low memory, which
	  is suspected to be caused by BIOS.  Even when enabled in the
	  configuration, it is disabled at runtime.  Enable it by
	  setting "memory_corruption_check=1" on the kernel command
	  line.  By default it scans the low 64k of memory every 60
	  seconds; see the memory_corruption_check_size and
	  memory_corruption_check_period parameters in
	  Documentation/kernel-parameters.txt to adjust this.

	  When enabled with the default parameters, this option has
	  almost no overhead, as it reserves a relatively small amount
	  of memory and scans it infrequently.  It both detects corruption
	  and prevents it from affecting the running system.

	  It is, however, intended as a diagnostic tool; if repeatable
	  BIOS-originated corruption always affects the same memory,
	  you can use memmap= to prevent the kernel from using that
	  memory.
1305

1306
config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
I
Ingo Molnar 已提交
1307
	bool "Set the default setting of memory_corruption_check"
1308 1309
	depends on X86_CHECK_BIOS_CORRUPTION
	default y
I
Ingo Molnar 已提交
1310 1311 1312
	---help---
	  Set whether the default state of memory_corruption_check is
	  on or off.
1313

1314
config X86_RESERVE_LOW
1315 1316 1317
	int "Amount of low memory, in kilobytes, to reserve for the BIOS"
	default 64
	range 4 640
I
Ingo Molnar 已提交
1318
	---help---
1319 1320 1321 1322 1323 1324 1325 1326 1327
	  Specify the amount of low memory to reserve for the BIOS.

	  The first page contains BIOS data structures that the kernel
	  must not use, so that page must always be reserved.

	  By default we reserve the first 64K of physical RAM, as a
	  number of BIOSes are known to corrupt that memory range
	  during events such as suspend/resume or monitor cable
	  insertion, so it must not be used by the kernel.
I
Ingo Molnar 已提交
1328

1329 1330 1331 1332 1333
	  You can set this to 4 if you are absolutely sure that you
	  trust the BIOS to get all its memory reservations and usages
	  right.  If you know your BIOS have problems beyond the
	  default 64K area, you can set this to 640 to avoid using the
	  entire low memory range.
I
Ingo Molnar 已提交
1334

1335 1336 1337 1338 1339
	  If you have doubts about the BIOS (e.g. suspend/resume does
	  not work or there's kernel crashes after certain hardware
	  hotplug events) then you might want to enable
	  X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
	  typical corruption patterns.
I
Ingo Molnar 已提交
1340

1341
	  Leave this to the default value of 64 if you are unsure.
I
Ingo Molnar 已提交
1342

1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369
config MATH_EMULATION
	bool
	prompt "Math emulation" if X86_32
	---help---
	  Linux can emulate a math coprocessor (used for floating point
	  operations) if you don't have one. 486DX and Pentium processors have
	  a math coprocessor built in, 486SX and 386 do not, unless you added
	  a 487DX or 387, respectively. (The messages during boot time can
	  give you some hints here ["man dmesg"].) Everyone needs either a
	  coprocessor or this emulation.

	  If you don't have a math coprocessor, you need to say Y here; if you
	  say Y here even though you have a coprocessor, the coprocessor will
	  be used nevertheless. (This behavior can be changed with the kernel
	  command line option "no387", which comes handy if your coprocessor
	  is broken. Try "man bootparam" or see the documentation of your boot
	  loader (lilo or loadlin) about how to pass options to the kernel at
	  boot time.) This means that it is a good idea to say Y here if you
	  intend to use this kernel on different machines.

	  More information about the internals of the Linux math coprocessor
	  emulation can be found in <file:arch/x86/math-emu/README>.

	  If you are not sure, say Y; apart from resulting in a 66 KB bigger
	  kernel, it won't hurt.

config MTRR
J
Jan Beulich 已提交
1370
	def_bool y
1371
	prompt "MTRR (Memory Type Range Register) support" if EXPERT
1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401
	---help---
	  On Intel P6 family processors (Pentium Pro, Pentium II and later)
	  the Memory Type Range Registers (MTRRs) may be used to control
	  processor access to memory ranges. This is most useful if you have
	  a video (VGA) card on a PCI or AGP bus. Enabling write-combining
	  allows bus write transfers to be combined into a larger transfer
	  before bursting over the PCI/AGP bus. This can increase performance
	  of image write operations 2.5 times or more. Saying Y here creates a
	  /proc/mtrr file which may be used to manipulate your processor's
	  MTRRs. Typically the X server should use this.

	  This code has a reasonably generic interface so that similar
	  control registers on other processors can be easily supported
	  as well:

	  The Cyrix 6x86, 6x86MX and M II processors have Address Range
	  Registers (ARRs) which provide a similar functionality to MTRRs. For
	  these, the ARRs are used to emulate the MTRRs.
	  The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
	  MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
	  write-combining. All of these processors are supported by this code
	  and it makes sense to say Y here if you have one of them.

	  Saying Y here also fixes a problem with buggy SMP BIOSes which only
	  set the MTRRs for the boot CPU and not for the secondary CPUs. This
	  can lead to all sorts of problems, so it's good to say Y here.

	  You can safely say Y even if your machine doesn't have MTRRs, you'll
	  just add about 9 KB to your kernel.

1402
	  See <file:Documentation/x86/mtrr.txt> for more information.
1403

1404
config MTRR_SANITIZER
1405
	def_bool y
1406 1407
	prompt "MTRR cleanup support"
	depends on MTRR
I
Ingo Molnar 已提交
1408
	---help---
T
Thomas Gleixner 已提交
1409 1410
	  Convert MTRR layout from continuous to discrete, so X drivers can
	  add writeback entries.
1411

T
Thomas Gleixner 已提交
1412
	  Can be disabled with disable_mtrr_cleanup on the kernel command line.
1413
	  The largest mtrr entry size for a continuous block can be set with
T
Thomas Gleixner 已提交
1414
	  mtrr_chunk_size.
1415

1416
	  If unsure, say Y.
1417 1418

config MTRR_SANITIZER_ENABLE_DEFAULT
1419 1420 1421
	int "MTRR cleanup enable value (0-1)"
	range 0 1
	default "0"
1422
	depends on MTRR_SANITIZER
I
Ingo Molnar 已提交
1423
	---help---
1424
	  Enable mtrr cleanup default value
1425

1426 1427 1428 1429 1430
config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
	int "MTRR cleanup spare reg num (0-7)"
	range 0 7
	default "1"
	depends on MTRR_SANITIZER
I
Ingo Molnar 已提交
1431
	---help---
1432
	  mtrr cleanup spare entries default, it can be changed via
T
Thomas Gleixner 已提交
1433
	  mtrr_spare_reg_nr=N on the kernel command line.
1434

1435
config X86_PAT
J
Jan Beulich 已提交
1436
	def_bool y
1437
	prompt "x86 PAT support" if EXPERT
1438
	depends on MTRR
I
Ingo Molnar 已提交
1439
	---help---
1440
	  Use PAT attributes to setup page level cache control.
1441

1442 1443 1444 1445
	  PATs are the modern equivalents of MTRRs and are much more
	  flexible than MTRRs.

	  Say N here if you see bootup problems (boot crash, boot hang,
1446
	  spontaneous reboots) or a non-working video driver.
1447 1448 1449

	  If unsure, say Y.

1450 1451 1452 1453
config ARCH_USES_PG_UNCACHED
	def_bool y
	depends on X86_PAT

1454
config EFI
1455
	bool "EFI runtime service support"
H
Huang, Ying 已提交
1456
	depends on ACPI
1457
	---help---
I
Ingo Molnar 已提交
1458 1459
	  This enables the kernel to use EFI runtime services that are
	  available (such as the EFI variable services).
1460

I
Ingo Molnar 已提交
1461 1462 1463 1464 1465 1466
	  This option is only useful on systems that have EFI firmware.
	  In addition, you should use the latest ELILO loader available
	  at <http://elilo.sourceforge.net> in order to take advantage
	  of EFI runtime services. However, even with this option, the
	  resultant kernel should continue to boot on existing non-EFI
	  platforms.
1467 1468

config SECCOMP
1469 1470
	def_bool y
	prompt "Enable seccomp to safely compute untrusted bytecode"
I
Ingo Molnar 已提交
1471
	---help---
1472 1473 1474 1475 1476 1477
	  This kernel feature is useful for number crunching applications
	  that may need to compute untrusted bytecode during their
	  execution. By using pipes or other transports made available to
	  the process as file descriptors supporting the read/write
	  syscalls, it's possible to isolate those applications in
	  their own address space using seccomp. Once seccomp is
1478
	  enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1479 1480 1481 1482 1483 1484 1485
	  and the task is only allowed to execute a few safe syscalls
	  defined by each seccomp mode.

	  If unsure, say Y. Only embedded should say N here.

config CC_STACKPROTECTOR
	bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
I
Ingo Molnar 已提交
1486 1487
	---help---
	  This option turns on the -fstack-protector GCC feature. This
I
Ingo Molnar 已提交
1488 1489
	  feature puts, at the beginning of functions, a canary value on
	  the stack just before the return address, and validates
1490 1491 1492 1493 1494 1495 1496
	  the value just before actually returning.  Stack based buffer
	  overflows (that need to overwrite this return address) now also
	  overwrite the canary, which gets detected and the attack is then
	  neutralized via a kernel panic.

	  This feature requires gcc version 4.2 or above, or a distribution
	  gcc with the feature backported. Older versions are automatically
I
Ingo Molnar 已提交
1497 1498
	  detected and for those versions, this configuration option is
	  ignored. (and a warning is printed during bootup)
1499 1500 1501 1502 1503

source kernel/Kconfig.hz

config KEXEC
	bool "kexec system call"
I
Ingo Molnar 已提交
1504
	---help---
1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518
	  kexec is a system call that implements the ability to shutdown your
	  current kernel, and to start another kernel.  It is like a reboot
	  but it is independent of the system firmware.   And like a reboot
	  you can start any kernel with it, not just Linux.

	  The name comes from the similarity to the exec system call.

	  It is an ongoing process to be certain the hardware in a machine
	  is properly shutdown, so do not be surprised if this code does not
	  initially work for you.  It may help to enable device hotplugging
	  support.  As of this writing the exact hardware interface is
	  strongly in flux, so no good recommendation can be made.

config CRASH_DUMP
1519
	bool "kernel crash dumps"
1520
	depends on X86_64 || (X86_32 && HIGHMEM)
I
Ingo Molnar 已提交
1521
	---help---
1522 1523 1524 1525 1526 1527 1528 1529 1530 1531
	  Generate crash dump after being started by kexec.
	  This should be normally only set in special crash dump kernels
	  which are loaded in the main kernel with kexec-tools into
	  a specially reserved region and then later executed after
	  a crash by kdump/kexec. The crash dump kernel must be compiled
	  to a memory address not used by the main kernel or BIOS using
	  PHYSICAL_START, or it must be built as a relocatable image
	  (CONFIG_RELOCATABLE=y).
	  For more details see Documentation/kdump/kdump.txt

H
Huang Ying 已提交
1532 1533 1534
config KEXEC_JUMP
	bool "kexec jump (EXPERIMENTAL)"
	depends on EXPERIMENTAL
1535
	depends on KEXEC && HIBERNATION
I
Ingo Molnar 已提交
1536
	---help---
1537 1538
	  Jump between original kernel and kexeced kernel and invoke
	  code in physical address mode via KEXEC
H
Huang Ying 已提交
1539

1540
config PHYSICAL_START
1541
	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
1542
	default "0x1000000"
I
Ingo Molnar 已提交
1543
	---help---
1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560
	  This gives the physical address where the kernel is loaded.

	  If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
	  bzImage will decompress itself to above physical address and
	  run from there. Otherwise, bzImage will run from the address where
	  it has been loaded by the boot loader and will ignore above physical
	  address.

	  In normal kdump cases one does not have to set/change this option
	  as now bzImage can be compiled as a completely relocatable image
	  (CONFIG_RELOCATABLE=y) and be used to load and run from a different
	  address. This option is mainly useful for the folks who don't want
	  to use a bzImage for capturing the crash dump and want to use a
	  vmlinux instead. vmlinux is not relocatable hence a kernel needs
	  to be specifically compiled to run from a specific memory area
	  (normally a reserved region) and this option comes handy.

1561 1562 1563 1564 1565 1566 1567 1568 1569
	  So if you are using bzImage for capturing the crash dump,
	  leave the value here unchanged to 0x1000000 and set
	  CONFIG_RELOCATABLE=y.  Otherwise if you plan to use vmlinux
	  for capturing the crash dump change this value to start of
	  the reserved region.  In other words, it can be set based on
	  the "X" value as specified in the "crashkernel=YM@XM"
	  command line boot parameter passed to the panic-ed
	  kernel. Please take a look at Documentation/kdump/kdump.txt
	  for more details about crash dumps.
1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581

	  Usage of bzImage for capturing the crash dump is recommended as
	  one does not have to build two kernels. Same kernel can be used
	  as production kernel and capture kernel. Above option should have
	  gone away after relocatable bzImage support is introduced. But it
	  is present because there are users out there who continue to use
	  vmlinux for dump capture. This option should go away down the
	  line.

	  Don't change this unless you know what you are doing.

config RELOCATABLE
1582 1583
	bool "Build a relocatable kernel"
	default y
I
Ingo Molnar 已提交
1584
	---help---
1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597
	  This builds a kernel image that retains relocation information
	  so it can be loaded someplace besides the default 1MB.
	  The relocations tend to make the kernel binary about 10% larger,
	  but are discarded at runtime.

	  One use is for the kexec on panic case where the recovery kernel
	  must live at a different physical address than the primary
	  kernel.

	  Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
	  it has been loaded at and the compile time physical address
	  (CONFIG_PHYSICAL_START) is ignored.

1598 1599 1600 1601 1602
# Relocation on x86-32 needs some additional build support
config X86_NEED_RELOCS
	def_bool y
	depends on X86_32 && RELOCATABLE

1603
config PHYSICAL_ALIGN
J
Jan Beulich 已提交
1604
	hex "Alignment value to which kernel should be aligned" if X86_32
1605 1606
	default "0x1000000"
	range 0x2000 0x1000000
I
Ingo Molnar 已提交
1607
	---help---
1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626
	  This value puts the alignment restrictions on physical address
	  where kernel is loaded and run from. Kernel is compiled for an
	  address which meets above alignment restriction.

	  If bootloader loads the kernel at a non-aligned address and
	  CONFIG_RELOCATABLE is set, kernel will move itself to nearest
	  address aligned to above value and run from there.

	  If bootloader loads the kernel at a non-aligned address and
	  CONFIG_RELOCATABLE is not set, kernel will ignore the run time
	  load address and decompress itself to the address it has been
	  compiled for and run from there. The address for which kernel is
	  compiled already meets above alignment restrictions. Hence the
	  end result is that kernel runs from a physical address meeting
	  above alignment restrictions.

	  Don't change this unless you know what you are doing.

config HOTPLUG_CPU
1627
	bool "Support for hot-pluggable CPUs"
1628
	depends on SMP && HOTPLUG
1629
	---help---
1630 1631 1632 1633 1634
	  Say Y here to allow turning CPUs off and on. CPUs can be
	  controlled through /sys/devices/system/cpu.
	  ( Note: power management support will enable this option
	    automatically on SMP systems. )
	  Say N if you want to disable CPU hotplug.
1635 1636

config COMPAT_VDSO
1637 1638
	def_bool y
	prompt "Compat VDSO support"
R
Roland McGrath 已提交
1639
	depends on X86_32 || IA32_EMULATION
I
Ingo Molnar 已提交
1640
	---help---
R
Roland McGrath 已提交
1641
	  Map the 32-bit VDSO to the predictable old-style address too.
R
Randy Dunlap 已提交
1642

1643 1644 1645 1646 1647 1648
	  Say N here if you are running a sufficiently recent glibc
	  version (2.3.3 or later), to remove the high-mapped
	  VDSO mapping and to exclusively use the randomized VDSO.

	  If unsure, say Y.

1649 1650
config CMDLINE_BOOL
	bool "Built-in kernel command line"
I
Ingo Molnar 已提交
1651
	---help---
1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668
	  Allow for specifying boot arguments to the kernel at
	  build time.  On some systems (e.g. embedded ones), it is
	  necessary or convenient to provide some or all of the
	  kernel boot arguments with the kernel itself (that is,
	  to not rely on the boot loader to provide them.)

	  To compile command line arguments into the kernel,
	  set this option to 'Y', then fill in the
	  the boot arguments in CONFIG_CMDLINE.

	  Systems with fully functional boot loaders (i.e. non-embedded)
	  should leave this option set to 'N'.

config CMDLINE
	string "Built-in kernel command string"
	depends on CMDLINE_BOOL
	default ""
I
Ingo Molnar 已提交
1669
	---help---
1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684
	  Enter arguments here that should be compiled into the kernel
	  image and used at boot time.  If the boot loader provides a
	  command line at boot time, it is appended to this string to
	  form the full kernel command line, when the system boots.

	  However, you can use the CONFIG_CMDLINE_OVERRIDE option to
	  change this behavior.

	  In most cases, the command line (whether built-in or provided
	  by the boot loader) should specify the device for the root
	  file system.

config CMDLINE_OVERRIDE
	bool "Built-in command line overrides boot loader arguments"
	depends on CMDLINE_BOOL
I
Ingo Molnar 已提交
1685
	---help---
1686 1687 1688 1689 1690 1691
	  Set this option to 'Y' to have the kernel ignore the boot loader
	  command line, and use ONLY the built-in command line.

	  This is used to work around broken boot loaders.  This should
	  be set to 'N' under normal conditions.

1692 1693 1694 1695 1696 1697
endmenu

config ARCH_ENABLE_MEMORY_HOTPLUG
	def_bool y
	depends on X86_64 || (X86_32 && HIGHMEM)

1698 1699 1700 1701
config ARCH_ENABLE_MEMORY_HOTREMOVE
	def_bool y
	depends on MEMORY_HOTPLUG

1702
config USE_PERCPU_NUMA_NODE_ID
1703
	def_bool y
1704 1705
	depends on NUMA

1706
menu "Power management and ACPI options"
1707 1708

config ARCH_HIBERNATION_HEADER
1709
	def_bool y
1710 1711 1712 1713 1714 1715
	depends on X86_64 && HIBERNATION

source "kernel/power/Kconfig"

source "drivers/acpi/Kconfig"

F
Feng Tang 已提交
1716 1717
source "drivers/sfi/Kconfig"

1718
config X86_APM_BOOT
J
Jan Beulich 已提交
1719
	def_bool y
1720 1721
	depends on APM || APM_MODULE

1722 1723
menuconfig APM
	tristate "APM (Advanced Power Management) BIOS support"
1724
	depends on X86_32 && PM_SLEEP
1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739
	---help---
	  APM is a BIOS specification for saving power using several different
	  techniques. This is mostly useful for battery powered laptops with
	  APM compliant BIOSes. If you say Y here, the system time will be
	  reset after a RESUME operation, the /proc/apm device will provide
	  battery status information, and user-space programs will receive
	  notification of APM "events" (e.g. battery status change).

	  If you select "Y" here, you can disable actual use of the APM
	  BIOS by passing the "apm=off" option to the kernel at boot time.

	  Note that the APM support is almost completely disabled for
	  machines with more than one CPU.

	  In order to use APM, you will need supporting software. For location
1740
	  and more information, read <file:Documentation/power/pm.txt> and the
1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784
	  Battery Powered Linux mini-HOWTO, available from
	  <http://www.tldp.org/docs.html#howto>.

	  This driver does not spin down disk drives (see the hdparm(8)
	  manpage ("man 8 hdparm") for that), and it doesn't turn off
	  VESA-compliant "green" monitors.

	  This driver does not support the TI 4000M TravelMate and the ACER
	  486/DX4/75 because they don't have compliant BIOSes. Many "green"
	  desktop machines also don't have compliant BIOSes, and this driver
	  may cause those machines to panic during the boot phase.

	  Generally, if you don't have a battery in your machine, there isn't
	  much point in using this driver and you should say N. If you get
	  random kernel OOPSes or reboots that don't seem to be related to
	  anything, try disabling/enabling this option (or disabling/enabling
	  APM in your BIOS).

	  Some other things you should try when experiencing seemingly random,
	  "weird" problems:

	  1) make sure that you have enough swap space and that it is
	  enabled.
	  2) pass the "no-hlt" option to the kernel
	  3) switch on floating point emulation in the kernel and pass
	  the "no387" option to the kernel
	  4) pass the "floppy=nodma" option to the kernel
	  5) pass the "mem=4M" option to the kernel (thereby disabling
	  all but the first 4 MB of RAM)
	  6) make sure that the CPU is not over clocked.
	  7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
	  8) disable the cache from your BIOS settings
	  9) install a fan for the video card or exchange video RAM
	  10) install a better fan for the CPU
	  11) exchange RAM chips
	  12) exchange the motherboard.

	  To compile this driver as a module, choose M here: the
	  module will be called apm.

if APM

config APM_IGNORE_USER_SUSPEND
	bool "Ignore USER SUSPEND"
I
Ingo Molnar 已提交
1785
	---help---
1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808
	  This option will ignore USER SUSPEND requests. On machines with a
	  compliant APM BIOS, you want to say N. However, on the NEC Versa M
	  series notebooks, it is necessary to say Y because of a BIOS bug.

config APM_DO_ENABLE
	bool "Enable PM at boot time"
	---help---
	  Enable APM features at boot time. From page 36 of the APM BIOS
	  specification: "When disabled, the APM BIOS does not automatically
	  power manage devices, enter the Standby State, enter the Suspend
	  State, or take power saving steps in response to CPU Idle calls."
	  This driver will make CPU Idle calls when Linux is idle (unless this
	  feature is turned off -- see "Do CPU IDLE calls", below). This
	  should always save battery power, but more complicated APM features
	  will be dependent on your BIOS implementation. You may need to turn
	  this option off if your computer hangs at boot time when using APM
	  support, or if it beeps continuously instead of suspending. Turn
	  this off if you have a NEC UltraLite Versa 33/C or a Toshiba
	  T400CDT. This is off by default since most machines do fine without
	  this feature.

config APM_CPU_IDLE
	bool "Make CPU Idle calls when idle"
I
Ingo Molnar 已提交
1809
	---help---
1810 1811 1812 1813 1814 1815 1816 1817 1818 1819
	  Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
	  On some machines, this can activate improved power savings, such as
	  a slowed CPU clock rate, when the machine is idle. These idle calls
	  are made after the idle loop has run for some length of time (e.g.,
	  333 mS). On some machines, this will cause a hang at boot time or
	  whenever the CPU becomes idle. (On machines with more than one CPU,
	  this option does nothing.)

config APM_DISPLAY_BLANK
	bool "Enable console blanking using APM"
I
Ingo Molnar 已提交
1820
	---help---
1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832
	  Enable console blanking using the APM. Some laptops can use this to
	  turn off the LCD backlight when the screen blanker of the Linux
	  virtual console blanks the screen. Note that this is only used by
	  the virtual console screen blanker, and won't turn off the backlight
	  when using the X Window system. This also doesn't have anything to
	  do with your VESA-compliant power-saving monitor. Further, this
	  option doesn't work for all laptops -- it might not turn off your
	  backlight at all, or it might print a lot of errors to the console,
	  especially if you are using gpm.

config APM_ALLOW_INTS
	bool "Allow interrupts during APM BIOS calls"
I
Ingo Molnar 已提交
1833
	---help---
1834 1835 1836 1837 1838 1839 1840 1841 1842
	  Normally we disable external interrupts while we are making calls to
	  the APM BIOS as a measure to lessen the effects of a badly behaving
	  BIOS implementation.  The BIOS should reenable interrupts if it
	  needs to.  Unfortunately, some BIOSes do not -- especially those in
	  many of the newer IBM Thinkpads.  If you experience hangs when you
	  suspend, try setting this to Y.  Otherwise, say N.

endif # APM

1843
source "drivers/cpufreq/Kconfig"
1844 1845 1846

source "drivers/cpuidle/Kconfig"

A
Andy Henroid 已提交
1847 1848
source "drivers/idle/Kconfig"

1849 1850 1851 1852 1853 1854
endmenu


menu "Bus options (PCI etc.)"

config PCI
I
Ingo Molnar 已提交
1855
	bool "PCI support"
A
Adrian Bunk 已提交
1856
	default y
1857
	select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
I
Ingo Molnar 已提交
1858
	---help---
1859 1860 1861 1862 1863 1864 1865
	  Find out whether you have a PCI motherboard. PCI is the name of a
	  bus system, i.e. the way the CPU talks to the other stuff inside
	  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
	  VESA. If you have PCI, say Y, otherwise N.

choice
	prompt "PCI access mode"
1866
	depends on X86_32 && PCI
1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891
	default PCI_GOANY
	---help---
	  On PCI systems, the BIOS can be used to detect the PCI devices and
	  determine their configuration. However, some old PCI motherboards
	  have BIOS bugs and may crash if this is done. Also, some embedded
	  PCI-based systems don't have any BIOS at all. Linux can also try to
	  detect the PCI hardware directly without using the BIOS.

	  With this option, you can specify how Linux should detect the
	  PCI devices. If you choose "BIOS", the BIOS will be used,
	  if you choose "Direct", the BIOS won't be used, and if you
	  choose "MMConfig", then PCI Express MMCONFIG will be used.
	  If you choose "Any", the kernel will try MMCONFIG, then the
	  direct access method and falls back to the BIOS if that doesn't
	  work. If unsure, go with the default, which is "Any".

config PCI_GOBIOS
	bool "BIOS"

config PCI_GOMMCONFIG
	bool "MMConfig"

config PCI_GODIRECT
	bool "Direct"

1892
config PCI_GOOLPC
1893
	bool "OLPC XO-1"
1894 1895
	depends on OLPC

1896 1897 1898
config PCI_GOANY
	bool "Any"

1899 1900 1901
endchoice

config PCI_BIOS
1902
	def_bool y
1903
	depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1904 1905 1906

# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
config PCI_DIRECT
1907
	def_bool y
1908
	depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
1909 1910

config PCI_MMCONFIG
1911
	def_bool y
F
Feng Tang 已提交
1912
	depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
1913

1914
config PCI_OLPC
1915 1916
	def_bool y
	depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1917

1918 1919 1920 1921 1922
config PCI_XEN
	def_bool y
	depends on PCI && XEN
	select SWIOTLB_XEN

1923
config PCI_DOMAINS
1924
	def_bool y
1925 1926 1927 1928 1929 1930
	depends on PCI

config PCI_MMCONFIG
	bool "Support mmconfig PCI config space access"
	depends on X86_64 && PCI && ACPI

1931
config PCI_CNB20LE_QUIRK
1932
	bool "Read CNB20LE Host Bridge Windows" if EXPERT
1933 1934
	default n
	depends on PCI && EXPERIMENTAL
1935 1936 1937 1938 1939
	help
	  Read the PCI windows out of the CNB20LE host bridge. This allows
	  PCI hotplug to work on systems with the CNB20LE chipset which do
	  not have ACPI.

1940 1941 1942 1943 1944
	  There's no public spec for this chipset, and this functionality
	  is known to be incomplete.

	  You should say N unless you know you need this.

1945 1946
config DMAR
	bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1947
	depends on PCI_MSI && ACPI && EXPERIMENTAL
1948 1949 1950 1951 1952 1953 1954
	help
	  DMA remapping (DMAR) devices support enables independent address
	  translations for Direct Memory Access (DMA) from devices.
	  These DMA remapping devices are reported via ACPI tables
	  and include PCI device scope covered by these DMA
	  remapping devices.

1955
config DMAR_DEFAULT_ON
K
Kyle McMartin 已提交
1956
	def_bool y
1957 1958 1959 1960 1961 1962 1963 1964 1965
	prompt "Enable DMA Remapping Devices by default"
	depends on DMAR
	help
	  Selecting this option will enable a DMAR device at boot time if
	  one is found. If this option is not selected, DMAR support can
	  be enabled by passing intel_iommu=on to the kernel. It is
	  recommended you say N here while the DMAR code remains
	  experimental.

1966
config DMAR_BROKEN_GFX_WA
J
Jan Beulich 已提交
1967
	bool "Workaround broken graphics drivers (going away soon)"
1968
	depends on DMAR && BROKEN
1969 1970 1971 1972 1973 1974 1975 1976
	---help---
	  Current Graphics drivers tend to use physical address
	  for DMA and avoid using DMA APIs. Setting this config
	  option permits the IOMMU driver to set a unity map for
	  all the OS-visible memory. Hence the driver can continue
	  to use physical addresses for DMA, at least until this
	  option is removed in the 2.6.32 kernel.

1977
config DMAR_FLOPPY_WA
1978
	def_bool y
1979
	depends on DMAR
I
Ingo Molnar 已提交
1980
	---help---
1981
	  Floppy disk drivers are known to bypass DMA API calls
I
Ingo Molnar 已提交
1982 1983
	  thereby failing to work when IOMMU is enabled. This
	  workaround will setup a 1:1 mapping for the first
1984
	  16MiB to make floppy (an ISA device) work.
1985

1986 1987 1988
config INTR_REMAP
	bool "Support for Interrupt Remapping (EXPERIMENTAL)"
	depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
I
Ingo Molnar 已提交
1989 1990 1991 1992
	---help---
	  Supports Interrupt remapping for IO-APIC and MSI devices.
	  To use x2apic mode in the CPU's which support x2APIC enhancements or
	  to support platforms with CPU's having > 8 bit APIC ID, say Y.
1993

1994 1995 1996 1997
source "drivers/pci/pcie/Kconfig"

source "drivers/pci/Kconfig"

1998
# x86_64 have no ISA slots, but can have ISA-style DMA.
1999
config ISA_DMA_API
2000 2001 2002 2003 2004
	bool "ISA-style DMA support" if (X86_64 && EXPERT)
	default y
	help
	  Enables ISA-style DMA support for devices requiring such controllers.
	  If unsure, say Y.
2005 2006 2007 2008 2009

if X86_32

config ISA
	bool "ISA support"
I
Ingo Molnar 已提交
2010
	---help---
2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035
	  Find out whether you have ISA slots on your motherboard.  ISA is the
	  name of a bus system, i.e. the way the CPU talks to the other stuff
	  inside your box.  Other bus systems are PCI, EISA, MicroChannel
	  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
	  newer boards don't support it.  If you have ISA, say Y, otherwise N.

config EISA
	bool "EISA support"
	depends on ISA
	---help---
	  The Extended Industry Standard Architecture (EISA) bus was
	  developed as an open alternative to the IBM MicroChannel bus.

	  The EISA bus provided some of the features of the IBM MicroChannel
	  bus while maintaining backward compatibility with cards made for
	  the older ISA bus.  The EISA bus saw limited use between 1988 and
	  1995 when it was made obsolete by the PCI bus.

	  Say Y here if you are building a kernel for an EISA-based machine.

	  Otherwise, say N.

source "drivers/eisa/Kconfig"

config MCA
2036
	bool "MCA support"
I
Ingo Molnar 已提交
2037
	---help---
2038 2039 2040 2041 2042 2043 2044 2045 2046
	  MicroChannel Architecture is found in some IBM PS/2 machines and
	  laptops.  It is a bus system similar to PCI or ISA. See
	  <file:Documentation/mca.txt> (and especially the web page given
	  there) before attempting to build an MCA bus kernel.

source "drivers/mca/Kconfig"

config SCx200
	tristate "NatSemi SCx200 support"
I
Ingo Molnar 已提交
2047
	---help---
2048 2049 2050 2051 2052 2053 2054 2055 2056
	  This provides basic support for National Semiconductor's
	  (now AMD's) Geode processors.  The driver probes for the
	  PCI-IDs of several on-chip devices, so its a good dependency
	  for other scx200_* drivers.

	  If compiled as a module, the driver is named scx200.

config SCx200HR_TIMER
	tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
J
John Stultz 已提交
2057
	depends on SCx200
2058
	default y
I
Ingo Molnar 已提交
2059
	---help---
2060 2061 2062 2063 2064 2065
	  This driver provides a clocksource built upon the on-chip
	  27MHz high-resolution timer.  Its also a workaround for
	  NSC Geode SC-1100's buggy TSC, which loses time when the
	  processor goes idle (as is done by the scheduler).  The
	  other workaround is idle=poll boot option.

2066 2067
config OLPC
	bool "One Laptop Per Child support"
2068
	depends on !X86_PAE
2069
	select GPIOLIB
2070
	select OF
2071
	select OF_PROMTREE
I
Ingo Molnar 已提交
2072
	---help---
2073 2074 2075
	  Add support for detecting the unique features of the OLPC
	  XO hardware.

2076 2077
config OLPC_XO1_PM
	bool "OLPC XO-1 Power Management"
2078
	depends on OLPC && MFD_CS5535 && PM_SLEEP
2079
	select MFD_CORE
2080
	---help---
2081
	  Add support for poweroff and suspend of the OLPC XO-1 laptop.
2082

2083 2084
config OLPC_XO1_SCI
	bool "OLPC XO-1 SCI extras"
2085
	depends on OLPC && OLPC_XO1_PM && POWER_SUPPLY
2086 2087 2088 2089
	select GPIO_CS5535
	select MFD_CORE
	---help---
	  Add support for SCI-based features of the OLPC XO-1 laptop:
2090
	   - EC-driven system wakeups
2091
	   - Power button
2092
	   - Ebook switch
2093
	   - Lid switch
2094 2095
	   - AC adapter status updates
	   - Battery status updates
2096

2097 2098
endif # X86_32

2099
config AMD_NB
2100
	def_bool y
2101
	depends on CPU_SUP_AMD && PCI
2102 2103 2104 2105 2106

source "drivers/pcmcia/Kconfig"

source "drivers/pci/hotplug/Kconfig"

2107 2108 2109 2110 2111 2112 2113 2114 2115 2116
config RAPIDIO
	bool "RapidIO support"
	depends on PCI
	default n
	help
	  If you say Y here, the kernel will include drivers and
	  infrastructure code to support RapidIO interconnect devices.

source "drivers/rapidio/Kconfig"

2117 2118 2119 2120 2121 2122 2123 2124 2125 2126
endmenu


menu "Executable file formats / Emulations"

source "fs/Kconfig.binfmt"

config IA32_EMULATION
	bool "IA32 Emulation"
	depends on X86_64
R
Roland McGrath 已提交
2127
	select COMPAT_BINFMT_ELF
I
Ingo Molnar 已提交
2128
	---help---
2129 2130 2131 2132 2133
	  Include code to run 32-bit programs under a 64-bit kernel. You should
	  likely turn this on, unless you're 100% sure that you don't have any
	  32-bit programs left.

config IA32_AOUT
I
Ingo Molnar 已提交
2134 2135 2136 2137
	tristate "IA32 a.out support"
	depends on IA32_EMULATION
	---help---
	  Support old a.out binaries in the 32bit emulation.
2138 2139

config COMPAT
2140
	def_bool y
2141 2142 2143 2144 2145 2146 2147
	depends on IA32_EMULATION

config COMPAT_FOR_U64_ALIGNMENT
	def_bool COMPAT
	depends on X86_64

config SYSVIPC_COMPAT
2148
	def_bool y
2149
	depends on COMPAT && SYSVIPC
2150

2151 2152 2153 2154 2155
config KEYS_COMPAT
	bool
	depends on COMPAT && KEYS
	default y

2156 2157 2158
endmenu


K
Keith Packard 已提交
2159 2160 2161 2162
config HAVE_ATOMIC_IOMAP
	def_bool y
	depends on X86_32

2163 2164 2165 2166
config HAVE_TEXT_POKE_SMP
	bool
	select STOP_MACHINE if SMP

2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180
source "net/Kconfig"

source "drivers/Kconfig"

source "drivers/firmware/Kconfig"

source "fs/Kconfig"

source "arch/x86/Kconfig.debug"

source "security/Kconfig"

source "crypto/Kconfig"

2181 2182
source "arch/x86/kvm/Kconfig"

2183
source "lib/Kconfig"