From: Bhupesh Sharma <bhsharma@redhat.com>
To: kexec@lists.infradead.org
Cc: John Donnelly <john.p.donnelly@oracle.com>,
bhsharma@redhat.com, bhupesh.linux@gmail.com,
Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Subject: [PATCH v4 4/4] makedumpfile: Mark --mem-usage option unsupported for arm64
Date: Tue, 12 Nov 2019 16:38:59 +0530 [thread overview]
Message-ID: <1573556939-17803-5-git-send-email-bhsharma@redhat.com> (raw)
In-Reply-To: <1573556939-17803-1-git-send-email-bhsharma@redhat.com>
This patch marks '--mem-usage' option as unsupported for arm64
architecture.
With the newer arm64 kernels supporting 48-bit/52-bit VA address spaces
and keeping a single binary for supporting the same, the address of
kernel symbols like _stext which could be earlier used to determine
VA_BITS value, can no longer to determine whether VA_BITS is set to 48
or 52 in the kernel space.
Hence for now, it makes sense to mark '--mem-usage' option as
unsupported for arm64 architecture until we have more clarity from arm64
kernel maintainers on how to manage the same in future
kernel/makedumpfile versions.
Cc: John Donnelly <john.p.donnelly@oracle.com>
Cc: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Cc: kexec@lists.infradead.org
Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
---
makedumpfile.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/makedumpfile.c b/makedumpfile.c
index baf559e4d74e..ae60466a1e9c 100644
--- a/makedumpfile.c
+++ b/makedumpfile.c
@@ -11564,6 +11564,11 @@ main(int argc, char *argv[])
MSG("\n");
MSG("The dmesg log is saved to %s.\n", info->name_dumpfile);
} else if (info->flag_mem_usage) {
+#ifdef __aarch64__
+ MSG("mem-usage not supported for arm64 architecure.\n");
+ goto out;
+#endif
+
if (!check_param_for_creating_dumpfile(argc, argv)) {
MSG("Commandline parameter is invalid.\n");
MSG("Try `makedumpfile --help' for more information.\n");
--
2.7.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-11-12 11:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 11:08 [PATCH v4 0/4] makedumpfile/arm64: Add support for ARMv8.2 extensions Bhupesh Sharma
2019-11-12 11:08 ` [PATCH v4 1/4] tree-wide: Retrieve 'MAX_PHYSMEM_BITS' from vmcoreinfo (if available) Bhupesh Sharma
2019-12-04 17:34 ` Kazuhito Hagio
2019-12-05 18:17 ` Bhupesh Sharma
2019-12-05 20:41 ` Kazuhito Hagio
2019-11-12 11:08 ` [PATCH v4 2/4] makedumpfile/arm64: Add support for ARMv8.2-LPA (52-bit PA support) Bhupesh Sharma
2019-12-04 17:36 ` Kazuhito Hagio
2019-12-05 18:21 ` Bhupesh Sharma
2019-12-05 20:45 ` Kazuhito Hagio
2019-11-12 11:08 ` [PATCH v4 3/4] makedumpfile/arm64: Add support for ARMv8.2-LVA (52-bit kernel VA support) Bhupesh Sharma
2019-12-04 17:45 ` Kazuhito Hagio
2019-12-05 15:29 ` Kazuhito Hagio
2019-12-05 18:05 ` Bhupesh Sharma
2019-12-05 20:49 ` Kazuhito Hagio
2019-11-12 11:08 ` Bhupesh Sharma [this message]
2019-12-04 17:49 ` [PATCH v4 4/4] makedumpfile: Mark --mem-usage option unsupported for arm64 Kazuhito Hagio
2019-12-05 18:24 ` Bhupesh Sharma
2019-11-13 21:59 ` [PATCH v4 0/4] makedumpfile/arm64: Add support for ARMv8.2 extensions Kazuhito Hagio
2019-11-14 19:10 ` Bhupesh Sharma
2019-11-18 5:12 ` Prabhakar Kushwaha
2019-11-18 17:11 ` John Donnelly
2019-11-18 19:01 ` Bhupesh Sharma
2019-11-18 19:12 ` John Donnelly
2019-11-18 20:00 ` John Donnelly
2019-11-20 16:33 ` John Donnelly
2019-11-21 16:32 ` Bhupesh Sharma
2019-11-21 16:59 ` John Donnelly
2019-11-21 19:20 ` John Donnelly
2019-11-21 21:52 ` John Donnelly
2019-11-22 12:30 ` John Donnelly
2019-11-22 14:22 ` John Donnelly
2019-12-05 20:59 ` Kazuhito Hagio
2019-12-10 14:50 ` Kazuhito Hagio
2019-11-18 18:56 ` Bhupesh Sharma
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=1573556939-17803-5-git-send-email-bhsharma@redhat.com \
--to=bhsharma@redhat.com \
--cc=bhupesh.linux@gmail.com \
--cc=john.p.donnelly@oracle.com \
--cc=k-hagio@ab.jp.nec.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