aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAKASHI Takahiro <takahiro.akashi@linaro.org>2017-04-02 22:24:40 -0400
committerCatalin Marinas <catalin.marinas@arm.com>2017-04-05 13:32:32 -0400
commit0ceb7d887ed6cf22d84657fa31a1521a7e935473 (patch)
tree5b198ca5d01533a7f80b9dab0954e72fe9a15e0a
parent3f5c1e1e761981b41d0be22f9aadfc7458fcc786 (diff)
Documentation: kdump: describe arm64 port
Add arch specific descriptions about kdump usage on arm64 to kdump.txt. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Baoquan He <bhe@redhat.com> Acked-by: Dave Young <dyoung@redhat.com> Acked-by: Catalin Marinas <catalin.marinas@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
-rw-r--r--Documentation/kdump/kdump.txt16
1 files changed, 15 insertions, 1 deletions
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index b0eb27b956d9..615434d81108 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
18a remote system. 18a remote system.
19 19
20Kdump and kexec are currently supported on the x86, x86_64, ppc64, ia64, 20Kdump and kexec are currently supported on the x86, x86_64, ppc64, ia64,
21s390x and arm architectures. 21s390x, arm and arm64 architectures.
22 22
23When the system kernel boots, it reserves a small section of memory for 23When the system kernel boots, it reserves a small section of memory for
24the dump-capture kernel. This ensures that ongoing Direct Memory Access 24the 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
252Dump-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
252Extended crashkernel syntax 259Extended crashkernel syntax
253=========================== 260===========================
254 261
@@ -305,6 +312,8 @@ Boot into System Kernel
305 kernel will automatically locate the crash kernel image within the 312 kernel will automatically locate the crash kernel image within the
306 first 512MB of RAM if X is not given. 313 first 512MB of RAM if X is not given.
307 314
315 On arm64, use "crashkernel=Y[@X]". Note that the start address of
316 the kernel, X if explicitly specified, must be aligned to 2MiB (0x200000).
308 317
309Load the Dump-capture Kernel 318Load the Dump-capture Kernel
310============================ 319============================
@@ -327,6 +336,8 @@ For s390x:
327 - Use image or bzImage 336 - Use image or bzImage
328For arm: 337For arm:
329 - Use zImage 338 - Use zImage
339For arm64:
340 - Use vmlinux or Image
330 341
331If you are using a uncompressed vmlinux image then use following command 342If you are using a uncompressed vmlinux image then use following command
332to load dump-capture kernel. 343to load dump-capture kernel.
@@ -370,6 +381,9 @@ For s390x:
370For arm: 381For arm:
371 "1 maxcpus=1 reset_devices" 382 "1 maxcpus=1 reset_devices"
372 383
384For arm64:
385 "1 maxcpus=1 reset_devices"
386
373Notes on loading the dump-capture kernel: 387Notes on loading the dump-capture kernel:
374 388
375* By default, the ELF headers are stored in ELF64 format to support 389* By default, the ELF headers are stored in ELF64 format to support