From: Karl Mehltretter <kmehltretter@gmail.com>
To: Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
kvmarm@lists.linux.dev
Cc: Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Eric Auger <eric.auger@redhat.com>,
Christoffer Dall <christoffer.dall@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 0/4] KVM: arm64: fix VGICv3 redistributor rollback
Date: Fri, 2 Oct 2026 19:45:21 +0200 [thread overview]
Message-ID: <ar_tdaYQO-t1K2F_@gmail.com> (raw)
In-Reply-To: <20260831081005.41346-1-kmehltretter@gmail.com>
On Mon, Aug 31, 2026 at 10:10:00AM +0100, Karl Mehltretter wrote:
> Changes since v3:
> - Dropped the REDIST/REDIST_REGION serialization and VGIC init/destroy
> rework, keeping the fix close to v2. (Marc)
> - Limited rollback to assignments from the new region so an older-region
> assignment cannot be missed during concurrent vCPU creation.
> - Added Fuad's Reviewed-by tags to patches 1, 3 and 4. These are otherwise
> unchanged from v3 (formerly patches 1, 4 and 5).
>
> Previous version:
> v3: https://lore.kernel.org/r/20260822095346.53882-1-kmehltretter@gmail.com
>
> Karl Mehltretter (4):
> KVM: arm64: vgic-v3: Undo assignment on iodev registration failure
> KVM: arm64: vgic-v3: Roll back assignments from the new region
> KVM: arm64: selftests: Pass guest code to vm_gic_create_with_vcpus()
> KVM: arm64: selftests: Test VGICv3 redistributor region retry
>
> arch/arm64/kvm/vgic/vgic-mmio-v3.c | 54 ++++++--
> tools/testing/selftests/kvm/arm64/vgic_init.c | 116 ++++++++++++++++--
> 2 files changed, 151 insertions(+), 19 deletions(-)
A friendly ping on v4. Patches 1, 3, and 4 have Fuad's Reviewed-by;
patch 2 was revised following Marc's feedback.
Thanks,
Karl
next prev parent reply other threads:[~2026-10-02 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 8:10 Karl Mehltretter
2026-08-31 8:10 ` [PATCH v4 1/4] KVM: arm64: vgic-v3: Undo assignment on iodev registration failure Karl Mehltretter
2026-08-31 8:10 ` [PATCH v4 2/4] KVM: arm64: vgic-v3: Roll back assignments from the new region Karl Mehltretter
2026-08-31 8:10 ` [PATCH v4 3/4] KVM: arm64: selftests: Pass guest code to vm_gic_create_with_vcpus() Karl Mehltretter
2026-08-31 8:10 ` [PATCH v4 4/4] KVM: arm64: selftests: Test VGICv3 redistributor region retry Karl Mehltretter
2026-10-02 17:45 ` Karl Mehltretter [this message]
2026-10-03 12:08 ` [PATCH v4 0/4] KVM: arm64: fix VGICv3 redistributor rollback Marc Zyngier
2026-10-03 12:09 ` Marc Zyngier
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=ar_tdaYQO-t1K2F_@gmail.com \
--to=kmehltretter@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=eric.auger@redhat.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seiden@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@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®