From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Kunkun Jiang <jiangkunkun@huawei.com>,
Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/3] KVM: arm64: Fix + cleanup for GICv3 ISPENDR
Date: Tue, 19 Dec 2023 06:58:52 +0000 [thread overview]
Message-ID: <20231219065855.1019608-1-oliver.upton@linux.dev> (raw)
Here's the alternative approach I had suggested in response to Kunkun's
bug report, building the GICv3 ISPENDR accessor on top of the existing
ISPENDR / ICPENDR accessors. With these changes userspace should
consistently read / configure the hardware pending state for GICv4.1
vSGIs.
Oliver Upton (3):
KVM: arm64: vgic: Use common accessor for writes to ISPENDR
KVM: arm64: vgic: Use common accessor for writes to ICPENDR
KVM: arm64: vgic-v3: Reinterpret user ISPENDR writes as I{C,S}PENDR
arch/arm64/kvm/vgic/vgic-mmio-v3.c | 29 ++-------
arch/arm64/kvm/vgic/vgic-mmio.c | 101 ++++++++++++-----------------
2 files changed, 49 insertions(+), 81 deletions(-)
base-commit: 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab
--
2.43.0.472.g3155946c3a-goog
next reply other threads:[~2023-12-19 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 6:58 Oliver Upton [this message]
2023-12-19 6:58 ` [PATCH 1/3] KVM: arm64: vgic: Use common accessor for writes to ISPENDR Oliver Upton
2023-12-19 6:58 ` [PATCH 2/3] KVM: arm64: vgic: Use common accessor for writes to ICPENDR Oliver Upton
2023-12-19 6:58 ` [PATCH 3/3] KVM: arm64: vgic-v3: Reinterpret user ISPENDR writes as I{C,S}PENDR Oliver Upton
2023-12-22 13:03 ` [PATCH 0/3] KVM: arm64: Fix + cleanup for GICv3 ISPENDR 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=20231219065855.1019608-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=jiangkunkun@huawei.com \
--cc=kvm@vger.kernel.org \
--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