From: Pingfan Liu <piliu@redhat.com>
To: kexec@lists.infradead.org
Cc: Pingfan Liu <piliu@redhat.com>
Subject: [PATCH 0/3] arm64: make phys_to_virt() correct
Date: Fri, 10 Dec 2021 11:07:32 +0800 [thread overview]
Message-ID: <20211210030735.53155-1-piliu@redhat.com> (raw)
Currently phys_to_virt() does not work well on 52-bits VA arm64 kernel.
One issue is contributed by phys_offset not signed.
The other is contributed by wrong page_offset.
This series fixes them so vmcore-dmesg can work on 52-bits VA kernel
Pingfan Liu (3):
arm64: make phys_offset signed
arm64/crashdump: unify routine to get page_offset
arm64: read VA_BITS from kcore for 52-bits VA kernel
kexec/arch/arm64/crashdump-arm64.c | 23 +---------------
kexec/arch/arm64/kexec-arm64.c | 43 +++++++++++++++++++++++-------
kexec/arch/arm64/kexec-arm64.h | 4 ++-
util_lib/elf_info.c | 7 ++++-
util_lib/include/elf_info.h | 2 +-
5 files changed, 44 insertions(+), 35 deletions(-)
--
2.31.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2021-12-10 3:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 3:07 Pingfan Liu [this message]
2021-12-10 3:07 ` [PATCH 1/3] arm64: make phys_offset signed Pingfan Liu
2021-12-10 3:07 ` [PATCH 2/3] arm64/crashdump: unify routine to get page_offset Pingfan Liu
2021-12-15 13:35 ` Philipp Rudo
2021-12-16 2:58 ` Pingfan Liu
2021-12-10 3:07 ` [PATCH 3/3] arm64: read VA_BITS from kcore for 52-bits VA kernel Pingfan Liu
2021-12-15 13:34 ` Philipp Rudo
2021-12-16 2:46 ` Pingfan Liu
2021-12-16 3:05 ` Pingfan Liu
[not found] ` <20211215130557.GB4314@vergenet.net>
2021-12-16 1:59 ` Pingfan Liu
2021-12-16 11:02 ` Simon Horman
2021-12-15 1:43 ` [PATCH 0/3] arm64: make phys_to_virt() correct Pingfan Liu
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=20211210030735.53155-1-piliu@redhat.com \
--to=piliu@redhat.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