Re: [PATCH v1 00/10] KVM: arm64: Nested stage-2 walk error handling and other small fixes

[Marc Zyngier]

On Mon, 28 Sep 2026 16:24:57 +0100,
Fuad Tabba <fuad.tabba@xxxxxxxxx> wrote:
> 
> Hi folks,
> 
> Small KVM/arm64 fixes that came out of reviewing Karl's SMCCC filter
> series [1], and it just kept growing.
> 
> The first two are WARNs that userspace or a guest can trigger: the
> SMCCC filter one on an allocation failure userspace can force with a
> memory cgroup limit, which Sashiko raised [2], the nested one when an
> L1 guest programs an invalid VTCR_EL2. Patches 3 and 4 are the same
> walk's return values. With an invalid VTCR_EL2 or a stage-2 descriptor
> KVM can't read, AT S12E{0,1}{R,W} was retried forever instead of
> retiring with the fault in PAR_EL1. Reporting the unreadable descriptor
> as a Data Abort instead, for the stage-1 walks too, is a separate
> change I'll send later.

Why later?

> Patch 5 extends the AT selftest to cover the
> SL0 case.
> 
> The three documentation patches fix identifiers in api.rst that don't
> exist anywhere in the tree, and the last two fix selftest leaks.

<rant>
What is this series about? Suppressing spurious warnings? Fixing the
PTWs?  Fixing the documentation for something totally unrelated?
Random selftest maintenance?

To give you an idea, here's what my -next branch looks like:

maz@valley-girl:~/hot-poop/arm-platforms$ git log --oneline --merges v7.3-rc3..kvmarm-master/next
5c49bb52faf38 Merge branch kvm-arm64/misc-7.4 into kvmarm-master/next
c345ec7f39efd Merge branch kvm-arm64/pre-faulting into kvmarm-master/next
2716832906bd9 Merge branch kvm-arm64/s2-rmap into kvmarm-master/next
edeb68e3d4e0c Merge tag 'kvmarm-fixes-7.3-1' into kvm-arm64/s2-rmap
ede721366f1bf Merge branch kvm-arm64/gicv5-7.4 into kvmarm-master/next
062cbcbae3e00 Merge branch kvm-arm64/gicv5-7.4 into kvmarm-master/next
928737a70c491 Merge branch kvm-arm64/hyp-type-checking-7.4 into kvmarm-master/next
1f99916b2a3d7 Merge branch kvm-arm64/selftests-7.4 into kvmarm-master/next
a8f9576fa8466 Merge branch kvm-arm64/doc-7.4 into kvmarm-master/next
7413af8a61612 Merge branch kvm-arm64/ffa-7.4 into kvmarm-master/next

Where does this series fit? What is the theme? Do you really expect me
to cherry-pick one patch after the other and build 3 or 4 consistent
series out of this? Or should simply apply it as kvm-arm64/random-stuff-from-fuad-7.4?

My definition of a series is "an ordered set of changes that have a
common theme or form a progression towards a precise goal". This is
not a series, but a patch dump.
</rant>

	M.

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