From: Pratyush Anand <panand@redhat.com>
To: Bharat Bhushan <bharat.bhushan@nxp.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Dave Young <dyoung@redhat.com>, "bhe@redhat.com" <bhe@redhat.com>,
"vgoyal@redhat.com" <vgoyal@redhat.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@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:35:04 +0530 [thread overview]
Message-ID: <3b29d230-7295-4e04-5d07-b14817ccb954@redhat.com> (raw)
In-Reply-To: <AM5PR0401MB25453F52820674F1D07EC8569AF80@AM5PR0401MB2545.eurprd04.prod.outlook.com>
On Monday 22 May 2017 12:19 PM, Bharat Bhushan wrote:
>> 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.
>
> Should I mention "-dtb" also for "Image"?
No,I think it is fine.
This documentation is representing a typical use case and so above changes is
OK for me. I think,your v2 is fine.
~Pratyush
>
> Also do we need to mention that it is optional somewhere in this document? I do not see "optional" is mentioned for other parameters and architecture.
>
> Does this looks ok:
>
> " -dtb=<optional-dtb-for-dump-capture-kernel> \"
>
> Thanks
> -Bharat
>
>>>
>>> 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
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-05-22 7:05 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
2017-05-22 6:49 ` Bharat Bhushan
2017-05-22 7:05 ` Pratyush Anand [this message]
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=3b29d230-7295-4e04-5d07-b14817ccb954@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