blob: 7500aad95f3ceaf70a0d546488c9231751731f3c [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001AMD64 specific boot options
2
3There are many others (usually documented in driver documentation), but
4only the AMD64 specific ones are listed here.
5
6Machine check
7
8 mce=off disable machine check
Andi Kleend5172f22005-08-07 09:42:07 -07009 mce=bootlog Enable logging of machine checks left over from booting.
Andi Kleene5835382005-11-05 17:25:54 +010010 Disabled by default on AMD because some BIOS leave bogus ones.
Andi Kleend5172f22005-08-07 09:42:07 -070011 If your BIOS doesn't do that it's a good idea to enable though
12 to make sure you log even machine check events that result
Andi Kleene5835382005-11-05 17:25:54 +010013 in a reboot. On Intel systems it is enabled by default.
14 mce=nobootlog
15 Disable boot machine check logging.
Andi Kleen8c566ef2005-09-12 18:49:24 +020016 mce=tolerancelevel (number)
17 0: always panic, 1: panic if deadlock possible,
18 2: try to avoid panic, 3: never panic or exit (for testing)
19 default is 1
20 Can be also set using sysfs which is preferable.
Linus Torvalds1da177e2005-04-16 15:20:36 -070021
22 nomce (for compatibility with i386): same as mce=off
23
24 Everything else is in sysfs now.
25
26APICs
27
28 apic Use IO-APIC. Default
29
30 noapic Don't use the IO-APIC.
31
32 disableapic Don't use the local APIC
33
34 nolapic Don't use the local APIC (alias for i386 compatibility)
35
36 pirq=... See Documentation/i386/IO-APIC.txt
37
38 noapictimer Don't set up the APIC timer
39
Andi Kleen14d98ca2005-05-20 14:27:59 -070040 no_timer_check Don't check the IO-APIC timer. This can work around
41 problems with incorrect timer initialization on some boards.
42
Andi Kleen73dea472006-02-03 21:50:50 +010043 apicmaintimer Run time keeping from the local APIC timer instead
44 of using the PIT/HPET interrupt for this. This is useful
45 when the PIT/HPET interrupts are unreliable.
46
47 noapicmaintimer Don't do time keeping using the APIC timer.
48 Useful when this option was auto selected, but doesn't work.
49
Andi Kleen0c3749c2006-02-03 21:51:41 +010050 apicpmtimer
51 Do APIC timer calibration using the pmtimer. Implies
52 apicmaintimer. Useful when your PIT timer is totally
53 broken.
54
Linus Torvaldsfea5f1e2007-01-08 15:04:46 -080055 disable_8254_timer / enable_8254_timer
56 Enable interrupt 0 timer routing over the 8254 in addition to over
57 the IO-APIC. The kernel tries to set a sensible default.
58
Linus Torvalds1da177e2005-04-16 15:20:36 -070059Early Console
60
61 syntax: earlyprintk=vga
62 earlyprintk=serial[,ttySn[,baudrate]]
63
64 The early console is useful when the kernel crashes before the
65 normal console is initialized. It is not enabled by
66 default because it has some cosmetic problems.
67 Append ,keep to not disable it when the real console takes over.
68 Only vga or serial at a time, not both.
69 Currently only ttyS0 and ttyS1 are supported.
70 Interaction with the standard serial driver is not very good.
71 The VGA output is eventually overwritten by the real console.
72
73Timing
74
75 notsc
76 Don't use the CPU time stamp counter to read the wall time.
77 This can be used to work around timing problems on multiprocessor systems
Andi Kleenef4d7cb2005-07-28 21:15:34 -070078 with not properly synchronized CPUs.
Linus Torvalds1da177e2005-04-16 15:20:36 -070079
80 report_lost_ticks
81 Report when timer interrupts are lost because some code turned off
82 interrupts for too long.
83
84 nmi_watchdog=NUMBER[,panic]
85 NUMBER can be:
86 0 don't use an NMI watchdog
87 1 use the IO-APIC timer for the NMI watchdog
88 2 use the local APIC for the NMI watchdog using a performance counter. Note
89 This will use one performance counter and the local APIC's performance
90 vector.
91 When panic is specified panic when an NMI watchdog timeout occurs.
92 This is useful when you use a panic=... timeout and need the box
93 quickly up again.
94
95 nohpet
96 Don't use the HPET timer.
97
98Idle loop
99
100 idle=poll
101 Don't do power saving in the idle loop using HLT, but poll for rescheduling
102 event. This will make the CPUs eat a lot more power, but may be useful
103 to get slightly better performance in multiprocessor benchmarks. It also
104 makes some profiling using performance counters more accurate.
Andi Kleenef4d7cb2005-07-28 21:15:34 -0700105 Please note that on systems with MONITOR/MWAIT support (like Intel EM64T
106 CPUs) this option has no performance advantage over the normal idle loop.
107 It may also interact badly with hyperthreading.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700108
109Rebooting
110
111 reboot=b[ios] | t[riple] | k[bd] [, [w]arm | [c]old]
Matt LaPlanted6bc8ac2006-10-03 22:54:15 +0200112 bios Use the CPU reboot vector for warm reset
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 warm Don't set the cold reboot flag
114 cold Set the cold reboot flag
115 triple Force a triple fault (init)
116 kbd Use the keyboard controller. cold reset (default)
117
118 Using warm reset will be much faster especially on big memory
119 systems because the BIOS will not go through the memory check.
120 Disadvantage is that not all hardware will be completely reinitialized
121 on reboot so there may be boot problems on some systems.
122
123 reboot=force
124
125 Don't stop other CPUs on reboot. This can make reboot more reliable
126 in some cases.
127
128Non Executable Mappings
129
130 noexec=on|off
131
132 on Enable(default)
133 off Disable
134
135SMP
136
137 nosmp Only use a single CPU
138
139 maxcpus=NUMBER only use upto NUMBER CPUs
140
141 cpumask=MASK only use cpus with bits set in mask
142
Andi Kleen420f8f62005-11-05 17:25:54 +0100143 additional_cpus=NUM Allow NUM more CPUs for hotplug
Andi Kleenf62a91f2006-01-11 22:42:35 +0100144 (defaults are specified by the BIOS, see Documentation/x86_64/cpu-hotplug-spec)
Andi Kleen420f8f62005-11-05 17:25:54 +0100145
Linus Torvalds1da177e2005-04-16 15:20:36 -0700146NUMA
147
148 numa=off Only set up a single NUMA node spanning all memory.
149
150 numa=noacpi Don't parse the SRAT table for NUMA setup
151
David Rientjes8b8ca80e2007-05-02 19:27:09 +0200152 numa=fake=CMDLINE
153 If a number, fakes CMDLINE nodes and ignores NUMA setup of the
154 actual machine. Otherwise, system memory is configured
155 depending on the sizes and coefficients listed. For example:
156 numa=fake=2*512,1024,4*256
157 gives two 512M nodes, a 1024M node, and four 256M nodes. The
158 remaining system RAM is allocated to an additional node.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700159
Andi Kleen68a3a7f2006-04-07 19:49:18 +0200160 numa=hotadd=percent
161 Only allow hotadd memory to preallocate page structures upto
162 percent of already available memory.
163 numa=hotadd=0 will disable hotadd memory.
164
Linus Torvalds1da177e2005-04-16 15:20:36 -0700165ACPI
166
167 acpi=off Don't enable ACPI
168 acpi=ht Use ACPI boot table parsing, but don't enable ACPI
169 interpreter
170 acpi=force Force ACPI on (currently not needed)
171
172 acpi=strict Disable out of spec ACPI workarounds.
173
174 acpi_sci={edge,level,high,low} Set up ACPI SCI interrupt.
175
176 acpi=noirq Don't route interrupts
177
178PCI
179
180 pci=off Don't use PCI
181 pci=conf1 Use conf1 access.
182 pci=conf2 Use conf2 access.
183 pci=rom Assign ROMs.
184 pci=assign-busses Assign busses
185 pci=irqmask=MASK Set PCI interrupt mask to MASK
186 pci=lastbus=NUMBER Scan upto NUMBER busses, no matter what the mptable says.
187 pci=noacpi Don't use ACPI to set up PCI interrupt routing.
188
Karsten Weiss55588702007-02-13 13:26:21 +0100189IOMMU (input/output memory management unit)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700190
Karsten Weiss55588702007-02-13 13:26:21 +0100191 Currently four x86-64 PCI-DMA mapping implementations exist:
Linus Torvalds1da177e2005-04-16 15:20:36 -0700192
Karsten Weiss55588702007-02-13 13:26:21 +0100193 1. <arch/x86_64/kernel/pci-nommu.c>: use no hardware/software IOMMU at all
194 (e.g. because you have < 3 GB memory).
195 Kernel boot message: "PCI-DMA: Disabling IOMMU"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700196
Karsten Weiss55588702007-02-13 13:26:21 +0100197 2. <arch/x86_64/kernel/pci-gart.c>: AMD GART based hardware IOMMU.
198 Kernel boot message: "PCI-DMA: using GART IOMMU"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700199
Karsten Weiss55588702007-02-13 13:26:21 +0100200 3. <arch/x86_64/kernel/pci-swiotlb.c> : Software IOMMU implementation. Used
201 e.g. if there is no hardware IOMMU in the system and it is need because
202 you have >3GB memory or told the kernel to us it (iommu=soft))
203 Kernel boot message: "PCI-DMA: Using software bounce buffering
204 for IO (SWIOTLB)"
205
206 4. <arch/x86_64/pci-calgary.c> : IBM Calgary hardware IOMMU. Used in IBM
207 pSeries and xSeries servers. This hardware IOMMU supports DMA address
208 mapping with memory protection, etc.
209 Kernel boot message: "PCI-DMA: Using Calgary IOMMU"
210
211 iommu=[<size>][,noagp][,off][,force][,noforce][,leak[=<nr_of_leak_pages>]
212 [,memaper[=<order>]][,merge][,forcesac][,fullflush][,nomerge]
213 [,noaperture][,calgary]
214
215 General iommu options:
216 off Don't initialize and use any kind of IOMMU.
217 noforce Don't force hardware IOMMU usage when it is not needed.
218 (default).
219 force Force the use of the hardware IOMMU even when it is
220 not actually needed (e.g. because < 3 GB memory).
221 soft Use software bounce buffering (SWIOTLB) (default for
222 Intel machines). This can be used to prevent the usage
223 of an available hardware IOMMU.
224
225 iommu options only relevant to the AMD GART hardware IOMMU:
226 <size> Set the size of the remapping area in bytes.
227 allowed Overwrite iommu off workarounds for specific chipsets.
228 fullflush Flush IOMMU on each allocation (default).
229 nofullflush Don't use IOMMU fullflush.
230 leak Turn on simple iommu leak tracing (only when
231 CONFIG_IOMMU_LEAK is on). Default number of leak pages
232 is 20.
233 memaper[=<order>] Allocate an own aperture over RAM with size 32MB<<order.
234 (default: order=1, i.e. 64MB)
Randy Dunlap57d30772007-02-13 13:26:23 +0100235 merge Do scatter-gather (SG) merging. Implies "force"
Karsten Weiss55588702007-02-13 13:26:21 +0100236 (experimental).
Randy Dunlap57d30772007-02-13 13:26:23 +0100237 nomerge Don't do scatter-gather (SG) merging.
Karsten Weiss55588702007-02-13 13:26:21 +0100238 noaperture Ask the IOMMU not to touch the aperture for AGP.
239 forcesac Force single-address cycle (SAC) mode for masks <40bits
240 (experimental).
241 noagp Don't initialize the AGP driver and use full aperture.
242 allowdac Allow double-address cycle (DAC) mode, i.e. DMA >4GB.
243 DAC is used with 32-bit PCI to push a 64-bit address in
244 two cycles. When off all DMA over >4GB is forced through
245 an IOMMU or software bounce buffering.
246 nodac Forbid DAC mode, i.e. DMA >4GB.
247 panic Always panic when IOMMU overflows.
248 calgary Use the Calgary IOMMU if it is available
249
250 iommu options only relevant to the software bounce buffering (SWIOTLB) IOMMU
251 implementation:
252 swiotlb=<pages>[,force]
253 <pages> Prereserve that many 128K pages for the software IO
254 bounce buffering.
255 force Force all IO through the software TLB.
256
257 Settings for the IBM Calgary hardware IOMMU currently found in IBM
258 pSeries and xSeries machines:
259
260 calgary=[64k,128k,256k,512k,1M,2M,4M,8M]
261 calgary=[translate_empty_slots]
262 calgary=[disable=<PCI bus number>]
263 panic Always panic when IOMMU overflows
Jon Masone4650582006-06-26 13:58:14 +0200264
265 64k,...,8M - Set the size of each PCI slot's translation table
266 when using the Calgary IOMMU. This is the size of the translation
267 table itself in main memory. The smallest table, 64k, covers an IO
268 space of 32MB; the largest, 8MB table, can cover an IO space of
269 4GB. Normally the kernel will make the right choice by itself.
270
271 translate_empty_slots - Enable translation even on slots that have
272 no devices attached to them, in case a device will be hotplugged
273 in the future.
274
275 disable=<PCI bus number> - Disable translation on a given PHB. For
276 example, the built-in graphics adapter resides on the first bridge
277 (PCI bus number 0); if translation (isolation) is enabled on this
278 bridge, X servers that access the hardware directly from user
279 space might stop working. Use this option if you have devices that
280 are accessed from userspace directly on some PCI host bridge.
281
Linus Torvalds1da177e2005-04-16 15:20:36 -0700282Debugging
283
Randy Dunlap57d30772007-02-13 13:26:23 +0100284 oops=panic Always panic on oopses. Default is to just kill the process,
285 but there is a small probability of deadlocking the machine.
286 This will also cause panics on machine check exceptions.
287 Useful together with panic=30 to trigger a reboot.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700288
Randy Dunlap57d30772007-02-13 13:26:23 +0100289 kstack=N Print N words from the kernel stack in oops dumps.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700290
Randy Dunlap57d30772007-02-13 13:26:23 +0100291 pagefaulttrace Dump all page faults. Only useful for extreme debugging
Andi Kleen9e43e1b2005-11-05 17:25:54 +0100292 and will create a lot of output.
293
Andi Kleenb783fd92006-07-28 14:44:54 +0200294 call_trace=[old|both|newfallback|new]
295 old: use old inexact backtracer
296 new: use new exact dwarf2 unwinder
297 both: print entries from both
298 newfallback: use new unwinder but fall back to old if it gets
299 stuck (default)
300
Randy Dunlap57d30772007-02-13 13:26:23 +0100301Miscellaneous