All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Bharat Bhushan <Bharat.Bhushan@nxp.com>
Cc: linux-doc@vger.kernel.org, corbet@lwn.net,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	dyoung@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and Image
Date: Thu, 18 May 2017 13:45:22 +0800	[thread overview]
Message-ID: <20170518054522.GF29117@x1> (raw)
In-Reply-To: <1495085600-2645-1-git-send-email-Bharat.Bhushan@nxp.com>

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@nxp.com>
> ---
>  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
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Bharat Bhushan <Bharat.Bhushan@nxp.com>
Cc: dyoung@redhat.com, vgoyal@redhat.com, corbet@lwn.net,
	kexec@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and Image
Date: Thu, 18 May 2017 13:45:22 +0800	[thread overview]
Message-ID: <20170518054522.GF29117@x1> (raw)
In-Reply-To: <1495085600-2645-1-git-send-email-Bharat.Bhushan@nxp.com>

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@nxp.com>
> ---
>  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
> 

  reply	other threads:[~2017-05-18  5:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  5:33 [PATCH] kexec/kdump: Minor Documentation updates for arm64 and Image Bharat Bhushan
2017-05-18  5:33 ` Bharat Bhushan
2017-05-18  5:45 ` Baoquan He [this message]
2017-05-18  5:45   ` Baoquan He
2017-05-18  5:59 ` Dave Young
2017-05-18  5:59   ` Dave Young
2017-05-18  6:14   ` Bharat Bhushan
2017-05-18  6:14     ` Bharat Bhushan
2017-05-19  3:45   ` AKASHI Takahiro
2017-05-19  3:45     ` AKASHI Takahiro
2017-05-22  6:39     ` Pratyush Anand
2017-05-22  6:39       ` Pratyush Anand
2017-05-22  6:49       ` Bharat Bhushan
2017-05-22  6:49         ` Bharat Bhushan
2017-05-22  7:05         ` Pratyush Anand
2017-05-22  7:05           ` Pratyush Anand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170518054522.GF29117@x1 \
    --to=bhe@redhat.com \
    --cc=Bharat.Bhushan@nxp.com \
    --cc=corbet@lwn.net \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.