Kconfig 52 KB

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