Kconfig 63 KB

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