boot-options.txt 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281
  1. AMD64 specific boot options
  2. There are many others (usually documented in driver documentation), but
  3. only the AMD64 specific ones are listed here.
  4. Machine check
  5. Please see Documentation/x86/x86_64/machinecheck for sysfs runtime tunables.
  6. mce=off
  7. Disable machine check
  8. mce=no_cmci
  9. Disable CMCI(Corrected Machine Check Interrupt) that
  10. Intel processor supports. Usually this disablement is
  11. not recommended, but it might be handy if your hardware
  12. is misbehaving.
  13. Note that you'll get more problems without CMCI than with
  14. due to the shared banks, i.e. you might get duplicated
  15. error logs.
  16. mce=dont_log_ce
  17. Don't make logs for corrected errors. All events reported
  18. as corrected are silently cleared by OS.
  19. This option will be useful if you have no interest in any
  20. of corrected errors.
  21. mce=ignore_ce
  22. Disable features for corrected errors, e.g. polling timer
  23. and CMCI. All events reported as corrected are not cleared
  24. by OS and remained in its error banks.
  25. Usually this disablement is not recommended, however if
  26. there is an agent checking/clearing corrected errors
  27. (e.g. BIOS or hardware monitoring applications), conflicting
  28. with OS's error handling, and you cannot deactivate the agent,
  29. then this option will be a help.
  30. mce=no_lmce
  31. Do not opt-in to Local MCE delivery. Use legacy method
  32. to broadcast MCEs.
  33. mce=bootlog
  34. Enable logging of machine checks left over from booting.
  35. Disabled by default on AMD Fam10h and older because some BIOS
  36. leave bogus ones.
  37. If your BIOS doesn't do that it's a good idea to enable though
  38. to make sure you log even machine check events that result
  39. in a reboot. On Intel systems it is enabled by default.
  40. mce=nobootlog
  41. Disable boot machine check logging.
  42. mce=tolerancelevel[,monarchtimeout] (number,number)
  43. tolerance levels:
  44. 0: always panic on uncorrected errors, log corrected errors
  45. 1: panic or SIGBUS on uncorrected errors, log corrected errors
  46. 2: SIGBUS or log uncorrected errors, log corrected errors
  47. 3: never panic or SIGBUS, log all errors (for testing only)
  48. Default is 1
  49. Can be also set using sysfs which is preferable.
  50. monarchtimeout:
  51. Sets the time in us to wait for other CPUs on machine checks. 0
  52. to disable.
  53. mce=bios_cmci_threshold
  54. Don't overwrite the bios-set CMCI threshold. This boot option
  55. prevents Linux from overwriting the CMCI threshold set by the
  56. bios. Without this option, Linux always sets the CMCI
  57. threshold to 1. Enabling this may make memory predictive failure
  58. analysis less effective if the bios sets thresholds for memory
  59. errors since we will not see details for all errors.
  60. mce=recovery
  61. Force-enable recoverable machine check code paths
  62. nomce (for compatibility with i386): same as mce=off
  63. Everything else is in sysfs now.
  64. APICs
  65. apic Use IO-APIC. Default
  66. noapic Don't use the IO-APIC.
  67. disableapic Don't use the local APIC
  68. nolapic Don't use the local APIC (alias for i386 compatibility)
  69. pirq=... See Documentation/x86/i386/IO-APIC.txt
  70. noapictimer Don't set up the APIC timer
  71. no_timer_check Don't check the IO-APIC timer. This can work around
  72. problems with incorrect timer initialization on some boards.
  73. apicpmtimer
  74. Do APIC timer calibration using the pmtimer. Implies
  75. apicmaintimer. Useful when your PIT timer is totally
  76. broken.
  77. Timing
  78. notsc
  79. Deprecated, use tsc=unstable instead.
  80. nohpet
  81. Don't use the HPET timer.
  82. Idle loop
  83. idle=poll
  84. Don't do power saving in the idle loop using HLT, but poll for rescheduling
  85. event. This will make the CPUs eat a lot more power, but may be useful
  86. to get slightly better performance in multiprocessor benchmarks. It also
  87. makes some profiling using performance counters more accurate.
  88. Please note that on systems with MONITOR/MWAIT support (like Intel EM64T
  89. CPUs) this option has no performance advantage over the normal idle loop.
  90. It may also interact badly with hyperthreading.
  91. Rebooting
  92. reboot=b[ios] | t[riple] | k[bd] | a[cpi] | e[fi] [, [w]arm | [c]old]
  93. bios Use the CPU reboot vector for warm reset
  94. warm Don't set the cold reboot flag
  95. cold Set the cold reboot flag
  96. triple Force a triple fault (init)
  97. kbd Use the keyboard controller. cold reset (default)
  98. acpi Use the ACPI RESET_REG in the FADT. If ACPI is not configured or the
  99. ACPI reset does not work, the reboot path attempts the reset using
  100. the keyboard controller.
  101. efi Use efi reset_system runtime service. If EFI is not configured or the
  102. EFI reset does not work, the reboot path attempts the reset using
  103. the keyboard controller.
  104. Using warm reset will be much faster especially on big memory
  105. systems because the BIOS will not go through the memory check.
  106. Disadvantage is that not all hardware will be completely reinitialized
  107. on reboot so there may be boot problems on some systems.
  108. reboot=force
  109. Don't stop other CPUs on reboot. This can make reboot more reliable
  110. in some cases.
  111. Non Executable Mappings
  112. noexec=on|off
  113. on Enable(default)
  114. off Disable
  115. NUMA
  116. numa=off Only set up a single NUMA node spanning all memory.
  117. numa=noacpi Don't parse the SRAT table for NUMA setup
  118. numa=fake=<size>[MG]
  119. If given as a memory unit, fills all system RAM with nodes of
  120. size interleaved over physical nodes.
  121. numa=fake=<N>
  122. If given as an integer, fills all system RAM with N fake nodes
  123. interleaved over physical nodes.
  124. numa=fake=<N>U
  125. If given as an integer followed by 'U', it will divide each
  126. physical node into N emulated nodes.
  127. ACPI
  128. acpi=off Don't enable ACPI
  129. acpi=ht Use ACPI boot table parsing, but don't enable ACPI
  130. interpreter
  131. acpi=force Force ACPI on (currently not needed)
  132. acpi=strict Disable out of spec ACPI workarounds.
  133. acpi_sci={edge,level,high,low} Set up ACPI SCI interrupt.
  134. acpi=noirq Don't route interrupts
  135. acpi=nocmcff Disable firmware first mode for corrected errors. This
  136. disables parsing the HEST CMC error source to check if
  137. firmware has set the FF flag. This may result in
  138. duplicate corrected error reports.
  139. PCI
  140. pci=off Don't use PCI
  141. pci=conf1 Use conf1 access.
  142. pci=conf2 Use conf2 access.
  143. pci=rom Assign ROMs.
  144. pci=assign-busses Assign busses
  145. pci=irqmask=MASK Set PCI interrupt mask to MASK
  146. pci=lastbus=NUMBER Scan up to NUMBER busses, no matter what the mptable says.
  147. pci=noacpi Don't use ACPI to set up PCI interrupt routing.
  148. IOMMU (input/output memory management unit)
  149. Multiple x86-64 PCI-DMA mapping implementations exist, for example:
  150. 1. <lib/dma-direct.c>: use no hardware/software IOMMU at all
  151. (e.g. because you have < 3 GB memory).
  152. Kernel boot message: "PCI-DMA: Disabling IOMMU"
  153. 2. <arch/x86/kernel/amd_gart_64.c>: AMD GART based hardware IOMMU.
  154. Kernel boot message: "PCI-DMA: using GART IOMMU"
  155. 3. <arch/x86_64/kernel/pci-swiotlb.c> : Software IOMMU implementation. Used
  156. e.g. if there is no hardware IOMMU in the system and it is need because
  157. you have >3GB memory or told the kernel to us it (iommu=soft))
  158. Kernel boot message: "PCI-DMA: Using software bounce buffering
  159. for IO (SWIOTLB)"
  160. 4. <arch/x86_64/pci-calgary.c> : IBM Calgary hardware IOMMU. Used in IBM
  161. pSeries and xSeries servers. This hardware IOMMU supports DMA address
  162. mapping with memory protection, etc.
  163. Kernel boot message: "PCI-DMA: Using Calgary IOMMU"
  164. iommu=[<size>][,noagp][,off][,force][,noforce][,leak[=<nr_of_leak_pages>]
  165. [,memaper[=<order>]][,merge][,fullflush][,nomerge]
  166. [,noaperture][,calgary]
  167. General iommu options:
  168. off Don't initialize and use any kind of IOMMU.
  169. noforce Don't force hardware IOMMU usage when it is not needed.
  170. (default).
  171. force Force the use of the hardware IOMMU even when it is
  172. not actually needed (e.g. because < 3 GB memory).
  173. soft Use software bounce buffering (SWIOTLB) (default for
  174. Intel machines). This can be used to prevent the usage
  175. of an available hardware IOMMU.
  176. iommu options only relevant to the AMD GART hardware IOMMU:
  177. <size> Set the size of the remapping area in bytes.
  178. allowed Overwrite iommu off workarounds for specific chipsets.
  179. fullflush Flush IOMMU on each allocation (default).
  180. nofullflush Don't use IOMMU fullflush.
  181. leak Turn on simple iommu leak tracing (only when
  182. CONFIG_IOMMU_LEAK is on). Default number of leak pages
  183. is 20.
  184. memaper[=<order>] Allocate an own aperture over RAM with size 32MB<<order.
  185. (default: order=1, i.e. 64MB)
  186. merge Do scatter-gather (SG) merging. Implies "force"
  187. (experimental).
  188. nomerge Don't do scatter-gather (SG) merging.
  189. noaperture Ask the IOMMU not to touch the aperture for AGP.
  190. noagp Don't initialize the AGP driver and use full aperture.
  191. panic Always panic when IOMMU overflows.
  192. calgary Use the Calgary IOMMU if it is available
  193. iommu options only relevant to the software bounce buffering (SWIOTLB) IOMMU
  194. implementation:
  195. swiotlb=<pages>[,force]
  196. <pages> Prereserve that many 128K pages for the software IO
  197. bounce buffering.
  198. force Force all IO through the software TLB.
  199. Settings for the IBM Calgary hardware IOMMU currently found in IBM
  200. pSeries and xSeries machines:
  201. calgary=[64k,128k,256k,512k,1M,2M,4M,8M]
  202. calgary=[translate_empty_slots]
  203. calgary=[disable=<PCI bus number>]
  204. panic Always panic when IOMMU overflows
  205. 64k,...,8M - Set the size of each PCI slot's translation table
  206. when using the Calgary IOMMU. This is the size of the translation
  207. table itself in main memory. The smallest table, 64k, covers an IO
  208. space of 32MB; the largest, 8MB table, can cover an IO space of
  209. 4GB. Normally the kernel will make the right choice by itself.
  210. translate_empty_slots - Enable translation even on slots that have
  211. no devices attached to them, in case a device will be hotplugged
  212. in the future.
  213. disable=<PCI bus number> - Disable translation on a given PHB. For
  214. example, the built-in graphics adapter resides on the first bridge
  215. (PCI bus number 0); if translation (isolation) is enabled on this
  216. bridge, X servers that access the hardware directly from user
  217. space might stop working. Use this option if you have devices that
  218. are accessed from userspace directly on some PCI host bridge.
  219. Miscellaneous
  220. nogbpages
  221. Do not use GB pages for kernel direct mappings.
  222. gbpages
  223. Use GB pages for kernel direct mappings.