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>,
Raghavendra Rao Ananta <rananta@google.com>,
Ben Horgan <ben.horgan@arm.com>,
Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH v2 0/4] KVM: arm64: Add attribute to control GICD_TYPER2.nASSGIcap
Date: Fri, 30 May 2025 18:25:41 -0700 [thread overview]
Message-ID: <20250531012545.709887-1-oliver.upton@linux.dev> (raw)
Raghu, I applied this locally for review and wound up changing enough
things to where it was easier just to repost. Sorry, hope you don't
mind.
v1: https://lore.kernel.org/kvmarm/20250514192159.1751538-1-rananta@google.com/
v1 -> v2:
- Drop all use of GICv4 in the UAPI and KVM-internal helpers in favor
of nASSGIcap. This changes things around to model a guest feature,
not a host feature.
- Consolidate UAPI into a single attribute and expect userspace to use
to read the attribute for discovery, much like we do with the ID
registers
- Squash documentation together with implementation
- Clean up maintenance IRQ attribute handling, which I ran into as part
of reviewing this series
Oliver Upton (2):
KVM: arm64: Disambiguate support for vSGIs v. vLPIs
KVM: arm64: vgic-v3: Consolidate MAINT_IRQ handling
Raghavendra Rao Ananta (2):
KVM: arm64: Introduce attribute to control GICD_TYPER2.nASSGIcap
KVM: arm64: selftests: Add test for nASSGIcap attribute
.../virt/kvm/devices/arm-vgic-v3.rst | 29 ++++++
arch/arm64/include/uapi/asm/kvm.h | 3 +
arch/arm64/kvm/vgic/vgic-init.c | 7 +-
arch/arm64/kvm/vgic/vgic-kvm-device.c | 88 +++++++++++++------
arch/arm64/kvm/vgic/vgic-mmio-v3.c | 24 +++--
arch/arm64/kvm/vgic/vgic-v4.c | 4 +-
arch/arm64/kvm/vgic/vgic.c | 4 +-
arch/arm64/kvm/vgic/vgic.h | 7 ++
include/kvm/arm_vgic.h | 3 +
tools/testing/selftests/kvm/arm64/vgic_init.c | 41 +++++++++
10 files changed, 172 insertions(+), 38 deletions(-)
base-commit: 1b85d923ba8c9e6afaf19e26708411adde94fba8
--
2.39.5
next reply other threads:[~2025-05-31 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 1:25 Oliver Upton [this message]
2025-05-31 1:25 ` [PATCH v2 1/4] KVM: arm64: Disambiguate support for vSGIs v. vLPIs Oliver Upton
2025-05-31 1:25 ` [PATCH v2 2/4] KVM: arm64: vgic-v3: Consolidate MAINT_IRQ handling Oliver Upton
2025-05-31 1:25 ` [PATCH v2 3/4] KVM: arm64: Introduce attribute to control GICD_TYPER2.nASSGIcap Oliver Upton
2025-06-03 18:33 ` Raghavendra Rao Ananta
2025-06-03 19:03 ` Oliver Upton
2025-05-31 1:25 ` [PATCH v2 4/4] KVM: arm64: selftests: Add test for nASSGIcap attribute Oliver Upton
2025-06-03 18:42 ` Raghavendra Rao Ananta
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=20250531012545.709887-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=ben.horgan@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=rananta@google.com \
--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