Kconfig 21.7 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
#
# For a description of the syntax of this configuration file,
# see Documentation/kbuild/kconfig-language.txt.
#
# Note: ISA is disabled and will hopefully never be enabled.
# If you managed to buy an ISA x86-64 box you'll have to fix all the
# ISA drivers you need yourself.
#

mainmenu "Linux Kernel Configuration"

config X86_64
	bool
	default y
	help
	  Port to the x86-64 architecture. x86-64 is a 64-bit extension to the
	  classical 32-bit x86 architecture. For details see
	  <http://www.x86-64.org/>.

config 64BIT
	def_bool y

config X86
	bool
	default y

27 28 29 30
config GENERIC_TIME
	bool
	default y

31 32 33 34
config GENERIC_TIME_VSYSCALL
	bool
	default y

35 36 37 38
config GENERIC_CMOS_UPDATE
	bool
	default y

39 40 41 42
config CLOCKSOURCE_WATCHDOG
	bool
	default y

T
Thomas Gleixner 已提交
43 44 45 46 47
config GENERIC_CLOCKEVENTS
	bool
	default y

config GENERIC_CLOCKEVENTS_BROADCAST
48 49 50
	bool
	default y

51 52 53 54
config ZONE_DMA32
	bool
	default y

I
Ingo Molnar 已提交
55 56 57 58
config LOCKDEP_SUPPORT
	bool
	default y

59 60 61 62
config STACKTRACE_SUPPORT
	bool
	default y

63 64 65 66
config SEMAPHORE_SLEEPERS
	bool
	default y

L
Linus Torvalds 已提交
67 68 69 70
config MMU
	bool
	default y

71 72 73 74
config ZONE_DMA
	bool
	default y

L
Linus Torvalds 已提交
75 76 77 78 79 80 81 82 83 84 85 86 87
config ISA
	bool

config SBUS
	bool

config RWSEM_GENERIC_SPINLOCK
	bool
	default y

config RWSEM_XCHGADD_ALGORITHM
	bool

88 89 90 91
config GENERIC_HWEIGHT
	bool
	default y

L
Linus Torvalds 已提交
92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111
config GENERIC_CALIBRATE_DELAY
	bool
	default y

config X86_CMPXCHG
	bool
	default y

config EARLY_PRINTK
	bool
	default y

config GENERIC_ISA_DMA
	bool
	default y

config GENERIC_IOMAP
	bool
	default y

112 113 114 115
config ARCH_MAY_HAVE_PC_FDC
	bool
	default y

116 117 118
config ARCH_POPULATES_NODE_MAP
	def_bool y

119 120 121 122
config DMI
	bool
	default y

123 124 125 126
config AUDIT_ARCH
	bool
	default y

127 128 129 130 131
config GENERIC_BUG
	bool
	default y
	depends on BUG

132 133 134 135 136 137 138 139
config ARCH_HAS_ILOG2_U32
	bool
	default n

config ARCH_HAS_ILOG2_U64
	bool
	default n

L
Linus Torvalds 已提交
140 141 142 143 144
source "init/Kconfig"


menu "Processor type and features"

145 146
source "kernel/time/Kconfig"

147 148 149 150 151 152 153 154 155 156 157
choice
	prompt "Subarchitecture Type"
	default X86_PC

config X86_PC
	bool "PC-compatible"
	help
	  Choose this option if your computer is a standard PC or compatible.

config X86_VSMP
	bool "Support for ScaleMP vSMP"
158
	depends on PCI
159 160 161 162 163 164 165
	 help
	  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.

endchoice

L
Linus Torvalds 已提交
166 167
choice
	prompt "Processor family"
168
	default GENERIC_CPU
L
Linus Torvalds 已提交
169 170 171 172 173 174 175

config MK8
	bool "AMD-Opteron/Athlon64"
	help
	  Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.

config MPSC
176
       bool "Intel P4 / older Netburst based Xeon"
L
Linus Torvalds 已提交
177
       help
178 179
	  Optimize for Intel Pentium 4 and older Nocona/Dempsey Xeon CPUs
	  with Intel Extended Memory 64 Technology(EM64T). For details see
L
Linus Torvalds 已提交
180
	  <http://www.intel.com/technology/64bitextensions/>.
N
Nicolas Kaiser 已提交
181 182
	  Note that the latest Xeons (Xeon 51xx and 53xx) are not based on the
          Netburst core and shouldn't use this option. You can distinguish them
183
	  using the cpu family field
N
Nicolas Kaiser 已提交
184 185
	  in /proc/cpuinfo. Family 15 is an older Xeon, Family 6 a newer one
	  (this rule only applies to systems that support EM64T)
186 187 188 189 190

config MCORE2
	bool "Intel Core2 / newer Xeon"
	help
	  Optimize for Intel Core2 and newer Xeons (51xx)
N
Nicolas Kaiser 已提交
191 192
	  You can distinguish the newer Xeons from the older ones using
	  the cpu family field in /proc/cpuinfo. 15 is an older Xeon
193 194
	  (use CONFIG_MPSC then), 6 is a newer one. This rule only
	  applies to CPUs that support EM64T.
L
Linus Torvalds 已提交
195 196 197 198 199

config GENERIC_CPU
	bool "Generic-x86-64"
	help
	  Generic x86-64 CPU.
200
	  Run equally well on all x86-64 CPUs.
L
Linus Torvalds 已提交
201 202 203 204 205 206 207 208 209

endchoice

#
# Define implied options from the CPU selection here
#
config X86_L1_CACHE_BYTES
	int
	default "128" if GENERIC_CPU || MPSC
210
	default "64" if MK8 || MCORE2
L
Linus Torvalds 已提交
211 212 213 214

config X86_L1_CACHE_SHIFT
	int
	default "7" if GENERIC_CPU || MPSC
215
	default "6" if MK8 || MCORE2
L
Linus Torvalds 已提交
216

217 218 219 220 221
config X86_INTERNODE_CACHE_BYTES
	int
	default "4096" if X86_VSMP
	default X86_L1_CACHE_BYTES if !X86_VSMP

L
Linus Torvalds 已提交
222 223 224 225 226 227 228 229 230 231
config X86_TSC
	bool
	default y

config X86_GOOD_APIC
	bool
	default y

config MICROCODE
	tristate "/dev/cpu/microcode - Intel CPU microcode support"
232
	select FW_LOADER
L
Linus Torvalds 已提交
233 234 235 236 237 238 239 240 241 242 243 244 245 246 247
	---help---
	  If you say Y here the 'File systems' section, you will be
	  able to update the microcode on Intel processors. You will
	  obviously need the actual microcode binary data itself which is
	  not shipped with the Linux kernel.

	  For latest news and information on obtaining all the required
	  ingredients for this driver, check:
	  <http://www.urbanmyth.org/microcode/>.

	  To compile this driver as a module, choose M here: the
	  module will be called microcode.
	  If you use modprobe or kmod you may also want to add the line
	  'alias char-major-10-184 microcode' to your /etc/modules.conf file.

248 249 250 251 252
config MICROCODE_OLD_INTERFACE
	bool
	depends on MICROCODE
	default y

L
Linus Torvalds 已提交
253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341
config X86_MSR
	tristate "/dev/cpu/*/msr - Model-specific register support"
	help
	  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"
	help
	  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.

config X86_HT
	bool
	depends on SMP && !MK8
	default y

config MATH_EMULATION
	bool

config MCA
	bool

config EISA
	bool

config X86_IO_APIC
	bool
	default y

config X86_LOCAL_APIC
	bool
	default y

config MTRR
	bool "MTRR (Memory Type Range Register) support"
	---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.

	  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.

	  Just say Y here, all x86-64 machines support MTRRs.

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

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.

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

config SCHED_SMT
	bool "SMT (Hyperthreading) scheduler support"
	depends on SMP
	default n
	help
	  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.

342 343 344 345 346 347 348 349 350
config SCHED_MC
	bool "Multi-core scheduler support"
	depends on SMP
	default y
	help
	  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.

351 352
source "kernel/Kconfig.preempt"

353 354
config NUMA
       bool "Non Uniform Memory Access (NUMA) Support"
L
Linus Torvalds 已提交
355 356
       depends on SMP
       help
357 358 359 360 361 362 363 364 365
	 Enable NUMA (Non Uniform Memory Access) support. 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.
	 This code is recommended on all multiprocessor Opteron systems.
	 If the system is EM64T, you should say N unless your system is EM64T 
	 NUMA. 

config K8_NUMA
       bool "Old style AMD Opteron NUMA detection"
366
       depends on NUMA && PCI
367 368 369 370
       default y
       help
	 Enable K8 NUMA node topology detection.  You should say Y here if
	 you have a multi processor AMD K8 system. This uses an old
M
Matt LaPlante 已提交
371
	 method to read the NUMA configuration directly from the builtin
372 373 374
	 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
	 instead, which also takes priority if both are compiled in.   

Y
Yasunori Goto 已提交
375 376 377 378 379
config NODES_SHIFT
	int
	default "6"
	depends on NEED_MULTIPLE_NODES

380 381 382 383 384 385
# Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.

config X86_64_ACPI_NUMA
       bool "ACPI NUMA detection"
       depends on NUMA
       select ACPI 
386
	select PCI
387 388 389 390
       select ACPI_NUMA
       default y
       help
	 Enable ACPI SRAT based node topology detection.
L
Linus Torvalds 已提交
391 392

config NUMA_EMU
393 394
	bool "NUMA emulation"
	depends on NUMA
L
Linus Torvalds 已提交
395 396 397 398 399
	help
	  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.

400
config ARCH_DISCONTIGMEM_ENABLE
L
Linus Torvalds 已提交
401 402 403 404
       bool
       depends on NUMA
       default y

405 406 407 408 409 410
config ARCH_DISCONTIGMEM_DEFAULT
	def_bool y
	depends on NUMA

config ARCH_SPARSEMEM_ENABLE
	def_bool y
411
	depends on (NUMA || EXPERIMENTAL)
412
	select SPARSEMEM_VMEMMAP_ENABLE
413 414 415 416

config ARCH_MEMORY_PROBE
	def_bool y
	depends on MEMORY_HOTPLUG
417 418 419 420 421

config ARCH_FLATMEM_ENABLE
	def_bool y
	depends on !NUMA

422 423
source "mm/Kconfig"

424 425 426 427
config MEMORY_HOTPLUG_RESERVE
	def_bool y
	depends on (MEMORY_HOTPLUG && DISCONTIGMEM)

428 429
config HAVE_ARCH_EARLY_PFN_TO_NID
	def_bool y
430
	depends on NUMA
431

432 433 434 435
config OUT_OF_LINE_PFN_TO_PAGE
	def_bool y
	depends on DISCONTIGMEM

L
Linus Torvalds 已提交
436
config NR_CPUS
437
	int "Maximum number of CPUs (2-255)"
438
	range 2 255
L
Linus Torvalds 已提交
439 440 441 442
	depends on SMP
	default "8"
	help
	  This allows you to specify the maximum number of CPUs which this
443
	  kernel will support. Current maximum is 255 CPUs due to
L
Linus Torvalds 已提交
444 445 446 447 448
	  APIC addressing limits. Less depending on the hardware.

	  This is purely to save memory - each supported CPU requires
	  memory in the static kernel configuration.

449 450 451 452
config PHYSICAL_ALIGN
	hex
	default "0x200000"

A
Ashok Raj 已提交
453
config HOTPLUG_CPU
454
	bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
A
Ashok Raj 已提交
455 456 457 458
	depends on SMP && HOTPLUG && EXPERIMENTAL
	help
		Say Y here to experiment with turning CPUs off and on.  CPUs
		can be controlled through /sys/devices/system/cpu/cpu#.
459 460 461 462
		This is also required for suspend/hibernation on SMP systems.

		Say N if you want to disable CPU hotplug and don't need to
		suspend.
A
Ashok Raj 已提交
463

464 465
config ARCH_ENABLE_MEMORY_HOTPLUG
	def_bool y
A
Ashok Raj 已提交
466

L
Linus Torvalds 已提交
467 468 469 470 471 472 473 474 475
config HPET_TIMER
	bool
	default y
	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.  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
R
Randy Dunlap 已提交
476
	  <http://www.intel.com/hardwaredesign/hpetspec.htm>.
L
Linus Torvalds 已提交
477 478 479 480 481

config HPET_EMULATE_RTC
	bool "Provide RTC interrupt"
	depends on HPET_TIMER && RTC=y

482 483 484 485
# Mark as embedded because too many people got it wrong.
# The code disables itself when not needed.
config IOMMU
	bool "IOMMU support" if EMBEDDED
486
	default y
487
	select SWIOTLB
488
	select AGP
L
Linus Torvalds 已提交
489 490
	depends on PCI
	help
491 492 493 494
	  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
495 496
	  based hardware IOMMU and a software bounce buffer based IOMMU used
	  on Intel systems and as fallback.
497 498 499 500
	  The code is only active when needed (enough memory and limited
	  device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
	  too.

501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518
config CALGARY_IOMMU
	bool "IBM Calgary IOMMU support"
	select SWIOTLB
	depends on PCI && EXPERIMENTAL
	help
	  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.

519 520
config CALGARY_IOMMU_ENABLED_BY_DEFAULT
	bool "Should Calgary be enabled by default?"
521
	default y
522 523
	depends on CALGARY_IOMMU
	help
524
	  Should Calgary be enabled by default? if you choose 'y', Calgary
525 526 527
	  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.
528
	  If unsure, say Y.
529

530
# need this always selected by IOMMU for the VIA workaround
L
Linus Torvalds 已提交
531 532
config SWIOTLB
	bool
533 534 535 536 537 538
	help
	  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.
L
Linus Torvalds 已提交
539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556

config X86_MCE
	bool "Machine check support" if EMBEDDED
	default y
	help
	   Include a machine check error handler to report hardware errors.
	   This version will require the mcelog utility to decode some
	   machine check error logs. See
	   ftp://ftp.x86-64.org/pub/linux/tools/mcelog

config X86_MCE_INTEL
	bool "Intel MCE features"
	depends on X86_MCE && X86_LOCAL_APIC
	default y
	help
	   Additional support for intel specific MCE features such as
	   the thermal monitor.

557 558 559 560 561 562 563 564
config X86_MCE_AMD
	bool "AMD MCE features"
	depends on X86_MCE && X86_LOCAL_APIC
	default y
	help
	   Additional support for AMD specific MCE features such as
	   the DRAM Error Threshold.

565
config KEXEC
566
	bool "kexec system call"
567 568 569
	help
	  kexec is a system call that implements the ability to shutdown your
	  current kernel, and to start another kernel.  It is like a reboot
570
	  but it is independent of the system firmware.   And like a reboot
571 572
	  you can start any kernel with it, not just Linux.

573
	  The name comes from the similarity to the exec system call.
574 575 576 577 578 579 580

	  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.

581 582 583 584
config CRASH_DUMP
	bool "kernel crash dumps (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	help
585 586 587 588 589
	  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
590
	  to a memory address not used by the main kernel or BIOS using
591 592 593
	  PHYSICAL_START, or it must be built as a relocatable image
	  (CONFIG_RELOCATABLE=y).
	  For more details see Documentation/kdump/kdump.txt
594

595
config RELOCATABLE
596
	bool "Build a relocatable kernel (EXPERIMENTAL)"
597 598 599 600 601 602 603 604 605 606
	depends on EXPERIMENTAL
	help
	  Builds a relocatable kernel. This enables loading and running
	  a kernel binary from a different physical address than it has
	  been compiled for.

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

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

611 612
config PHYSICAL_START
	hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
A
Andi Kleen 已提交
613
	default "0x200000"
614
	help
615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635
	  This gives the physical address where the kernel is loaded. It
	  should be aligned to 2MB boundary.

	  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.

	  So if you are using bzImage for capturing the crash dump, leave
	  the value here unchanged to 0x200000 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 (Typically 16MB
	  0x1000000). In other words, it can be set based on the "X" value as
636 637 638 639 640
	  specified in the "crashkernel=YM@XM" command line boot parameter
	  passed to the panic-ed kernel. Typically this parameter is set as
	  crashkernel=64M@16M. Please take a look at
	  Documentation/kdump/kdump.txt for more details about crash dumps.

641 642 643 644
	  Usage of bzImage for capturing the crash dump is advantageous as
	  one does not have to build two kernels. Same kernel can be used
	  as production kernel and capture kernel.

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

L
Linus Torvalds 已提交
647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663
config SECCOMP
	bool "Enable seccomp to safely compute untrusted bytecode"
	depends on PROC_FS
	default y
	help
	  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
	  enabled via /proc/<pid>/seccomp, it cannot be disabled
	  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.

664
config CC_STACKPROTECTOR
665
	bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687
	depends on EXPERIMENTAL
	help
         This option turns on the -fstack-protector GCC feature. This
	  feature puts, at the beginning of critical functions, a canary
	  value on the stack just before the return address, and validates
	  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
	  detected and for those versions, this configuration option is ignored.

config CC_STACKPROTECTOR_ALL
	bool "Use stack-protector for all functions"
	depends on CC_STACKPROTECTOR
	help
	  Normally, GCC only inserts the canary value protection for
	  functions that use large-ish on-stack buffers. By enabling
	  this option, GCC will be asked to do this for ALL functions.

688 689
source kernel/Kconfig.hz

690 691
config K8_NB
	def_bool y
692
	depends on AGP_AMD64 || IOMMU || (PCI && NUMA)
693

L
Linus Torvalds 已提交
694 695 696 697 698 699 700 701 702 703 704 705 706
endmenu

#
# Use the generic interrupt handling code in kernel/irq/:
#
config GENERIC_HARDIRQS
	bool
	default y

config GENERIC_IRQ_PROBE
	bool
	default y

A
Al Viro 已提交
707 708 709 710 711
# we have no ISA slots, but we do have ISA-style DMA.
config ISA_DMA_API
	bool
	default y

712 713 714 715 716
config GENERIC_PENDING_IRQ
	bool
	depends on GENERIC_HARDIRQS && SMP
	default y

L
Linus Torvalds 已提交
717 718 719 720 721 722
menu "Power management options"

source kernel/power/Kconfig

source "drivers/acpi/Kconfig"

T
Thomas Gleixner 已提交
723
source "arch/x86/kernel/cpufreq/Kconfig"
L
Linus Torvalds 已提交
724 725 726 727 728 729 730

endmenu

menu "Bus options (PCI etc.)"

config PCI
	bool "PCI support"
731
	select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
L
Linus Torvalds 已提交
732 733 734 735 736 737 738 739 740

# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
config PCI_DIRECT
	bool
	depends on PCI
	default y

config PCI_MMCONFIG
	bool "Support mmconfig PCI config space access"
741
	depends on PCI && ACPI
L
Linus Torvalds 已提交
742

743 744 745 746 747
config PCI_DOMAINS
	bool
	depends on PCI
	default y

L
Linus Torvalds 已提交
748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770
source "drivers/pci/pcie/Kconfig"

source "drivers/pci/Kconfig"

source "drivers/pcmcia/Kconfig"

source "drivers/pci/hotplug/Kconfig"

endmenu


menu "Executable file formats / Emulations"

source "fs/Kconfig.binfmt"

config IA32_EMULATION
	bool "IA32 Emulation"
	help
	  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
771
       tristate "IA32 a.out support"
L
Linus Torvalds 已提交
772 773 774 775 776 777 778 779 780
       depends on IA32_EMULATION
       help
         Support old a.out binaries in the 32bit emulation.

config COMPAT
	bool
	depends on IA32_EMULATION
	default y

781 782 783
config COMPAT_FOR_U64_ALIGNMENT
	def_bool COMPAT

L
Linus Torvalds 已提交
784 785 786 787 788 789 790
config SYSVIPC_COMPAT
	bool
	depends on COMPAT && SYSVIPC
	default y

endmenu

791 792
source "net/Kconfig"

L
Linus Torvalds 已提交
793 794 795 796 797 798
source drivers/Kconfig

source "drivers/firmware/Kconfig"

source fs/Kconfig

799 800
menu "Instrumentation Support"

T
Thomas Gleixner 已提交
801
source "arch/x86/oprofile/Kconfig"
L
Linus Torvalds 已提交
802

803
config KPROBES
804 805
	bool "Kprobes"
	depends on KALLSYMS && MODULES
806 807 808 809 810 811 812 813
	help
	  Kprobes allows you to trap at almost any kernel address and
	  execute a callback function.  register_kprobe() establishes
	  a probepoint and specifies the callback.  Kprobes is useful
	  for kernel debugging, non-intrusive instrumentation and testing.
	  If in doubt, say "N".
endmenu

L
Linus Torvalds 已提交
814 815 816 817 818 819 820
source "arch/x86_64/Kconfig.debug"

source "security/Kconfig"

source "crypto/Kconfig"

source "lib/Kconfig"