From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754732AbdERF71 (ORCPT <rfc822;w@1wt.eu>);
        Thu, 18 May 2017 01:59:27 -0400
Received: from mx1.redhat.com ([209.132.183.28]:53420 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753606AbdERF70 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 18 May 2017 01:59:26 -0400
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com E23B8C059720
Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dyoung@redhat.com
DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com E23B8C059720
Date: Thu, 18 May 2017 13:59:14 +0800
From: Dave Young <dyoung@redhat.com>
To: Bharat Bhushan <Bharat.Bhushan@nxp.com>
Cc: bhe@redhat.com, vgoyal@redhat.com, corbet@lwn.net,
        kexec@lists.infradead.org, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org, takahiro.akashi@linaro.org,
        panand@redhat.com
Subject: Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and
 Image
Message-ID: <20170518055914.GC4059@dhcp-128-65.nay.redhat.com>
References: <1495085600-2645-1-git-send-email-Bharat.Bhushan@nxp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1495085600-2645-1-git-send-email-Bharat.Bhushan@nxp.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Thu, 18 May 2017 05:59:26 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Add Takahiro and Pratyush, they should be able to review the arm64 part.

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

s/a/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>"

For uncompressed Image, dtb is not necessary?

>  
>  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
> 

Thanks
Dave