From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/2] KVM: arm64: Ensure VGIC is fully initialized before entering guest
Date: Thu, 17 Oct 2024 00:19:45 +0000 [thread overview]
Message-ID: <20241017001947.2707312-1-oliver.upton@linux.dev> (raw)
Fix for the race [*] that I had mentioned last week. The first patch
isn't entirely necessary, but it gets rid of a bogus check that could've
potentially raced with kvm_vgic_map_resources() as vgic_dist::ready is
no longer protected with the config_lock.
Applies to kvmarm/fixes.
Oliver Upton (2):
KVM: arm64: vgic: Don't check for vgic_ready() when setting NR_IRQS
KVM: arm64: Ensure vgic_ready() is ordered against MMIO registration
arch/arm64/kvm/vgic/vgic-init.c | 13 +++++++++++--
arch/arm64/kvm/vgic/vgic-kvm-device.c | 7 ++++++-
2 files changed, 17 insertions(+), 3 deletions(-)
base-commit: df5fd75ee305cb5927e0b1a0b46cc988ad8db2b1
--
2.47.0.rc1.288.g06298d1525-goog
next reply other threads:[~2024-10-17 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 0:19 Oliver Upton [this message]
2024-10-17 0:19 ` [PATCH 1/2] KVM: arm64: vgic: Don't check for vgic_ready() when setting NR_IRQS Oliver Upton
2024-10-17 0:19 ` [PATCH 2/2] KVM: arm64: Ensure vgic_ready() is ordered against MMIO registration Oliver Upton
2024-10-17 7:58 ` Marc Zyngier
2024-10-17 15:53 ` Oliver Upton
2024-10-17 0:22 ` [PATCH 0/2] KVM: arm64: Ensure VGIC is fully initialized before entering guest Oliver Upton
2024-10-17 8:23 ` 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=20241017001947.2707312-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--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