From: Bhupesh Sharma <bhsharma@redhat.com>
To: kexec@lists.infradead.org
Cc: Bhupesh Sharma <bhsharma@redhat.com>,
takahiro.akashi@linaro.org, horms@verge.net.au,
james.morse@arm.com, bhupesh.linux@gmail.com, dyoung@redhat.com
Subject: [PATCH v3 2/2] kexec-arm64: Add functionality to dump 2nd dtb
Date: Mon, 30 Apr 2018 02:52:36 +0530 [thread overview]
Message-ID: <1525036956-7440-3-git-send-email-bhsharma@redhat.com> (raw)
In-Reply-To: <1525036956-7440-1-git-send-email-bhsharma@redhat.com>
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.
Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
---
kexec/arch/arm64/kexec-arm64.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kexec/arch/arm64/kexec-arm64.c b/kexec/arch/arm64/kexec-arm64.c
index 62f37585b788..1b54718465b9 100644
--- a/kexec/arch/arm64/kexec-arm64.c
+++ b/kexec/arch/arm64/kexec-arm64.c
@@ -477,9 +477,10 @@ static int setup_2nd_dtb(struct dtb *dtb, char *command_line, int on_crash)
dtb->size = fdt_totalsize(new_buf);
}
+ dbgprintf("%s: found %s\n", __func__, dtb->path);
+ dump_fdt(dtb->buf);
dump_reservemap(dtb);
-
return result;
on_error:
--
2.7.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2018-04-29 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 21:22 [PATCH v3 0/2] Add capability to dump fdt blob for arm64 platforms Bhupesh Sharma
2018-04-29 21:22 ` [PATCH v3 1/2] dt-ops: Add helper API to dump fdt blob Bhupesh Sharma
2018-05-08 2:14 ` AKASHI Takahiro
2018-06-20 10:29 ` Bhupesh Sharma
2018-06-21 8:00 ` Bhupesh Sharma
2018-04-29 21:22 ` Bhupesh Sharma [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=1525036956-7440-3-git-send-email-bhsharma@redhat.com \
--to=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 \
--cc=takahiro.akashi@linaro.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