Kconfig 61 KB

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