From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org,
Wei-Lin Chang <weilin.chang@arm.com>
Cc: Oliver Upton <oupton@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2 0/2] KVM: arm64: nv: Expose shadow page tables in debugfs
Date: Mon, 23 Mar 2026 10:30:54 +0000 [thread overview]
Message-ID: <177426184180.2895807.211946324243843322.b4-ty@kernel.org> (raw)
In-Reply-To: <20260317182638.1592507-1-weilin.chang@arm.com>
On Tue, 17 Mar 2026 18:26:36 +0000, Wei-Lin Chang wrote:
> This is v2 of exposing shadow page tables in debugfs, there are a few
> small improvements, please see below.
>
> Changes in v2:
> - move debugfs_nv_dentry also behind CONFIG_PTDUMP_STAGE2_DEBUGFS
> - use a macro to define the file names of shadow ptdumps, also
> explicitly spell out the string to get its maximum size
> - add Reviewed-by tag from Sebastian (thanks!)
> - Link to v1: https://lore.kernel.org/kvmarm/20260308231829.864983-1-weilin.chang@arm.com/
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: ptdump: Make KVM ptdump code s2 mmu aware
commit: 204f7c018d76c2488a90fc6681519b8eb6eebb1d
[2/2] KVM: arm64: nv: Expose shadow page tables in debugfs
commit: 19e15dc73f0fc74eaf63ad9b3a50648450269b4d
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-03-23 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 18:26 Wei-Lin Chang
2026-03-17 18:26 ` [PATCH v2 1/2] KVM: arm64: ptdump: Make KVM ptdump code s2 mmu aware Wei-Lin Chang
2026-03-17 18:26 ` [PATCH v2 2/2] KVM: arm64: nv: Expose shadow page tables in debugfs Wei-Lin Chang
2026-03-19 16:01 ` Marc Zyngier
2026-03-21 16:36 ` Wei-Lin Chang
2026-06-12 4:06 ` Itaru Kitayama
2026-06-12 13:41 ` Wei-Lin Chang
2026-03-18 11:42 ` [PATCH v2 0/2] " Joey Gouly
2026-03-23 10:30 ` Marc Zyngier [this message]
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=177426184180.2895807.211946324243843322.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oupton@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®