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