Kconfig 52 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601160216031604160516061607
  1. # x86 configuration
  2. mainmenu "Linux Kernel Configuration for x86"
  3. # Select 32 or 64 bit
  4. config 64BIT
  5. bool "64-bit kernel" if ARCH = "x86"
  6. default ARCH = "x86_64"
  7. help
  8. Say yes to build a 64-bit kernel - formerly known as x86_64
  9. Say no to build a 32-bit kernel - formerly known as i386
  10. config X86_32
  11. def_bool !64BIT
  12. config X86_64
  13. def_bool 64BIT
  14. ### Arch settings
  15. config X86
  16. def_bool y
  17. config GENERIC_LOCKBREAK
  18. def_bool n
  19. config GENERIC_TIME
  20. def_bool y
  21. config GENERIC_CMOS_UPDATE
  22. def_bool y
  23. config CLOCKSOURCE_WATCHDOG
  24. def_bool y
  25. config GENERIC_CLOCKEVENTS
  26. def_bool y
  27. config GENERIC_CLOCKEVENTS_BROADCAST
  28. def_bool y
  29. depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
  30. config LOCKDEP_SUPPORT
  31. def_bool y
  32. config STACKTRACE_SUPPORT
  33. def_bool y
  34. config HAVE_LATENCYTOP_SUPPORT
  35. def_bool y
  36. config SEMAPHORE_SLEEPERS
  37. def_bool y
  38. config MMU
  39. def_bool y
  40. config ZONE_DMA
  41. def_bool y
  42. config QUICKLIST
  43. def_bool X86_32
  44. config SBUS
  45. bool
  46. config GENERIC_ISA_DMA
  47. def_bool y
  48. config GENERIC_IOMAP
  49. def_bool y
  50. config GENERIC_BUG
  51. def_bool y
  52. depends on BUG
  53. config GENERIC_HWEIGHT
  54. def_bool y
  55. config GENERIC_GPIO
  56. def_bool n
  57. config ARCH_MAY_HAVE_PC_FDC
  58. def_bool y
  59. config DMI
  60. def_bool y
  61. config RWSEM_GENERIC_SPINLOCK
  62. def_bool !X86_XADD
  63. config RWSEM_XCHGADD_ALGORITHM
  64. def_bool X86_XADD
  65. config ARCH_HAS_ILOG2_U32
  66. def_bool n
  67. config ARCH_HAS_ILOG2_U64
  68. def_bool n
  69. config GENERIC_CALIBRATE_DELAY
  70. def_bool y
  71. config GENERIC_TIME_VSYSCALL
  72. bool
  73. default X86_64
  74. config HAVE_SETUP_PER_CPU_AREA
  75. def_bool X86_64
  76. config ARCH_SUPPORTS_OPROFILE
  77. bool
  78. default y
  79. select HAVE_KVM
  80. config ZONE_DMA32
  81. bool
  82. default X86_64
  83. config ARCH_POPULATES_NODE_MAP
  84. def_bool y
  85. config AUDIT_ARCH
  86. bool
  87. default X86_64
  88. # Use the generic interrupt handling code in kernel/irq/:
  89. config GENERIC_HARDIRQS
  90. bool
  91. default y
  92. config GENERIC_IRQ_PROBE
  93. bool
  94. default y
  95. config GENERIC_PENDING_IRQ
  96. bool
  97. depends on GENERIC_HARDIRQS && SMP
  98. default y
  99. config X86_SMP
  100. bool
  101. depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
  102. default y
  103. config X86_32_SMP
  104. def_bool y
  105. depends on X86_32 && SMP
  106. config X86_64_SMP
  107. def_bool y
  108. depends on X86_64 && SMP
  109. config X86_HT
  110. bool
  111. depends on SMP
  112. depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
  113. default y
  114. config X86_BIOS_REBOOT
  115. bool
  116. depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
  117. default y
  118. config X86_TRAMPOLINE
  119. bool
  120. depends on X86_SMP || (X86_VOYAGER && SMP)
  121. default y
  122. config KTIME_SCALAR
  123. def_bool X86_32
  124. source "init/Kconfig"
  125. menu "Processor type and features"
  126. source "kernel/time/Kconfig"
  127. config SMP
  128. bool "Symmetric multi-processing support"
  129. ---help---
  130. This enables support for systems with more than one CPU. If you have
  131. a system with only one CPU, like most personal computers, say N. If
  132. you have a system with more than one CPU, say Y.
  133. If you say N here, the kernel will run on single and multiprocessor
  134. machines, but will use only one CPU of a multiprocessor machine. If
  135. you say Y here, the kernel will run on many, but not all,
  136. singleprocessor machines. On a singleprocessor machine, the kernel
  137. will run faster if you say N here.
  138. Note that if you say Y here and choose architecture "586" or
  139. "Pentium" under "Processor family", the kernel will not work on 486
  140. architectures. Similarly, multiprocessor kernels for the "PPro"
  141. architecture may not work on all Pentium based boards.
  142. People using multiprocessor machines who say Y here should also say
  143. Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
  144. Management" code will be disabled if you say Y here.
  145. See also the <file:Documentation/smp.txt>,
  146. <file:Documentation/i386/IO-APIC.txt>,
  147. <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
  148. <http://www.tldp.org/docs.html#howto>.
  149. If you don't know what to do here, say N.
  150. choice
  151. prompt "Subarchitecture Type"
  152. default X86_PC
  153. config X86_PC
  154. bool "PC-compatible"
  155. help
  156. Choose this option if your computer is a standard PC or compatible.
  157. config X86_ELAN
  158. bool "AMD Elan"
  159. depends on X86_32
  160. help
  161. Select this for an AMD Elan processor.
  162. Do not use this option for K6/Athlon/Opteron processors!
  163. If unsure, choose "PC-compatible" instead.
  164. config X86_VOYAGER
  165. bool "Voyager (NCR)"
  166. depends on X86_32
  167. select SMP if !BROKEN
  168. help
  169. Voyager is an MCA-based 32-way capable SMP architecture proprietary
  170. to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
  171. *** WARNING ***
  172. If you do not specifically know you have a Voyager based machine,
  173. say N here, otherwise the kernel you build will not be bootable.
  174. config X86_NUMAQ
  175. bool "NUMAQ (IBM/Sequent)"
  176. select SMP
  177. select NUMA
  178. depends on X86_32
  179. help
  180. This option is used for getting Linux to run on a (IBM/Sequent) NUMA
  181. multiquad box. This changes the way that processors are bootstrapped,
  182. and uses Clustered Logical APIC addressing mode instead of Flat Logical.
  183. You will need a new lynxer.elf file to flash your firmware with - send
  184. email to <Martin.Bligh@us.ibm.com>.
  185. config X86_SUMMIT
  186. bool "Summit/EXA (IBM x440)"
  187. depends on X86_32 && SMP
  188. help
  189. This option is needed for IBM systems that use the Summit/EXA chipset.
  190. In particular, it is needed for the x440.
  191. If you don't have one of these computers, you should say N here.
  192. If you want to build a NUMA kernel, you must select ACPI.
  193. config X86_BIGSMP
  194. bool "Support for other sub-arch SMP systems with more than 8 CPUs"
  195. depends on X86_32 && SMP
  196. help
  197. This option is needed for the systems that have more than 8 CPUs
  198. and if the system is not of any sub-arch type above.
  199. If you don't have such a system, you should say N here.
  200. config X86_VISWS
  201. bool "SGI 320/540 (Visual Workstation)"
  202. depends on X86_32
  203. help
  204. The SGI Visual Workstation series is an IA32-based workstation
  205. based on SGI systems chips with some legacy PC hardware attached.
  206. Say Y here to create a kernel to run on the SGI 320 or 540.
  207. A kernel compiled for the Visual Workstation will not run on PCs
  208. and vice versa. See <file:Documentation/sgi-visws.txt> for details.
  209. config X86_GENERICARCH
  210. bool "Generic architecture (Summit, bigsmp, ES7000, default)"
  211. depends on X86_32
  212. help
  213. This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
  214. It is intended for a generic binary kernel.
  215. If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
  216. config X86_ES7000
  217. bool "Support for Unisys ES7000 IA32 series"
  218. depends on X86_32 && SMP
  219. help
  220. Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
  221. supposed to run on an IA32-based Unisys ES7000 system.
  222. Only choose this option if you have such a system, otherwise you
  223. should say N here.
  224. config X86_RDC321X
  225. bool "RDC R-321x SoC"
  226. depends on X86_32
  227. select M486
  228. select X86_REBOOTFIXUPS
  229. select GENERIC_GPIO
  230. select LEDS_GPIO
  231. help
  232. This option is needed for RDC R-321x system-on-chip, also known
  233. as R-8610-(G).
  234. If you don't have one of these chips, you should say N here.
  235. config X86_VSMP
  236. bool "Support for ScaleMP vSMP"
  237. depends on X86_64 && PCI
  238. help
  239. Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
  240. supposed to run on these EM64T-based machines. Only choose this option
  241. if you have one of these machines.
  242. endchoice
  243. config SCHED_NO_NO_OMIT_FRAME_POINTER
  244. def_bool y
  245. prompt "Single-depth WCHAN output"
  246. depends on X86_32
  247. help
  248. Calculate simpler /proc/<PID>/wchan values. If this option
  249. is disabled then wchan values will recurse back to the
  250. caller function. This provides more accurate wchan values,
  251. at the expense of slightly more scheduling overhead.
  252. If in doubt, say "Y".
  253. menuconfig PARAVIRT_GUEST
  254. bool "Paravirtualized guest support"
  255. help
  256. Say Y here to get to see options related to running Linux under
  257. various hypervisors. This option alone does not add any kernel code.
  258. If you say N, all options in this submenu will be skipped and disabled.
  259. if PARAVIRT_GUEST
  260. source "arch/x86/xen/Kconfig"
  261. config VMI
  262. bool "VMI Guest support"
  263. select PARAVIRT
  264. depends on X86_32
  265. depends on !(X86_VISWS || X86_VOYAGER)
  266. help
  267. VMI provides a paravirtualized interface to the VMware ESX server
  268. (it could be used by other hypervisors in theory too, but is not
  269. at the moment), by linking the kernel to a GPL-ed ROM module
  270. provided by the hypervisor.
  271. source "arch/x86/lguest/Kconfig"
  272. config PARAVIRT
  273. bool "Enable paravirtualization code"
  274. depends on !(X86_VISWS || X86_VOYAGER)
  275. help
  276. This changes the kernel so it can modify itself when it is run
  277. under a hypervisor, potentially improving performance significantly
  278. over full virtualization. However, when run without a hypervisor
  279. the kernel is theoretically slower and slightly larger.
  280. endif
  281. config ACPI_SRAT
  282. def_bool y
  283. depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
  284. select ACPI_NUMA
  285. config HAVE_ARCH_PARSE_SRAT
  286. def_bool y
  287. depends on ACPI_SRAT
  288. config X86_SUMMIT_NUMA
  289. def_bool y
  290. depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
  291. config X86_CYCLONE_TIMER
  292. def_bool y
  293. depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
  294. config ES7000_CLUSTERED_APIC
  295. def_bool y
  296. depends on SMP && X86_ES7000 && MPENTIUMIII
  297. source "arch/x86/Kconfig.cpu"
  298. config HPET_TIMER
  299. def_bool X86_64
  300. prompt "HPET Timer Support" if X86_32
  301. help
  302. Use the IA-PC HPET (High Precision Event Timer) to manage
  303. time in preference to the PIT and RTC, if a HPET is
  304. present.
  305. HPET is the next generation timer replacing legacy 8254s.
  306. The HPET provides a stable time base on SMP
  307. systems, unlike the TSC, but it is more expensive to access,
  308. as it is off-chip. You can find the HPET spec at
  309. <http://www.intel.com/hardwaredesign/hpetspec.htm>.
  310. You can safely choose Y here. However, HPET will only be
  311. activated if the platform and the BIOS support this feature.
  312. Otherwise the 8254 will be used for timing services.
  313. Choose N to continue using the legacy 8254 timer.
  314. config HPET_EMULATE_RTC
  315. def_bool y
  316. depends on HPET_TIMER && (RTC=y || RTC=m)
  317. # Mark as embedded because too many people got it wrong.
  318. # The code disables itself when not needed.
  319. config GART_IOMMU
  320. bool "GART IOMMU support" if EMBEDDED
  321. default y
  322. select SWIOTLB
  323. select AGP
  324. depends on X86_64 && PCI
  325. help
  326. Support for full DMA access of devices with 32bit memory access only
  327. on systems with more than 3GB. This is usually needed for USB,
  328. sound, many IDE/SATA chipsets and some other devices.
  329. Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
  330. based hardware IOMMU and a software bounce buffer based IOMMU used
  331. on Intel systems and as fallback.
  332. The code is only active when needed (enough memory and limited
  333. device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
  334. too.
  335. config CALGARY_IOMMU
  336. bool "IBM Calgary IOMMU support"
  337. select SWIOTLB
  338. depends on X86_64 && PCI && EXPERIMENTAL
  339. help
  340. Support for hardware IOMMUs in IBM's xSeries x366 and x460
  341. systems. Needed to run systems with more than 3GB of memory
  342. properly with 32-bit PCI devices that do not support DAC
  343. (Double Address Cycle). Calgary also supports bus level
  344. isolation, where all DMAs pass through the IOMMU. This
  345. prevents them from going anywhere except their intended
  346. destination. This catches hard-to-find kernel bugs and
  347. mis-behaving drivers and devices that do not use the DMA-API
  348. properly to set up their DMA buffers. The IOMMU can be
  349. turned off at boot time with the iommu=off parameter.
  350. Normally the kernel will make the right choice by itself.
  351. If unsure, say Y.
  352. config CALGARY_IOMMU_ENABLED_BY_DEFAULT
  353. def_bool y
  354. prompt "Should Calgary be enabled by default?"
  355. depends on CALGARY_IOMMU
  356. help
  357. Should Calgary be enabled by default? if you choose 'y', Calgary
  358. will be used (if it exists). If you choose 'n', Calgary will not be
  359. used even if it exists. If you choose 'n' and would like to use
  360. Calgary anyway, pass 'iommu=calgary' on the kernel command line.
  361. If unsure, say Y.
  362. # need this always selected by IOMMU for the VIA workaround
  363. config SWIOTLB
  364. bool
  365. help
  366. Support for software bounce buffers used on x86-64 systems
  367. which don't have a hardware IOMMU (e.g. the current generation
  368. of Intel's x86-64 CPUs). Using this PCI devices which can only
  369. access 32-bits of memory can be used on systems with more than
  370. 3 GB of memory. If unsure, say Y.
  371. config NR_CPUS
  372. int "Maximum number of CPUs (2-255)"
  373. range 2 255
  374. depends on SMP
  375. default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
  376. default "8"
  377. help
  378. This allows you to specify the maximum number of CPUs which this
  379. kernel will support. The maximum supported value is 255 and the
  380. minimum value which makes sense is 2.
  381. This is purely to save memory - each supported CPU adds
  382. approximately eight kilobytes to the kernel image.
  383. config SCHED_SMT
  384. bool "SMT (Hyperthreading) scheduler support"
  385. depends on (X86_64 && SMP) || (X86_32 && X86_HT)
  386. help
  387. SMT scheduler support improves the CPU scheduler's decision making
  388. when dealing with Intel Pentium 4 chips with HyperThreading at a
  389. cost of slightly increased overhead in some places. If unsure say
  390. N here.
  391. config SCHED_MC
  392. def_bool y
  393. prompt "Multi-core scheduler support"
  394. depends on (X86_64 && SMP) || (X86_32 && X86_HT)
  395. help
  396. Multi-core scheduler support improves the CPU scheduler's decision
  397. making when dealing with multi-core CPU chips at a cost of slightly
  398. increased overhead in some places. If unsure say N here.
  399. source "kernel/Kconfig.preempt"
  400. config X86_UP_APIC
  401. bool "Local APIC support on uniprocessors"
  402. depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
  403. help
  404. A local APIC (Advanced Programmable Interrupt Controller) is an
  405. integrated interrupt controller in the CPU. If you have a single-CPU
  406. system which has a processor with a local APIC, you can say Y here to
  407. enable and use it. If you say Y here even though your machine doesn't
  408. have a local APIC, then the kernel will still run with no slowdown at
  409. all. The local APIC supports CPU-generated self-interrupts (timer,
  410. performance counters), and the NMI watchdog which detects hard
  411. lockups.
  412. config X86_UP_IOAPIC
  413. bool "IO-APIC support on uniprocessors"
  414. depends on X86_UP_APIC
  415. help
  416. An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
  417. SMP-capable replacement for PC-style interrupt controllers. Most
  418. SMP systems and many recent uniprocessor systems have one.
  419. If you have a single-CPU system with an IO-APIC, you can say Y here
  420. to use it. If you say Y here even though your machine doesn't have
  421. an IO-APIC, then the kernel will still run with no slowdown at all.
  422. config X86_LOCAL_APIC
  423. def_bool y
  424. depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
  425. config X86_IO_APIC
  426. def_bool y
  427. depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
  428. config X86_VISWS_APIC
  429. def_bool y
  430. depends on X86_32 && X86_VISWS
  431. config X86_MCE
  432. bool "Machine Check Exception"
  433. depends on !X86_VOYAGER
  434. ---help---
  435. Machine Check Exception support allows the processor to notify the
  436. kernel if it detects a problem (e.g. overheating, component failure).
  437. The action the kernel takes depends on the severity of the problem,
  438. ranging from a warning message on the console, to halting the machine.
  439. Your processor must be a Pentium or newer to support this - check the
  440. flags in /proc/cpuinfo for mce. Note that some older Pentium systems
  441. have a design flaw which leads to false MCE events - hence MCE is
  442. disabled on all P5 processors, unless explicitly enabled with "mce"
  443. as a boot argument. Similarly, if MCE is built in and creates a
  444. problem on some new non-standard machine, you can boot with "nomce"
  445. to disable it. MCE support simply ignores non-MCE processors like
  446. the 386 and 486, so nearly everyone can say Y here.
  447. config X86_MCE_INTEL
  448. def_bool y
  449. prompt "Intel MCE features"
  450. depends on X86_64 && X86_MCE && X86_LOCAL_APIC
  451. help
  452. Additional support for intel specific MCE features such as
  453. the thermal monitor.
  454. config X86_MCE_AMD
  455. def_bool y
  456. prompt "AMD MCE features"
  457. depends on X86_64 && X86_MCE && X86_LOCAL_APIC
  458. help
  459. Additional support for AMD specific MCE features such as
  460. the DRAM Error Threshold.
  461. config X86_MCE_NONFATAL
  462. tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
  463. depends on X86_32 && X86_MCE
  464. help
  465. Enabling this feature starts a timer that triggers every 5 seconds which
  466. will look at the machine check registers to see if anything happened.
  467. Non-fatal problems automatically get corrected (but still logged).
  468. Disable this if you don't want to see these messages.
  469. Seeing the messages this option prints out may be indicative of dying
  470. or out-of-spec (ie, overclocked) hardware.
  471. This option only does something on certain CPUs.
  472. (AMD Athlon/Duron and Intel Pentium 4)
  473. config X86_MCE_P4THERMAL
  474. bool "check for P4 thermal throttling interrupt."
  475. depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
  476. help
  477. Enabling this feature will cause a message to be printed when the P4
  478. enters thermal throttling.
  479. config VM86
  480. bool "Enable VM86 support" if EMBEDDED
  481. default y
  482. depends on X86_32
  483. help
  484. This option is required by programs like DOSEMU to run 16-bit legacy
  485. code on X86 processors. It also may be needed by software like
  486. XFree86 to initialize some video cards via BIOS. Disabling this
  487. option saves about 6k.
  488. config TOSHIBA
  489. tristate "Toshiba Laptop support"
  490. depends on X86_32
  491. ---help---
  492. This adds a driver to safely access the System Management Mode of
  493. the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
  494. not work on models with a Phoenix BIOS. The System Management Mode
  495. is used to set the BIOS and power saving options on Toshiba portables.
  496. For information on utilities to make use of this driver see the
  497. Toshiba Linux utilities web site at:
  498. <http://www.buzzard.org.uk/toshiba/>.
  499. Say Y if you intend to run this kernel on a Toshiba portable.
  500. Say N otherwise.
  501. config I8K
  502. tristate "Dell laptop support"
  503. depends on X86_32
  504. ---help---
  505. This adds a driver to safely access the System Management Mode
  506. of the CPU on the Dell Inspiron 8000. The System Management Mode
  507. is used to read cpu temperature and cooling fan status and to
  508. control the fans on the I8K portables.
  509. This driver has been tested only on the Inspiron 8000 but it may
  510. also work with other Dell laptops. You can force loading on other
  511. models by passing the parameter `force=1' to the module. Use at
  512. your own risk.
  513. For information on utilities to make use of this driver see the
  514. I8K Linux utilities web site at:
  515. <http://people.debian.org/~dz/i8k/>
  516. Say Y if you intend to run this kernel on a Dell Inspiron 8000.
  517. Say N otherwise.
  518. config X86_REBOOTFIXUPS
  519. def_bool n
  520. prompt "Enable X86 board specific fixups for reboot"
  521. depends on X86_32 && X86
  522. ---help---
  523. This enables chipset and/or board specific fixups to be done
  524. in order to get reboot to work correctly. This is only needed on
  525. some combinations of hardware and BIOS. The symptom, for which
  526. this config is intended, is when reboot ends with a stalled/hung
  527. system.
  528. Currently, the only fixup is for the Geode machines using
  529. CS5530A and CS5536 chipsets and the RDC R-321x SoC.
  530. Say Y if you want to enable the fixup. Currently, it's safe to
  531. enable this option even if you don't need it.
  532. Say N otherwise.
  533. config MICROCODE
  534. tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
  535. select FW_LOADER
  536. ---help---
  537. If you say Y here, you will be able to update the microcode on
  538. Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
  539. Pentium III, Pentium 4, Xeon etc. You will obviously need the
  540. actual microcode binary data itself which is not shipped with the
  541. Linux kernel.
  542. For latest news and information on obtaining all the required
  543. ingredients for this driver, check:
  544. <http://www.urbanmyth.org/microcode/>.
  545. To compile this driver as a module, choose M here: the
  546. module will be called microcode.
  547. config MICROCODE_OLD_INTERFACE
  548. def_bool y
  549. depends on MICROCODE
  550. config X86_MSR
  551. tristate "/dev/cpu/*/msr - Model-specific register support"
  552. help
  553. This device gives privileged processes access to the x86
  554. Model-Specific Registers (MSRs). It is a character device with
  555. major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
  556. MSR accesses are directed to a specific CPU on multi-processor
  557. systems.
  558. config X86_CPUID
  559. tristate "/dev/cpu/*/cpuid - CPU information support"
  560. help
  561. This device gives processes access to the x86 CPUID instruction to
  562. be executed on a specific processor. It is a character device
  563. with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
  564. /dev/cpu/31/cpuid.
  565. choice
  566. prompt "High Memory Support"
  567. default HIGHMEM4G if !X86_NUMAQ
  568. default HIGHMEM64G if X86_NUMAQ
  569. depends on X86_32
  570. config NOHIGHMEM
  571. bool "off"
  572. depends on !X86_NUMAQ
  573. ---help---
  574. Linux can use up to 64 Gigabytes of physical memory on x86 systems.
  575. However, the address space of 32-bit x86 processors is only 4
  576. Gigabytes large. That means that, if you have a large amount of
  577. physical memory, not all of it can be "permanently mapped" by the
  578. kernel. The physical memory that's not permanently mapped is called
  579. "high memory".
  580. If you are compiling a kernel which will never run on a machine with
  581. more than 1 Gigabyte total physical RAM, answer "off" here (default
  582. choice and suitable for most users). This will result in a "3GB/1GB"
  583. split: 3GB are mapped so that each process sees a 3GB virtual memory
  584. space and the remaining part of the 4GB virtual memory space is used
  585. by the kernel to permanently map as much physical memory as
  586. possible.
  587. If the machine has between 1 and 4 Gigabytes physical RAM, then
  588. answer "4GB" here.
  589. If more than 4 Gigabytes is used then answer "64GB" here. This
  590. selection turns Intel PAE (Physical Address Extension) mode on.
  591. PAE implements 3-level paging on IA32 processors. PAE is fully
  592. supported by Linux, PAE mode is implemented on all recent Intel
  593. processors (Pentium Pro and better). NOTE: If you say "64GB" here,
  594. then the kernel will not boot on CPUs that don't support PAE!
  595. The actual amount of total physical memory will either be
  596. auto detected or can be forced by using a kernel command line option
  597. such as "mem=256M". (Try "man bootparam" or see the documentation of
  598. your boot loader (lilo or loadlin) about how to pass options to the
  599. kernel at boot time.)
  600. If unsure, say "off".
  601. config HIGHMEM4G
  602. bool "4GB"
  603. depends on !X86_NUMAQ
  604. help
  605. Select this if you have a 32-bit processor and between 1 and 4
  606. gigabytes of physical RAM.
  607. config HIGHMEM64G
  608. bool "64GB"
  609. depends on !M386 && !M486
  610. select X86_PAE
  611. help
  612. Select this if you have a 32-bit processor and more than 4
  613. gigabytes of physical RAM.
  614. endchoice
  615. choice
  616. depends on EXPERIMENTAL
  617. prompt "Memory split" if EMBEDDED
  618. default VMSPLIT_3G
  619. depends on X86_32
  620. help
  621. Select the desired split between kernel and user memory.
  622. If the address range available to the kernel is less than the
  623. physical memory installed, the remaining memory will be available
  624. as "high memory". Accessing high memory is a little more costly
  625. than low memory, as it needs to be mapped into the kernel first.
  626. Note that increasing the kernel address space limits the range
  627. available to user programs, making the address space there
  628. tighter. Selecting anything other than the default 3G/1G split
  629. will also likely make your kernel incompatible with binary-only
  630. kernel modules.
  631. If you are not absolutely sure what you are doing, leave this
  632. option alone!
  633. config VMSPLIT_3G
  634. bool "3G/1G user/kernel split"
  635. config VMSPLIT_3G_OPT
  636. depends on !X86_PAE
  637. bool "3G/1G user/kernel split (for full 1G low memory)"
  638. config VMSPLIT_2G
  639. bool "2G/2G user/kernel split"
  640. config VMSPLIT_2G_OPT
  641. depends on !X86_PAE
  642. bool "2G/2G user/kernel split (for full 2G low memory)"
  643. config VMSPLIT_1G
  644. bool "1G/3G user/kernel split"
  645. endchoice
  646. config PAGE_OFFSET
  647. hex
  648. default 0xB0000000 if VMSPLIT_3G_OPT
  649. default 0x80000000 if VMSPLIT_2G
  650. default 0x78000000 if VMSPLIT_2G_OPT
  651. default 0x40000000 if VMSPLIT_1G
  652. default 0xC0000000
  653. depends on X86_32
  654. config HIGHMEM
  655. def_bool y
  656. depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
  657. config X86_PAE
  658. def_bool n
  659. prompt "PAE (Physical Address Extension) Support"
  660. depends on X86_32 && !HIGHMEM4G
  661. select RESOURCES_64BIT
  662. help
  663. PAE is required for NX support, and furthermore enables
  664. larger swapspace support for non-overcommit purposes. It
  665. has the cost of more pagetable lookup overhead, and also
  666. consumes more pagetable space per process.
  667. # Common NUMA Features
  668. config NUMA
  669. bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
  670. depends on SMP
  671. depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
  672. default n if X86_PC
  673. default y if (X86_NUMAQ || X86_SUMMIT)
  674. help
  675. Enable NUMA (Non Uniform Memory Access) support.
  676. The kernel will try to allocate memory used by a CPU on the
  677. local memory controller of the CPU and add some more
  678. NUMA awareness to the kernel.
  679. For i386 this is currently highly experimental and should be only
  680. used for kernel development. It might also cause boot failures.
  681. For x86_64 this is recommended on all multiprocessor Opteron systems.
  682. If the system is EM64T, you should say N unless your system is
  683. EM64T NUMA.
  684. comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
  685. depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
  686. config K8_NUMA
  687. def_bool y
  688. prompt "Old style AMD Opteron NUMA detection"
  689. depends on X86_64 && NUMA && PCI
  690. help
  691. Enable K8 NUMA node topology detection. You should say Y here if
  692. you have a multi processor AMD K8 system. This uses an old
  693. method to read the NUMA configuration directly from the builtin
  694. Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
  695. instead, which also takes priority if both are compiled in.
  696. config X86_64_ACPI_NUMA
  697. def_bool y
  698. prompt "ACPI NUMA detection"
  699. depends on X86_64 && NUMA && ACPI && PCI
  700. select ACPI_NUMA
  701. help
  702. Enable ACPI SRAT based node topology detection.
  703. config NUMA_EMU
  704. bool "NUMA emulation"
  705. depends on X86_64 && NUMA
  706. help
  707. Enable NUMA emulation. A flat machine will be split
  708. into virtual nodes when booted with "numa=fake=N", where N is the
  709. number of nodes. This is only useful for debugging.
  710. config NODES_SHIFT
  711. int
  712. range 1 15 if X86_64
  713. default "6" if X86_64
  714. default "4" if X86_NUMAQ
  715. default "3"
  716. depends on NEED_MULTIPLE_NODES
  717. config HAVE_ARCH_BOOTMEM_NODE
  718. def_bool y
  719. depends on X86_32 && NUMA
  720. config ARCH_HAVE_MEMORY_PRESENT
  721. def_bool y
  722. depends on X86_32 && DISCONTIGMEM
  723. config NEED_NODE_MEMMAP_SIZE
  724. def_bool y
  725. depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
  726. config HAVE_ARCH_ALLOC_REMAP
  727. def_bool y
  728. depends on X86_32 && NUMA
  729. config ARCH_FLATMEM_ENABLE
  730. def_bool y
  731. depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
  732. config ARCH_DISCONTIGMEM_ENABLE
  733. def_bool y
  734. depends on NUMA && X86_32
  735. config ARCH_DISCONTIGMEM_DEFAULT
  736. def_bool y
  737. depends on NUMA && X86_32
  738. config ARCH_SPARSEMEM_DEFAULT
  739. def_bool y
  740. depends on X86_64
  741. config ARCH_SPARSEMEM_ENABLE
  742. def_bool y
  743. depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
  744. select SPARSEMEM_STATIC if X86_32
  745. select SPARSEMEM_VMEMMAP_ENABLE if X86_64
  746. config ARCH_SELECT_MEMORY_MODEL
  747. def_bool y
  748. depends on ARCH_SPARSEMEM_ENABLE
  749. config ARCH_MEMORY_PROBE
  750. def_bool X86_64
  751. depends on MEMORY_HOTPLUG
  752. source "mm/Kconfig"
  753. config HIGHPTE
  754. bool "Allocate 3rd-level pagetables from highmem"
  755. depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
  756. help
  757. The VM uses one page table entry for each page of physical memory.
  758. For systems with a lot of RAM, this can be wasteful of precious
  759. low memory. Setting this option will put user-space page table
  760. entries in high memory.
  761. config MATH_EMULATION
  762. bool
  763. prompt "Math emulation" if X86_32
  764. ---help---
  765. Linux can emulate a math coprocessor (used for floating point
  766. operations) if you don't have one. 486DX and Pentium processors have
  767. a math coprocessor built in, 486SX and 386 do not, unless you added
  768. a 487DX or 387, respectively. (The messages during boot time can
  769. give you some hints here ["man dmesg"].) Everyone needs either a
  770. coprocessor or this emulation.
  771. If you don't have a math coprocessor, you need to say Y here; if you
  772. say Y here even though you have a coprocessor, the coprocessor will
  773. be used nevertheless. (This behavior can be changed with the kernel
  774. command line option "no387", which comes handy if your coprocessor
  775. is broken. Try "man bootparam" or see the documentation of your boot
  776. loader (lilo or loadlin) about how to pass options to the kernel at
  777. boot time.) This means that it is a good idea to say Y here if you
  778. intend to use this kernel on different machines.
  779. More information about the internals of the Linux math coprocessor
  780. emulation can be found in <file:arch/x86/math-emu/README>.
  781. If you are not sure, say Y; apart from resulting in a 66 KB bigger
  782. kernel, it won't hurt.
  783. config MTRR
  784. bool "MTRR (Memory Type Range Register) support"
  785. ---help---
  786. On Intel P6 family processors (Pentium Pro, Pentium II and later)
  787. the Memory Type Range Registers (MTRRs) may be used to control
  788. processor access to memory ranges. This is most useful if you have
  789. a video (VGA) card on a PCI or AGP bus. Enabling write-combining
  790. allows bus write transfers to be combined into a larger transfer
  791. before bursting over the PCI/AGP bus. This can increase performance
  792. of image write operations 2.5 times or more. Saying Y here creates a
  793. /proc/mtrr file which may be used to manipulate your processor's
  794. MTRRs. Typically the X server should use this.
  795. This code has a reasonably generic interface so that similar
  796. control registers on other processors can be easily supported
  797. as well:
  798. The Cyrix 6x86, 6x86MX and M II processors have Address Range
  799. Registers (ARRs) which provide a similar functionality to MTRRs. For
  800. these, the ARRs are used to emulate the MTRRs.
  801. The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
  802. MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
  803. write-combining. All of these processors are supported by this code
  804. and it makes sense to say Y here if you have one of them.
  805. Saying Y here also fixes a problem with buggy SMP BIOSes which only
  806. set the MTRRs for the boot CPU and not for the secondary CPUs. This
  807. can lead to all sorts of problems, so it's good to say Y here.
  808. You can safely say Y even if your machine doesn't have MTRRs, you'll
  809. just add about 9 KB to your kernel.
  810. See <file:Documentation/mtrr.txt> for more information.
  811. config EFI
  812. def_bool n
  813. prompt "EFI runtime service support"
  814. depends on ACPI
  815. ---help---
  816. This enables the kernel to use EFI runtime services that are
  817. available (such as the EFI variable services).
  818. This option is only useful on systems that have EFI firmware.
  819. In addition, you should use the latest ELILO loader available
  820. at <http://elilo.sourceforge.net> in order to take advantage
  821. of EFI runtime services. However, even with this option, the
  822. resultant kernel should continue to boot on existing non-EFI
  823. platforms.
  824. config IRQBALANCE
  825. def_bool y
  826. prompt "Enable kernel irq balancing"
  827. depends on X86_32 && SMP && X86_IO_APIC
  828. help
  829. The default yes will allow the kernel to do irq load balancing.
  830. Saying no will keep the kernel from doing irq load balancing.
  831. config SECCOMP
  832. def_bool y
  833. prompt "Enable seccomp to safely compute untrusted bytecode"
  834. depends on PROC_FS
  835. help
  836. This kernel feature is useful for number crunching applications
  837. that may need to compute untrusted bytecode during their
  838. execution. By using pipes or other transports made available to
  839. the process as file descriptors supporting the read/write
  840. syscalls, it's possible to isolate those applications in
  841. their own address space using seccomp. Once seccomp is
  842. enabled via /proc/<pid>/seccomp, it cannot be disabled
  843. and the task is only allowed to execute a few safe syscalls
  844. defined by each seccomp mode.
  845. If unsure, say Y. Only embedded should say N here.
  846. config CC_STACKPROTECTOR
  847. bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
  848. depends on X86_64 && EXPERIMENTAL
  849. help
  850. This option turns on the -fstack-protector GCC feature. This
  851. feature puts, at the beginning of critical functions, a canary
  852. value on the stack just before the return address, and validates
  853. the value just before actually returning. Stack based buffer
  854. overflows (that need to overwrite this return address) now also
  855. overwrite the canary, which gets detected and the attack is then
  856. neutralized via a kernel panic.
  857. This feature requires gcc version 4.2 or above, or a distribution
  858. gcc with the feature backported. Older versions are automatically
  859. detected and for those versions, this configuration option is ignored.
  860. config CC_STACKPROTECTOR_ALL
  861. bool "Use stack-protector for all functions"
  862. depends on CC_STACKPROTECTOR
  863. help
  864. Normally, GCC only inserts the canary value protection for
  865. functions that use large-ish on-stack buffers. By enabling
  866. this option, GCC will be asked to do this for ALL functions.
  867. source kernel/Kconfig.hz
  868. config KEXEC
  869. bool "kexec system call"
  870. help
  871. kexec is a system call that implements the ability to shutdown your
  872. current kernel, and to start another kernel. It is like a reboot
  873. but it is independent of the system firmware. And like a reboot
  874. you can start any kernel with it, not just Linux.
  875. The name comes from the similarity to the exec system call.
  876. It is an ongoing process to be certain the hardware in a machine
  877. is properly shutdown, so do not be surprised if this code does not
  878. initially work for you. It may help to enable device hotplugging
  879. support. As of this writing the exact hardware interface is
  880. strongly in flux, so no good recommendation can be made.
  881. config CRASH_DUMP
  882. bool "kernel crash dumps (EXPERIMENTAL)"
  883. depends on EXPERIMENTAL
  884. depends on X86_64 || (X86_32 && HIGHMEM)
  885. help
  886. Generate crash dump after being started by kexec.
  887. This should be normally only set in special crash dump kernels
  888. which are loaded in the main kernel with kexec-tools into
  889. a specially reserved region and then later executed after
  890. a crash by kdump/kexec. The crash dump kernel must be compiled
  891. to a memory address not used by the main kernel or BIOS using
  892. PHYSICAL_START, or it must be built as a relocatable image
  893. (CONFIG_RELOCATABLE=y).
  894. For more details see Documentation/kdump/kdump.txt
  895. config PHYSICAL_START
  896. hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
  897. default "0x1000000" if X86_NUMAQ
  898. default "0x200000" if X86_64
  899. default "0x100000"
  900. help
  901. This gives the physical address where the kernel is loaded.
  902. If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
  903. bzImage will decompress itself to above physical address and
  904. run from there. Otherwise, bzImage will run from the address where
  905. it has been loaded by the boot loader and will ignore above physical
  906. address.
  907. In normal kdump cases one does not have to set/change this option
  908. as now bzImage can be compiled as a completely relocatable image
  909. (CONFIG_RELOCATABLE=y) and be used to load and run from a different
  910. address. This option is mainly useful for the folks who don't want
  911. to use a bzImage for capturing the crash dump and want to use a
  912. vmlinux instead. vmlinux is not relocatable hence a kernel needs
  913. to be specifically compiled to run from a specific memory area
  914. (normally a reserved region) and this option comes handy.
  915. So if you are using bzImage for capturing the crash dump, leave
  916. the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
  917. Otherwise if you plan to use vmlinux for capturing the crash dump
  918. change this value to start of the reserved region (Typically 16MB
  919. 0x1000000). In other words, it can be set based on the "X" value as
  920. specified in the "crashkernel=YM@XM" command line boot parameter
  921. passed to the panic-ed kernel. Typically this parameter is set as
  922. crashkernel=64M@16M. Please take a look at
  923. Documentation/kdump/kdump.txt for more details about crash dumps.
  924. Usage of bzImage for capturing the crash dump is recommended as
  925. one does not have to build two kernels. Same kernel can be used
  926. as production kernel and capture kernel. Above option should have
  927. gone away after relocatable bzImage support is introduced. But it
  928. is present because there are users out there who continue to use
  929. vmlinux for dump capture. This option should go away down the
  930. line.
  931. Don't change this unless you know what you are doing.
  932. config RELOCATABLE
  933. bool "Build a relocatable kernel (EXPERIMENTAL)"
  934. depends on EXPERIMENTAL
  935. help
  936. This builds a kernel image that retains relocation information
  937. so it can be loaded someplace besides the default 1MB.
  938. The relocations tend to make the kernel binary about 10% larger,
  939. but are discarded at runtime.
  940. One use is for the kexec on panic case where the recovery kernel
  941. must live at a different physical address than the primary
  942. kernel.
  943. Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
  944. it has been loaded at and the compile time physical address
  945. (CONFIG_PHYSICAL_START) is ignored.
  946. config PHYSICAL_ALIGN
  947. hex
  948. prompt "Alignment value to which kernel should be aligned" if X86_32
  949. default "0x100000" if X86_32
  950. default "0x200000" if X86_64
  951. range 0x2000 0x400000
  952. help
  953. This value puts the alignment restrictions on physical address
  954. where kernel is loaded and run from. Kernel is compiled for an
  955. address which meets above alignment restriction.
  956. If bootloader loads the kernel at a non-aligned address and
  957. CONFIG_RELOCATABLE is set, kernel will move itself to nearest
  958. address aligned to above value and run from there.
  959. If bootloader loads the kernel at a non-aligned address and
  960. CONFIG_RELOCATABLE is not set, kernel will ignore the run time
  961. load address and decompress itself to the address it has been
  962. compiled for and run from there. The address for which kernel is
  963. compiled already meets above alignment restrictions. Hence the
  964. end result is that kernel runs from a physical address meeting
  965. above alignment restrictions.
  966. Don't change this unless you know what you are doing.
  967. config HOTPLUG_CPU
  968. bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
  969. depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
  970. ---help---
  971. Say Y here to experiment with turning CPUs off and on, and to
  972. enable suspend on SMP systems. CPUs can be controlled through
  973. /sys/devices/system/cpu.
  974. Say N if you want to disable CPU hotplug and don't need to
  975. suspend.
  976. config COMPAT_VDSO
  977. def_bool y
  978. prompt "Compat VDSO support"
  979. depends on X86_32 || IA32_EMULATION
  980. help
  981. Map the 32-bit VDSO to the predictable old-style address too.
  982. ---help---
  983. Say N here if you are running a sufficiently recent glibc
  984. version (2.3.3 or later), to remove the high-mapped
  985. VDSO mapping and to exclusively use the randomized VDSO.
  986. If unsure, say Y.
  987. endmenu
  988. config ARCH_ENABLE_MEMORY_HOTPLUG
  989. def_bool y
  990. depends on X86_64 || (X86_32 && HIGHMEM)
  991. config HAVE_ARCH_EARLY_PFN_TO_NID
  992. def_bool X86_64
  993. depends on NUMA
  994. menu "Power management options"
  995. depends on !X86_VOYAGER
  996. config ARCH_HIBERNATION_HEADER
  997. def_bool y
  998. depends on X86_64 && HIBERNATION
  999. source "kernel/power/Kconfig"
  1000. source "drivers/acpi/Kconfig"
  1001. config X86_APM_BOOT
  1002. bool
  1003. default y
  1004. depends on APM || APM_MODULE
  1005. menuconfig APM
  1006. tristate "APM (Advanced Power Management) BIOS support"
  1007. depends on X86_32 && PM_SLEEP && !X86_VISWS
  1008. ---help---
  1009. APM is a BIOS specification for saving power using several different
  1010. techniques. This is mostly useful for battery powered laptops with
  1011. APM compliant BIOSes. If you say Y here, the system time will be
  1012. reset after a RESUME operation, the /proc/apm device will provide
  1013. battery status information, and user-space programs will receive
  1014. notification of APM "events" (e.g. battery status change).
  1015. If you select "Y" here, you can disable actual use of the APM
  1016. BIOS by passing the "apm=off" option to the kernel at boot time.
  1017. Note that the APM support is almost completely disabled for
  1018. machines with more than one CPU.
  1019. In order to use APM, you will need supporting software. For location
  1020. and more information, read <file:Documentation/pm.txt> and the
  1021. Battery Powered Linux mini-HOWTO, available from
  1022. <http://www.tldp.org/docs.html#howto>.
  1023. This driver does not spin down disk drives (see the hdparm(8)
  1024. manpage ("man 8 hdparm") for that), and it doesn't turn off
  1025. VESA-compliant "green" monitors.
  1026. This driver does not support the TI 4000M TravelMate and the ACER
  1027. 486/DX4/75 because they don't have compliant BIOSes. Many "green"
  1028. desktop machines also don't have compliant BIOSes, and this driver
  1029. may cause those machines to panic during the boot phase.
  1030. Generally, if you don't have a battery in your machine, there isn't
  1031. much point in using this driver and you should say N. If you get
  1032. random kernel OOPSes or reboots that don't seem to be related to
  1033. anything, try disabling/enabling this option (or disabling/enabling
  1034. APM in your BIOS).
  1035. Some other things you should try when experiencing seemingly random,
  1036. "weird" problems:
  1037. 1) make sure that you have enough swap space and that it is
  1038. enabled.
  1039. 2) pass the "no-hlt" option to the kernel
  1040. 3) switch on floating point emulation in the kernel and pass
  1041. the "no387" option to the kernel
  1042. 4) pass the "floppy=nodma" option to the kernel
  1043. 5) pass the "mem=4M" option to the kernel (thereby disabling
  1044. all but the first 4 MB of RAM)
  1045. 6) make sure that the CPU is not over clocked.
  1046. 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
  1047. 8) disable the cache from your BIOS settings
  1048. 9) install a fan for the video card or exchange video RAM
  1049. 10) install a better fan for the CPU
  1050. 11) exchange RAM chips
  1051. 12) exchange the motherboard.
  1052. To compile this driver as a module, choose M here: the
  1053. module will be called apm.
  1054. if APM
  1055. config APM_IGNORE_USER_SUSPEND
  1056. bool "Ignore USER SUSPEND"
  1057. help
  1058. This option will ignore USER SUSPEND requests. On machines with a
  1059. compliant APM BIOS, you want to say N. However, on the NEC Versa M
  1060. series notebooks, it is necessary to say Y because of a BIOS bug.
  1061. config APM_DO_ENABLE
  1062. bool "Enable PM at boot time"
  1063. ---help---
  1064. Enable APM features at boot time. From page 36 of the APM BIOS
  1065. specification: "When disabled, the APM BIOS does not automatically
  1066. power manage devices, enter the Standby State, enter the Suspend
  1067. State, or take power saving steps in response to CPU Idle calls."
  1068. This driver will make CPU Idle calls when Linux is idle (unless this
  1069. feature is turned off -- see "Do CPU IDLE calls", below). This
  1070. should always save battery power, but more complicated APM features
  1071. will be dependent on your BIOS implementation. You may need to turn
  1072. this option off if your computer hangs at boot time when using APM
  1073. support, or if it beeps continuously instead of suspending. Turn
  1074. this off if you have a NEC UltraLite Versa 33/C or a Toshiba
  1075. T400CDT. This is off by default since most machines do fine without
  1076. this feature.
  1077. config APM_CPU_IDLE
  1078. bool "Make CPU Idle calls when idle"
  1079. help
  1080. Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
  1081. On some machines, this can activate improved power savings, such as
  1082. a slowed CPU clock rate, when the machine is idle. These idle calls
  1083. are made after the idle loop has run for some length of time (e.g.,
  1084. 333 mS). On some machines, this will cause a hang at boot time or
  1085. whenever the CPU becomes idle. (On machines with more than one CPU,
  1086. this option does nothing.)
  1087. config APM_DISPLAY_BLANK
  1088. bool "Enable console blanking using APM"
  1089. help
  1090. Enable console blanking using the APM. Some laptops can use this to
  1091. turn off the LCD backlight when the screen blanker of the Linux
  1092. virtual console blanks the screen. Note that this is only used by
  1093. the virtual console screen blanker, and won't turn off the backlight
  1094. when using the X Window system. This also doesn't have anything to
  1095. do with your VESA-compliant power-saving monitor. Further, this
  1096. option doesn't work for all laptops -- it might not turn off your
  1097. backlight at all, or it might print a lot of errors to the console,
  1098. especially if you are using gpm.
  1099. config APM_ALLOW_INTS
  1100. bool "Allow interrupts during APM BIOS calls"
  1101. help
  1102. Normally we disable external interrupts while we are making calls to
  1103. the APM BIOS as a measure to lessen the effects of a badly behaving
  1104. BIOS implementation. The BIOS should reenable interrupts if it
  1105. needs to. Unfortunately, some BIOSes do not -- especially those in
  1106. many of the newer IBM Thinkpads. If you experience hangs when you
  1107. suspend, try setting this to Y. Otherwise, say N.
  1108. config APM_REAL_MODE_POWER_OFF
  1109. bool "Use real mode APM BIOS call to power off"
  1110. help
  1111. Use real mode APM BIOS calls to switch off the computer. This is
  1112. a work-around for a number of buggy BIOSes. Switch this option on if
  1113. your computer crashes instead of powering off properly.
  1114. endif # APM
  1115. source "arch/x86/kernel/cpu/cpufreq/Kconfig"
  1116. source "drivers/cpuidle/Kconfig"
  1117. endmenu
  1118. menu "Bus options (PCI etc.)"
  1119. config PCI
  1120. bool "PCI support" if !X86_VISWS
  1121. depends on !X86_VOYAGER
  1122. default y
  1123. select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
  1124. help
  1125. Find out whether you have a PCI motherboard. PCI is the name of a
  1126. bus system, i.e. the way the CPU talks to the other stuff inside
  1127. your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  1128. VESA. If you have PCI, say Y, otherwise N.
  1129. The PCI-HOWTO, available from
  1130. <http://www.tldp.org/docs.html#howto>, contains valuable
  1131. information about which PCI hardware does work under Linux and which
  1132. doesn't.
  1133. choice
  1134. prompt "PCI access mode"
  1135. depends on X86_32 && PCI && !X86_VISWS
  1136. default PCI_GOANY
  1137. ---help---
  1138. On PCI systems, the BIOS can be used to detect the PCI devices and
  1139. determine their configuration. However, some old PCI motherboards
  1140. have BIOS bugs and may crash if this is done. Also, some embedded
  1141. PCI-based systems don't have any BIOS at all. Linux can also try to
  1142. detect the PCI hardware directly without using the BIOS.
  1143. With this option, you can specify how Linux should detect the
  1144. PCI devices. If you choose "BIOS", the BIOS will be used,
  1145. if you choose "Direct", the BIOS won't be used, and if you
  1146. choose "MMConfig", then PCI Express MMCONFIG will be used.
  1147. If you choose "Any", the kernel will try MMCONFIG, then the
  1148. direct access method and falls back to the BIOS if that doesn't
  1149. work. If unsure, go with the default, which is "Any".
  1150. config PCI_GOBIOS
  1151. bool "BIOS"
  1152. config PCI_GOMMCONFIG
  1153. bool "MMConfig"
  1154. config PCI_GODIRECT
  1155. bool "Direct"
  1156. config PCI_GOANY
  1157. bool "Any"
  1158. endchoice
  1159. config PCI_BIOS
  1160. def_bool y
  1161. depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
  1162. # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
  1163. config PCI_DIRECT
  1164. def_bool y
  1165. depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
  1166. config PCI_MMCONFIG
  1167. def_bool y
  1168. depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
  1169. config PCI_DOMAINS
  1170. def_bool y
  1171. depends on PCI
  1172. config PCI_MMCONFIG
  1173. bool "Support mmconfig PCI config space access"
  1174. depends on X86_64 && PCI && ACPI
  1175. config DMAR
  1176. bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
  1177. depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
  1178. help
  1179. DMA remapping (DMAR) devices support enables independent address
  1180. translations for Direct Memory Access (DMA) from devices.
  1181. These DMA remapping devices are reported via ACPI tables
  1182. and include PCI device scope covered by these DMA
  1183. remapping devices.
  1184. config DMAR_GFX_WA
  1185. def_bool y
  1186. prompt "Support for Graphics workaround"
  1187. depends on DMAR
  1188. help
  1189. Current Graphics drivers tend to use physical address
  1190. for DMA and avoid using DMA APIs. Setting this config
  1191. option permits the IOMMU driver to set a unity map for
  1192. all the OS-visible memory. Hence the driver can continue
  1193. to use physical addresses for DMA.
  1194. config DMAR_FLOPPY_WA
  1195. def_bool y
  1196. depends on DMAR
  1197. help
  1198. Floppy disk drivers are know to bypass DMA API calls
  1199. thereby failing to work when IOMMU is enabled. This
  1200. workaround will setup a 1:1 mapping for the first
  1201. 16M to make floppy (an ISA device) work.
  1202. source "drivers/pci/pcie/Kconfig"
  1203. source "drivers/pci/Kconfig"
  1204. # x86_64 have no ISA slots, but do have ISA-style DMA.
  1205. config ISA_DMA_API
  1206. def_bool y
  1207. if X86_32
  1208. config ISA
  1209. bool "ISA support"
  1210. depends on !(X86_VOYAGER || X86_VISWS)
  1211. help
  1212. Find out whether you have ISA slots on your motherboard. ISA is the
  1213. name of a bus system, i.e. the way the CPU talks to the other stuff
  1214. inside your box. Other bus systems are PCI, EISA, MicroChannel
  1215. (MCA) or VESA. ISA is an older system, now being displaced by PCI;
  1216. newer boards don't support it. If you have ISA, say Y, otherwise N.
  1217. config EISA
  1218. bool "EISA support"
  1219. depends on ISA
  1220. ---help---
  1221. The Extended Industry Standard Architecture (EISA) bus was
  1222. developed as an open alternative to the IBM MicroChannel bus.
  1223. The EISA bus provided some of the features of the IBM MicroChannel
  1224. bus while maintaining backward compatibility with cards made for
  1225. the older ISA bus. The EISA bus saw limited use between 1988 and
  1226. 1995 when it was made obsolete by the PCI bus.
  1227. Say Y here if you are building a kernel for an EISA-based machine.
  1228. Otherwise, say N.
  1229. source "drivers/eisa/Kconfig"
  1230. config MCA
  1231. bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
  1232. default y if X86_VOYAGER
  1233. help
  1234. MicroChannel Architecture is found in some IBM PS/2 machines and
  1235. laptops. It is a bus system similar to PCI or ISA. See
  1236. <file:Documentation/mca.txt> (and especially the web page given
  1237. there) before attempting to build an MCA bus kernel.
  1238. source "drivers/mca/Kconfig"
  1239. config SCx200
  1240. tristate "NatSemi SCx200 support"
  1241. depends on !X86_VOYAGER
  1242. help
  1243. This provides basic support for National Semiconductor's
  1244. (now AMD's) Geode processors. The driver probes for the
  1245. PCI-IDs of several on-chip devices, so its a good dependency
  1246. for other scx200_* drivers.
  1247. If compiled as a module, the driver is named scx200.
  1248. config SCx200HR_TIMER
  1249. tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
  1250. depends on SCx200 && GENERIC_TIME
  1251. default y
  1252. help
  1253. This driver provides a clocksource built upon the on-chip
  1254. 27MHz high-resolution timer. Its also a workaround for
  1255. NSC Geode SC-1100's buggy TSC, which loses time when the
  1256. processor goes idle (as is done by the scheduler). The
  1257. other workaround is idle=poll boot option.
  1258. config GEODE_MFGPT_TIMER
  1259. def_bool y
  1260. prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
  1261. depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
  1262. help
  1263. This driver provides a clock event source based on the MFGPT
  1264. timer(s) in the CS5535 and CS5536 companion chip for the geode.
  1265. MFGPTs have a better resolution and max interval than the
  1266. generic PIT, and are suitable for use as high-res timers.
  1267. endif # X86_32
  1268. config K8_NB
  1269. def_bool y
  1270. depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
  1271. source "drivers/pcmcia/Kconfig"
  1272. source "drivers/pci/hotplug/Kconfig"
  1273. endmenu
  1274. menu "Executable file formats / Emulations"
  1275. source "fs/Kconfig.binfmt"
  1276. config IA32_EMULATION
  1277. bool "IA32 Emulation"
  1278. depends on X86_64
  1279. select COMPAT_BINFMT_ELF
  1280. help
  1281. Include code to run 32-bit programs under a 64-bit kernel. You should
  1282. likely turn this on, unless you're 100% sure that you don't have any
  1283. 32-bit programs left.
  1284. config IA32_AOUT
  1285. tristate "IA32 a.out support"
  1286. depends on IA32_EMULATION
  1287. help
  1288. Support old a.out binaries in the 32bit emulation.
  1289. config COMPAT
  1290. def_bool y
  1291. depends on IA32_EMULATION
  1292. config COMPAT_FOR_U64_ALIGNMENT
  1293. def_bool COMPAT
  1294. depends on X86_64
  1295. config SYSVIPC_COMPAT
  1296. def_bool y
  1297. depends on X86_64 && COMPAT && SYSVIPC
  1298. endmenu
  1299. source "net/Kconfig"
  1300. source "drivers/Kconfig"
  1301. source "drivers/firmware/Kconfig"
  1302. source "fs/Kconfig"
  1303. source "kernel/Kconfig.instrumentation"
  1304. source "arch/x86/Kconfig.debug"
  1305. source "security/Kconfig"
  1306. source "crypto/Kconfig"
  1307. source "arch/x86/kvm/Kconfig"
  1308. source "lib/Kconfig"