Commit a711bdc0 authored by Bharat Bhushan's avatar Bharat Bhushan Committed by Linus Torvalds

kexec/kdump: minor Documentation updates for arm64 and Image

Minor updates in Documentation for arm64 as relocatable kernel.  Also
this patch updates documentation for using uncompressed image "Image"
which is used for ARM64.

Link: http://lkml.kernel.org/r/1495104793-6563-1-git-send-email-Bharat.Bhushan@nxp.comSigned-off-by: default avatarBharat Bhushan <Bharat.Bhushan@nxp.com>
Cc: Dave Young <dyoung@redhat.com>
Cc: Baoquan He <bhe@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>
Cc: Pratyush Anand <panand@redhat.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 1229384f
...@@ -112,8 +112,8 @@ There are two possible methods of using Kdump. ...@@ -112,8 +112,8 @@ There are two possible methods of using Kdump.
2) Or use the system kernel binary itself as dump-capture kernel and there is 2) Or use the system kernel binary itself as dump-capture kernel and there is
no need to build a separate dump-capture kernel. This is possible no need to build a separate dump-capture kernel. This is possible
only with the architectures which support a relocatable kernel. As only with the architectures which support a relocatable kernel. As
of today, i386, x86_64, ppc64, ia64 and arm architectures support relocatable of today, i386, x86_64, ppc64, ia64, arm and arm64 architectures support
kernel. relocatable kernel.
Building a relocatable kernel is advantageous from the point of view that Building a relocatable kernel is advantageous from the point of view that
one does not have to build a second kernel for capturing the dump. But one does not have to build a second kernel for capturing the dump. But
...@@ -339,7 +339,7 @@ For arm: ...@@ -339,7 +339,7 @@ For arm:
For arm64: For arm64:
- Use vmlinux or Image - Use vmlinux or Image
If you are using a uncompressed vmlinux image then use following command If you are using an uncompressed vmlinux image then use following command
to load dump-capture kernel. to load dump-capture kernel.
kexec -p <dump-capture-kernel-vmlinux-image> \ kexec -p <dump-capture-kernel-vmlinux-image> \
...@@ -361,6 +361,12 @@ to load dump-capture kernel. ...@@ -361,6 +361,12 @@ to load dump-capture kernel.
--dtb=<dtb-for-dump-capture-kernel> \ --dtb=<dtb-for-dump-capture-kernel> \
--append="root=<root-dev> <arch-specific-options>" --append="root=<root-dev> <arch-specific-options>"
If you are using an uncompressed Image, then use following command
to load dump-capture kernel.
kexec -p <dump-capture-kernel-Image> \
--initrd=<initrd-for-dump-capture-kernel> \
--append="root=<root-dev> <arch-specific-options>"
Please note, that --args-linux does not need to be specified for ia64. Please note, that --args-linux does not need to be specified for ia64.
It is planned to make this a no-op on that architecture, but for now It is planned to make this a no-op on that architecture, but for now
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment