From: kazuhito.hagio@gmail.com
To: bhsharma@redhat.com, bhupesh.linux@gmail.com,
alexander.kamensky42@gmail.com, piliu@redhat.com,
kexec@lists.infradead.org
Cc: aadiga@qti.qualcomm.com, ioanna-maria.alifieraki@canonical.com
Subject: [RFC PATCH 0/4] makedumpfile/arm64: support flipped VA and 52-bit kernel VA
Date: Thu, 14 Jan 2021 17:25:05 +0900 [thread overview]
Message-ID: <1610612709-18887-1-git-send-email-kazuhito.hagio@gmail.com> (raw)
Hi Bhupesh, Alexander, Pingfan and arm64 guys,
I've rewritten Bhupesh's v5 patch [1] in order to avoid some limitations and
now this patchset
- can be built on some old arm64 environments hopefully,
- can be built on x86_64 machines with TARGET=aarch64,
- can process vmcores on different version of kernel from captured version.
Could you test this? The patchset is also on GitHub [2] and the commit
messages are to be written later.
However the following conditions are probably not supported:
- 5.11-rc is not taken into account
- 5.4 <= kernels <= 5.8 (*1)
* if PA_BITS=52 && VA_BITS!=52
* with -x option if vabits_actual=52
- kernels < 5.4 with CONFIG_ARM64_USER_VA_BITS_52=y (e.g. RHEL8 kernels)
(*1) supported with kernel commit bbdbc11804ff and 1d50e5d0c5052.
I think especially MAX_PHYSMEM_BITS cannot be guessed correctly only with
the entries in vmcoreinfo (even with Bhupesh's original patch), so basically
I would like distributions that uses 5.4 to 5.8 to backport Bhupesh's kernel
patches above if the patchset does not work well.
[1] http://lists.infradead.org/pipermail/kexec/2020-September/021336.html
[2] https://github.com/k-hagio/makedumpfile/commits/arm64.kh.test2
Kazuhito Hagio (4):
Use ELF vmcoreinfo note for --mem-usage option
arm64: use NUMBER(VA_BITS) in vmcoreinfo
Get kernel version from OSRELEASE in vmcoreinfo
arm64: support flipped VA and 52-bit kernel VA
arch/arm64.c | 155 ++++++++++++++++++++++++++++++++++++++++++++-------------
makedumpfile.c | 32 ++++++++++--
makedumpfile.h | 1 +
3 files changed, 149 insertions(+), 39 deletions(-)
--
2.9.3
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2021-01-14 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 8:25 kazuhito.hagio [this message]
2021-01-14 8:25 ` [RFC PATCH 1/4] Use ELF vmcoreinfo note for --mem-usage option kazuhito.hagio
2021-01-14 8:25 ` [RFC PATCH 2/4] arm64: use NUMBER(VA_BITS) in vmcoreinfo kazuhito.hagio
2021-01-14 8:25 ` [RFC PATCH 3/4] Get kernel version from OSRELEASE " kazuhito.hagio
2021-01-14 8:25 ` [RFC PATCH 4/4] arm64: support flipped VA and 52-bit kernel VA kazuhito.hagio
2021-01-14 10:03 ` piliu
2021-01-14 18:25 ` Bhupesh SHARMA
2021-01-15 0:40 ` HAGIO KAZUHITO(萩尾 一仁)
2021-01-15 1:41 ` piliu
2021-01-15 3:16 ` HAGIO KAZUHITO(萩尾 一仁)
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=1610612709-18887-1-git-send-email-kazuhito.hagio@gmail.com \
--to=kazuhito.hagio@gmail.com \
--cc=aadiga@qti.qualcomm.com \
--cc=alexander.kamensky42@gmail.com \
--cc=bhsharma@redhat.com \
--cc=bhupesh.linux@gmail.com \
--cc=ioanna-maria.alifieraki@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=piliu@redhat.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 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.