public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Wei-Lin Chang <weilin.chang@arm.com>
Cc: Joey Gouly <joey.gouly@arm.com>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	linux-kernel@vger.kernel.org, Oliver Upton <oupton@kernel.org>,
	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 RESEND 2/2] KVM: arm64: nv: Expose shadow page tables in debugfs
Date: Tue, 10 Mar 2026 16:50:22 +0000	[thread overview]
Message-ID: <86bjgv7ho1.wl-maz@kernel.org> (raw)
In-Reply-To: <thetpwxswabflbntrrxfsxpej4scwq25qpviv2svmbj7br3w3d@mdrrhsuexsf4>

On Tue, 10 Mar 2026 16:17:07 +0000,
Wei-Lin Chang <weilin.chang@arm.com> wrote:
> 
> On Tue, Mar 10, 2026 at 03:26:04PM +0000, Joey Gouly wrote:

> > > diff --git a/arch/arm64/include/asm/kvm_host.h b/arch/arm64/include/asm/kvm_host.h
> > > index 5d5a3bbdb95e..f88f6c4d646e 100644
> > > --- a/arch/arm64/include/asm/kvm_host.h
> > > +++ b/arch/arm64/include/asm/kvm_host.h
> > > @@ -217,6 +217,10 @@ struct kvm_s2_mmu {
> > >  	 */
> > >  	bool	nested_stage2_enabled;
> > >  
> > > +#ifdef CONFIG_PTDUMP_STAGE2_DEBUGFS
> > > +	struct dentry *shadow_pt_debugfs_dentry;
> > > +#endif
> > > +
> > >  	/*
> > >  	 * true when this MMU needs to be unmapped before being used for a new
> > >  	 * purpose.
> > > @@ -405,6 +409,9 @@ struct kvm_arch {
> > >  	 * the associated pKVM instance in the hypervisor.
> > >  	 */
> > >  	struct kvm_protected_vm pkvm;
> > > +
> > > +	/* Nested virtualization info */
> > > +	struct dentry *debugfs_nv_dentry;
> > 
> > Seems like this could be guarded with CONFIG_PTDUMP_STAGE2_DEBUGFS too, or is
> > there a reason you didn't?
> 
> Right, I was thinking this "nested" directory can also hold other NV
> related information in the future, that's why I didn't keep it behind
> the option.

We can cross that bridge when we get there. In the meantime, I'd side
with Joey and would rather not have a dangling pointer.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2026-03-10 16:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 23:18 [PATCH RESEND 0/2] KVM: arm64: nv: Expose shadow page tables in debugfs Wei-Lin Chang
2026-03-08 23:18 ` [PATCH RESEND 1/2] KVM: arm64: ptdump: Make KVM ptdump code s2 mmu aware Wei-Lin Chang
2026-03-08 23:18 ` [PATCH RESEND 2/2] KVM: arm64: nv: Expose shadow page tables in debugfs Wei-Lin Chang
2026-03-10 15:26   ` Joey Gouly
2026-03-10 16:17     ` Wei-Lin Chang
2026-03-10 16:50       ` Marc Zyngier [this message]
2026-03-10 17:41         ` Wei-Lin Chang
2026-03-11 15:41   ` Sebastian Ene
2026-03-13 22:28     ` Wei-Lin Chang
2026-03-14  9:39       ` Marc Zyngier
2026-03-16 10:52         ` Wei-Lin Chang

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=86bjgv7ho1.wl-maz@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