[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM5PR0401MB25457242B7B685CB21D6F0759AE40@AM5PR0401MB2545.eurprd04.prod.outlook.com>
Date: Thu, 18 May 2017 06:14:07 +0000
From: Bharat Bhushan <bharat.bhushan@....com>
To: Dave Young <dyoung@...hat.com>
CC: "bhe@...hat.com" <bhe@...hat.com>,
"vgoyal@...hat.com" <vgoyal@...hat.com>,
"corbet@....net" <corbet@....net>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"takahiro.akashi@...aro.org" <takahiro.akashi@...aro.org>,
"panand@...hat.com" <panand@...hat.com>
Subject: RE: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and
Image
> -----Original Message-----
> From: Dave Young [mailto:dyoung@...hat.com]
> Sent: Thursday, May 18, 2017 11:29 AM
> To: Bharat Bhushan <bharat.bhushan@....com>
> Cc: bhe@...hat.com; vgoyal@...hat.com; corbet@....net;
> kexec@...ts.infradead.org; linux-doc@...r.kernel.org; linux-
> kernel@...r.kernel.org; takahiro.akashi@...aro.org; panand@...hat.com
> Subject: Re: [PATCH] kexec/kdump: Minor Documentation updates for
> arm64 and Image
>
> 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?
Yes dtb is not necessary, it works for me without giving dtb.
Thanks
-Bharat
>
> >
> > 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
Powered by blists - more mailing lists