Kconfig 52 KB

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