diff options
Diffstat (limited to 'Documentation/kdump/kdump.txt')
-rw-r--r-- | Documentation/kdump/kdump.txt | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt index bc4bd5a44b88..b6fe6a885bf8 100644 --- a/Documentation/kdump/kdump.txt +++ b/Documentation/kdump/kdump.txt | |||
@@ -18,7 +18,7 @@ memory image to a dump file on the local disk, or across the network to | |||
18 | a remote system. | 18 | a remote system. |
19 | 19 | ||
20 | Kdump and kexec are currently supported on the x86, x86_64, ppc64, ia64, | 20 | Kdump and kexec are currently supported on the x86, x86_64, ppc64, ia64, |
21 | s390x and arm architectures. | 21 | s390x, arm and arm64 architectures. |
22 | 22 | ||
23 | When the system kernel boots, it reserves a small section of memory for | 23 | When the system kernel boots, it reserves a small section of memory for |
24 | the dump-capture kernel. This ensures that ongoing Direct Memory Access | 24 | the dump-capture kernel. This ensures that ongoing Direct Memory Access |
@@ -249,6 +249,13 @@ Dump-capture kernel config options (Arch Dependent, arm) | |||
249 | 249 | ||
250 | AUTO_ZRELADDR=y | 250 | AUTO_ZRELADDR=y |
251 | 251 | ||
252 | Dump-capture kernel config options (Arch Dependent, arm64) | ||
253 | ---------------------------------------------------------- | ||
254 | |||
255 | - Please note that kvm of the dump-capture kernel will not be enabled | ||
256 | on non-VHE systems even if it is configured. This is because the CPU | ||
257 | will not be reset to EL2 on panic. | ||
258 | |||
252 | Extended crashkernel syntax | 259 | Extended crashkernel syntax |
253 | =========================== | 260 | =========================== |
254 | 261 | ||
@@ -312,6 +319,8 @@ Boot into System Kernel | |||
312 | any space below the alignment point may be overwritten by the dump-capture kernel, | 319 | any space below the alignment point may be overwritten by the dump-capture kernel, |
313 | which means it is possible that the vmcore is not that precise as expected. | 320 | which means it is possible that the vmcore is not that precise as expected. |
314 | 321 | ||
322 | On arm64, use "crashkernel=Y[@X]". Note that the start address of | ||
323 | the kernel, X if explicitly specified, must be aligned to 2MiB (0x200000). | ||
315 | 324 | ||
316 | Load the Dump-capture Kernel | 325 | Load the Dump-capture Kernel |
317 | ============================ | 326 | ============================ |
@@ -334,6 +343,8 @@ For s390x: | |||
334 | - Use image or bzImage | 343 | - Use image or bzImage |
335 | For arm: | 344 | For arm: |
336 | - Use zImage | 345 | - Use zImage |
346 | For arm64: | ||
347 | - Use vmlinux or Image | ||
337 | 348 | ||
338 | If you are using a uncompressed vmlinux image then use following command | 349 | If you are using a uncompressed vmlinux image then use following command |
339 | to load dump-capture kernel. | 350 | to load dump-capture kernel. |
@@ -377,6 +388,9 @@ For s390x: | |||
377 | For arm: | 388 | For arm: |
378 | "1 maxcpus=1 reset_devices" | 389 | "1 maxcpus=1 reset_devices" |
379 | 390 | ||
391 | For arm64: | ||
392 | "1 maxcpus=1 reset_devices" | ||
393 | |||
380 | Notes on loading the dump-capture kernel: | 394 | Notes on loading the dump-capture kernel: |
381 | 395 | ||
382 | * By default, the ELF headers are stored in ELF64 format to support | 396 | * By default, the ELF headers are stored in ELF64 format to support |