On 05/18/17 at 11:03am, Bharat Bhushan wrote: > This patch have minor updates in Documentation for arm64i as > relocatable kernel. > Also this patch updates documentation for using uncompressed > image "Image" which is used for ARM64. > > Signed-off-by: Bharat Bhushan <Bharat.Bhushan@xxxxxxx> > --- > Documentation/kdump/kdump.txt | 10 ++++++++-- > 1 file changed, 8 insertions(+), 2 deletions(-) > > diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt > index 615434d..522ce13 100644 > --- a/Documentation/kdump/kdump.txt > +++ b/Documentation/kdump/kdump.txt > @@ -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 > no need to build a separate dump-capture kernel. This is possible > only with the architectures which support a relocatable kernel. As > - of today, i386, x86_64, ppc64, ia64 and arm architectures support relocatable > - kernel. > + of today, i386, x86_64, ppc64, ia64, arm and arm64 architectures support > + relocatable kernel. > > 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 > @@ -361,6 +361,12 @@ to load dump-capture kernel. > --dtb=<dtb-for-dump-capture-kernel> \ > --append="root=<root-dev> <arch-specific-options>" > > +If you are using a uncompressed Image, then use following command ~ an > +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. > It is planned to make this a no-op on that architecture, but for now > -- > 1.9.3 > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
