linux-kernel - Re: [PATCH] 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]

Date:   Fri, 19 May 2017 12:45:15 +0900
From:   AKASHI Takahiro <takahiro.akashi@...aro.org>
To:     Dave Young <dyoung@...hat.com>
Cc:     Bharat Bhushan <Bharat.Bhushan@....com>, bhe@...hat.com,
        vgoyal@...hat.com, corbet@....net, kexec@...ts.infradead.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        panand@...hat.com
Subject: Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and
 Image

On Thu, May 18, 2017 at 01:59:14PM +0800, Dave Young wrote:
> 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@....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?

Just for clarification, dtb is optional for both vmlinux and Image
on arm64. (This means you can specify it if you want.)
But this is also true for initrd and append(command line) to some extent.

More precisely, whether these parameters are optional or not will
depend on architectures, not formats, I believe.

Thanks,
-Takahiro AKASHI

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