Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@armlinux.org.uk>
To: Hoeun Ryu <hoeun.ryu@gmail.com>
Cc: Matthew Leach <matthew.leach@arm.com>,
	Simon Horman <horms@verge.net.au>, Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH] kexec:arm: support zImage with appended device tree
Date: Tue, 27 Jun 2017 09:53:59 +0100	[thread overview]
Message-ID: <20170627085359.GH837@flint.armlinux.org.uk> (raw)
In-Reply-To: <1498531003.1734.13.camel@gmail.com>

On Tue, Jun 27, 2017 at 11:36:43AM +0900, Hoeun Ryu wrote:
> We have some cases when we would like to use different dtb from the
> running system when using kexec and I think that's why kexec-tools
> supports --dtb command line option.
> 
> For example, I have the second kernel for the crash dump with different
> kernel configuration and the different dtb from the running system. I'd
> like to exclude some nodes/properties from dtb like memory reservations
> or unnecessary devices to keep the second kernel/dtb minimal.
> 
> The concatenated zImage for arm has a benefit (whether it's intended or
> not) to make it possible for users to merge multiple boot images into a
> simple single file.
> What I'd like to do is just to support the concatenated zImage so that
> users can use --load(-panic) zImage_with_dtb_from_the_running_system
> instead of --load(-panic) zImage --dtb
> different_dtb_from_the_running_system.

Don't you mean --load(-panic) zImage_with_different_dtb_from_the_running_system
?

So, what you seem to be saying is that you think it's easier for the user
to do this:

# cat zImage some-other-dtb > zImage.dtb
# kexec --load-panic zImage.dtb

rather than:

# kexec --load-panic zImage --dtb some-other-dtb

?

What about the initrd?  Do you want to append that as well?

-- 
Russell King

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2017-06-27  8:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  8:55 [PATCH] kexec:arm: support zImage with appended device tree Hoeun Ryu
2017-06-26  2:52 ` Dave Young
2017-06-27  2:13   ` Hoeun Ryu
2017-06-26  9:14 ` Russell King
2017-06-27  2:36   ` Hoeun Ryu
2017-06-27  8:53     ` Russell King [this message]
2017-06-27  9:51       ` Hoeun Ryu
2017-07-03 16:41         ` Russell King
2017-07-04  1:41           ` Dave Young
2017-07-04  2:09             ` Hoeun Ryu
2017-07-04  2:09           ` Hoeun Ryu
2017-06-26  9:15 ` Pratyush Anand
2017-06-27  2:52   ` Hoeun Ryu

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=20170627085359.GH837@flint.armlinux.org.uk \
    --to=rmk@armlinux.org.uk \
    --cc=dyoung@redhat.com \
    --cc=hoeun.ryu@gmail.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=matthew.leach@arm.com \
    --cc=wangnan0@huawei.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