From: Pratyush Anand <panand@redhat.com>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>,
Dave Young <dyoung@redhat.com>,
Bharat Bhushan <Bharat.Bhushan@nxp.com>,
bhe@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: Mon, 22 May 2017 12:09:26 +0530 [thread overview]
Message-ID: <2ed84f9f-76c8-62eb-36b5-e97568ba3a2e@redhat.com> (raw)
In-Reply-To: <20170519034514.GA4283@fireball>
On Friday 19 May 2017 09:15 AM, AKASHI Takahiro wrote:
>>> +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.
Yes, I agree.
>
> More precisely, whether these parameters are optional or not will
> depend on architectures, not formats, I believe.
May be not architecture, rather a distro environment.
For example, we should be able to work without --initrd for any arch if kernel
has been compiled by configuring CONFG_INITRAMFS_SOURCE.
~Pratyush
next prev parent reply other threads:[~2017-05-22 6:39 UTC|newest]
Thread overview: 8+ 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:45 ` Baoquan He
2017-05-18 5:59 ` Dave Young
2017-05-18 6:14 ` Bharat Bhushan
2017-05-19 3:45 ` AKASHI Takahiro
2017-05-22 6:39 ` Pratyush Anand [this message]
2017-05-22 6:49 ` Bharat Bhushan
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=2ed84f9f-76c8-62eb-36b5-e97568ba3a2e@redhat.com \
--to=panand@redhat.com \
--cc=Bharat.Bhushan@nxp.com \
--cc=bhe@redhat.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=takahiro.akashi@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).