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 2/2] kexec-arm64: Add functionality to dump 2nd dtb
Date: Thu, 28 Jun 2018 08:36:48 +0900 [thread overview]
Message-ID: <20180627233647.GL23681@linaro.org> (raw)
In-Reply-To: <20180627120437.gdq66rfr7q2yiynd@verge.net.au>
On Wed, Jun 27, 2018 at 02:04:38PM +0200, Simon Horman wrote:
> On Thu, Jun 21, 2018 at 03:54:38PM +0530, Bhupesh Sharma wrote:
> > Since during the arm64 kexec_load()/kdump invocation,
> > the dtb is passed to the second kernel, it is sometimes useful
> > to dump the dtb contents (to verify the correctness
> > of the same).
> >
> > This patch adds this feature which is enabled when '-d' flag is
> > used with kexec command line invocation.
>
> This seems significantly more verbose than what -d already outputs.
> Perhaps a second debug level is warranted here?
+1
Debug messages on arm64 are already noisy due to ones from
machine_apply_elf_rel(), which are not very useful in most cases,
even making logs hard to understand.
Some sort of level be helpful here, too.
Thanks,
-Takahiro AKASHI
>
> >
> > Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
> > ---
> > kexec/arch/arm64/kexec-arm64.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
> > index a206c172b1aa..47df756bd595 100644
> > --- a/kexec/arch/arm64/kexec-arm64.c
> > +++ b/kexec/arch/arm64/kexec-arm64.c
> > @@ -540,6 +540,8 @@ static int setup_2nd_dtb(struct dtb *dtb, char *command_line, int on_crash)
> > dtb->buf = new_buf;
> > dtb->size = fdt_totalsize(new_buf);
> >
> > + dbgprintf("%s: found %s\n", __func__, dtb->path);
> > + dump_fdt(dtb->buf);
> > dump_reservemap(dtb);
> >
> > return result;
> > --
> > 2.7.4
> >
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-06-27 23:36 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 [this message]
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
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=20180627233647.GL23681@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox