From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alexandre.ghiti@canonical.com,
guoren@kernel.org, anup@brainfault.org, mick@ics.forth.gr,
rppt@kernel.org, heiko@sntech.de
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
huanyi.xj@alibaba-inc.com,
Xianting Tian <xianting.tian@linux.alibaba.com>
Subject: [PATCH V2 0/2] Improve vmcoreinfo and memory layout dump
Date: Thu, 14 Jul 2022 10:58:59 +0800 [thread overview]
Message-ID: <20220714025901.359695-1-xianting.tian@linux.alibaba.com> (raw)
This patch series are the improvements for vmcoreinfo and memory
layout dump.
The first patch(1/2) is to add VM layout to vmcoreinfo, which can
simlify the development of crash tool as ARM64 already did
(arch/arm64/kernel/crash_core.c).
The second patch(2/2) is to add MODULES to memory layout dump.
Changes v1 -> v2:
patch 1: add VA_BITS to vmcoreinfo as ARM64 does, not satp_mode.
crash tool can read VA_BITS to determin the pagetable
levels.
patch 1,2: As MODULES area is only defined when CONFIG_64BIT=y for
riscv64, so only use MODULES area when CONFIG_64BIT=y.
Xianting Tian (2):
RISC-V: Add arch_crash_save_vmcoreinfo support
riscv: Add modules to virtual kernel memory layout dump
arch/riscv/kernel/Makefile | 1 +
arch/riscv/kernel/crash_core.c | 28 ++++++++++++++++++++++++++++
arch/riscv/mm/init.c | 3 +++
3 files changed, 32 insertions(+)
create mode 100644 arch/riscv/kernel/crash_core.c
--
2.17.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-07-14 2:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 2:58 Xianting Tian [this message]
2022-07-14 2:59 ` [PATCH V2 1/2] RISC-V: Add arch_crash_save_vmcoreinfo support Xianting Tian
2022-07-14 2:59 ` [PATCH V2 2/2] riscv: Add modules to virtual kernel memory layout dump Xianting Tian
2022-07-14 8:24 ` Arnd Bergmann
2022-07-14 9:17 ` Xianting Tian
2022-07-14 9:46 ` Heiko Stübner
2022-07-14 11:06 ` Xianting Tian
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=20220714025901.359695-1-xianting.tian@linux.alibaba.com \
--to=xianting.tian@linux.alibaba.com \
--cc=alexandre.ghiti@canonical.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=huanyi.xj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@kernel.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