linux-kernel - Re: [PATCH v2] kexec/kdump: Minor Documentation updates for arm64 and Image

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2eab1d0a-c147-8364-8fb8-4efbea879992@redhat.com>
Date:   Mon, 22 May 2017 12:39:59 +0530
From:   Pratyush Anand <panand@...hat.com>
To:     Bharat Bhushan <Bharat.Bhushan@....com>, dyoung@...hat.com,
        bhe@...hat.com, vgoyal@...hat.com, corbet@....net,
        takahiro.akashi@...aro.org
Cc:     kexec@...ts.infradead.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] kexec/kdump: Minor Documentation updates for arm64 and
 Image



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 <Bharat.Bhushan@....com>
> ---
> v1->v2
>   - "a uncompressed" replaced with "an uncompressed"

Reviewed-by: Pratyush Anand <panand@...hat.com>

>
>  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 <dump-capture-kernel-vmlinux-image> \
> @@ -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 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.
>  It is planned to make this a no-op on that architecture, but for now
>