From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Simon Horman <horms@verge.net.au>
Cc: dyoung@redhat.com, Bhupesh Sharma <bhsharma@redhat.com>,
bhupesh.linux@gmail.com, kexec@lists.infradead.org,
james.morse@arm.com
Subject: Re: [PATCH v4 0/2] Add capability to dump fdt blob for arm64 platforms
Date: Wed, 25 Jul 2018 09:32:29 +0900 [thread overview]
Message-ID: <20180725003228.GB11258@linaro.org> (raw)
In-Reply-To: <20180724063110.lclgpne27o5xbws3@verge.net.au>
On Tue, Jul 24, 2018 at 08:31:54AM +0200, Simon Horman wrote:
> On Tue, Jul 17, 2018 at 02:13:42AM +0530, Bhupesh Sharma wrote:
> > Hi Akashi,
> >
> > On 07/09/2018 12:41 PM, AKASHI Takahiro wrote:
> > > Bhupesh, Simon,
> > >
> > > #I'm afraid that I gonna rehash the old discussion.
> > >
> > > Looking into ppc's kexec-tools code, I found that ppc version of
> > > this tool has a similar feature and it saves a new dtb into a file,
> > > named "debug.dtb."
> > > See save_fixed_up_dtb() in kexec/arch/ppc/fixup_dtb.c
> > >
> > > Even if it is a debug feature, we'd better go in the same way
> > > (if possible).
> >
> > Thanks for sharing the same.
> >
> > I had a look earlier also at the ppc - "debug.dtb" code in kexec-tools, but
> > this is again fails to fulfill the same purpose that we are trying to
> > resolve for early primary kernel crash(es) on arm64 machines, because of
> > which we are not able to reach the command prompt with the primary kernel
> > itself.
> >
> > We would need to either reach the command prompt to dump out/save the
> > "debug.dtb" file when we are running the primary kernel (which is
> > unfortunately not always possible wit latest kernels on some of the arm64
> > machines),
Although I'm not sure how it cannot be possible,
> or use some initramfs scriptware to dump out the same to some
> > secondary storage device (nfs server or usb stick).
> >
> > So, I would still suggest to stick with the approach I proposed for now (and
> > we can take a similar approach as ppc for arm64 later on) once we have
> > kexec, kdump and other user-space utilities (which rely on the kexec kernel
> > framework) working stably on arm64 machines (with latest upstream kernels).
>
> That sounds like a reasonable argument to me.
>
> Akashi, what do you think?
it's fine to me, too.
-Takahiro AKASHI
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2018-07-25 0:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 10:24 [PATCH v4 0/2] Add capability to dump fdt blob for arm64 platforms Bhupesh Sharma
2018-06-21 10:24 ` [PATCH v4 1/2] dt-ops: Add helper API to dump fdt blob Bhupesh Sharma
2018-06-27 12:02 ` Simon Horman
2018-06-30 20:54 ` Bhupesh Sharma
2018-06-21 10:24 ` [PATCH v4 2/2] kexec-arm64: Add functionality to dump 2nd dtb Bhupesh Sharma
2018-06-27 12:04 ` Simon Horman
2018-06-27 23:36 ` AKASHI Takahiro
2018-06-30 20:34 ` Bhupesh Sharma
2018-07-09 7:11 ` [PATCH v4 0/2] Add capability to dump fdt blob for arm64 platforms AKASHI Takahiro
2018-07-16 20:43 ` Bhupesh Sharma
2018-07-24 6:31 ` Simon Horman
2018-07-25 0:32 ` AKASHI Takahiro [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=20180725003228.GB11258@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=bhsharma@redhat.com \
--cc=bhupesh.linux@gmail.com \
--cc=dyoung@redhat.com \
--cc=horms@verge.net.au \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.