Kconfig 53 KB

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