From: Marc Zyngier <maz@kernel.org>
To: Itaru Kitayama <itaru.kitayama@fujitsu.com>
Cc: Wei-Lin Chang <weilin.chang@arm.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, 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 v3 0/5] KVM: arm64: nv: Implement nested stage-2 reverse map
Date: Thu, 28 May 2026 11:19:34 +0100 [thread overview]
Message-ID: <86fr3bvnt5.wl-maz@kernel.org> (raw)
In-Reply-To: <ag1jQB3dRX0RSqbR@sm-arm-grace07>
On Wed, 20 May 2026 08:31:12 +0100,
Itaru Kitayama <itaru.kitayama@fujitsu.com> wrote:
>
> Hi Wei Lin,
>
> On Sun, May 10, 2026 at 03:53:33PM +0100, Wei-Lin Chang wrote:
> > Hi,
> >
> > This is v3 of optimizing the shadow s2 mmu unmapping during MMU
> > notifiers.
> >
> > Two new preparatory patches are added, one reduces a hole in kvm_s2_mmu
> > and another refactors the code a bit during s2 faults. Other changes are
> > listed below.
> >
> > * Changes from v2 [1]:
> >
> > - Removed "polluted" teminology.
> >
> > - Use xa_{mk, to}_value() when storing and retriving values from maple
> > trees.
> >
> > - Avoid using the 63rd bit in maple tree values so that xa_{mk, to}_value()
> > does not lose us a bit.
> >
> > - Added reverse map removal during TLBI handling.
> >
> > - Other suggested refactorings.
> >
> > Thanks!
>
> With this series applied on the recent kvmarm/fixes (minor local modification),
> your v3 hello_nested runs fine on all three page granules; without this 16KB
> kernel can't handle stage 2 unmapping paths. I tested using the latest QEMU only
> so wonder how you're testing.
Can you clarify this statement?
Are you saying that 16kB S2 unmap do not work with upstream? That
seems odd, as it would mean NV wouldn't work on Apple HW, which
represents two thirds of my development boxes...
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-05-28 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 14:53 [PATCH v3 0/5] KVM: arm64: nv: Implement nested stage-2 reverse map Wei-Lin Chang
2026-05-10 14:53 ` [PATCH v3 1/5] KVM: arm64: Use a variable for the canonical GPA in kvm_s2_fault_map() Wei-Lin Chang
2026-05-10 14:53 ` [PATCH v3 2/5] KVM: arm64: Move shadow_pt_debugfs_dentry to reduce holes in kvm_s2_mmu Wei-Lin Chang
2026-05-10 14:53 ` [PATCH v3 3/5] KVM: arm64: nv: Avoid full shadow s2 unmap Wei-Lin Chang
2026-05-28 12:59 ` Marc Zyngier
2026-05-10 14:53 ` [PATCH v3 4/5] KVM: arm64: nv: Remove reverse map entries during TLBI handling Wei-Lin Chang
2026-05-10 14:53 ` [PATCH v3 5/5] KVM: arm64: nv: Create nested IPA direct map to speed up reverse map removal Wei-Lin Chang
2026-05-20 7:31 ` [PATCH v3 0/5] KVM: arm64: nv: Implement nested stage-2 reverse map Itaru Kitayama
2026-05-28 10:19 ` 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=86fr3bvnt5.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=itaru.kitayama@fujitsu.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