From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752350AbdEVHKN (ORCPT ); Mon, 22 May 2017 03:10:13 -0400 Received: from mail-pf0-f180.google.com ([209.85.192.180]:34984 "EHLO mail-pf0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751843AbdEVHKK (ORCPT ); Mon, 22 May 2017 03:10:10 -0400 Subject: Re: [PATCH v2] kexec/kdump: Minor Documentation updates for arm64 and Image To: Bharat Bhushan , dyoung@redhat.com, bhe@redhat.com, vgoyal@redhat.com, corbet@lwn.net, takahiro.akashi@linaro.org References: <1495104793-6563-1-git-send-email-Bharat.Bhushan@nxp.com> Cc: kexec@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org From: Pratyush Anand Message-ID: <2eab1d0a-c147-8364-8fb8-4efbea879992@redhat.com> Date: Mon, 22 May 2017 12:39:59 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <1495104793-6563-1-git-send-email-Bharat.Bhushan@nxp.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 18 May 2017 04:23 PM, Bharat Bhushan wrote: > This patch have minor updates in Documentation for arm64i as arm64 > relocatable kernel. > Also this patch updates documentation for using uncompressed > image "Image" which is used for ARM64. > > Signed-off-by: Bharat Bhushan > --- > v1->v2 > - "a uncompressed" replaced with "an uncompressed" Reviewed-by: Pratyush Anand > > Documentation/kdump/kdump.txt | 12 +++++++++--- > 1 file changed, 9 insertions(+), 3 deletions(-) > > diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt > index 615434d..5181445 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 > @@ -339,7 +339,7 @@ For arm: > For arm64: > - 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. > > kexec -p \ > @@ -361,6 +361,12 @@ to load dump-capture kernel. > --dtb= \ > --append="root= " > > +If you are using an uncompressed Image, then use following command > +to load dump-capture kernel. > + > + kexec -p \ > + --initrd= \ > + --append="root= " > > 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 >