From: "Dylan.Wu" <fredwudi0305@gmail.com>
To: paul.walmsley@sifive.com, pjw@kernel.org
Cc: palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
anup@brainfault.org, atish.patra@linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm-riscv@lists.infradead.org, kvm@vger.kernel.org,
"Dylan.Wu" <fredwudi0305@gmail.com>
Subject: [PATCH v3 0/3] RISC-V KVM gstage page table dumper
Date: Tue, 28 Jul 2026 12:14:46 -0400 [thread overview]
Message-ID: <20260728161449.190058-1-fredwudi0305@gmail.com> (raw)
In-Reply-To: <3bb2f519-c70b-6c35-c404-6fbfe8adbeb1@kernel.org>
This series adds support for dumping RISC-V KVM gstage (second-stage)
page tables via debugfs, allowing inspection of the guest physical
address translation setup.
Changes since v2:
- Split the first patch into two as requested by Paul Walmsley:
Patch 1 now only creates ptdump.h and moves declarations there
with no functional changes (structures moved verbatim).
Patch 2 handles the structure renames and per-level attribute
bit parsing logic.
Patch 1: Create ptdump.h and move declarations
Patch 2: Use per-level attribute bits for parsing
Patch 3: Register gstage ptdump with debugfs on guest creation
Dylan.Wu (3):
riscv: ptdump: Create ptdump.h and move declarations
riscv: ptdump: Use per-level attribute bits for parsing
KVM: riscv: Register ptdump with debugfs on guest creation
arch/riscv/include/asm/ptdump.h | 43 ++++++++
arch/riscv/kvm/Kconfig | 12 +++
arch/riscv/kvm/Makefile | 1 +
arch/riscv/kvm/ptdump.c | 177 ++++++++++++++++++++++++++++++++
arch/riscv/mm/ptdump.c | 106 ++++++++-----------
5 files changed, 275 insertions(+), 64 deletions(-)
create mode 100644 arch/riscv/include/asm/ptdump.h
create mode 100644 arch/riscv/kvm/ptdump.c
--
2.34.1
next prev parent reply other threads:[~2026-07-28 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 8:50 [PATCH 0/2] riscv: ptdump: Refactor for KVM gstage ptdump support Dylan.Wu
2026-07-01 8:50 ` [PATCH 1/2] riscv: ptdump: Move pagetable definitions to common header Dylan.Wu
2026-07-01 9:01 ` sashiko-bot
2026-07-21 2:58 ` Paul Walmsley
2026-07-27 12:39 ` Dylan.Wu
2026-07-28 16:14 ` Dylan.Wu [this message]
2026-07-28 16:14 ` [PATCH v3 1/3] riscv: ptdump: Create ptdump.h and move declarations Dylan.Wu
2026-07-28 16:26 ` sashiko-bot
2026-07-28 16:14 ` [PATCH v3 2/3] riscv: ptdump: Use per-level attribute bits for parsing Dylan.Wu
2026-07-28 16:31 ` sashiko-bot
2026-07-28 16:14 ` [PATCH v3 3/3] KVM: riscv: Register ptdump with debugfs on guest creation Dylan.Wu
2026-07-28 16:50 ` sashiko-bot
2026-07-01 8:50 ` [PATCH 2/2] " Dylan.Wu
2026-07-01 9:06 ` sashiko-bot
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=20260728161449.190058-1-fredwudi0305@gmail.com \
--to=fredwudi0305@gmail.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@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