From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org
Cc: Eric Auger <eric.auger@redhat.com>,
Ricardo Koller <ricarkol@google.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Oliver Upton <oupton@google.com>,
kernel-team@android.com
Subject: [PATCH v2 0/3] KVM: arm64: Fix userspace access to HW pending state
Date: Tue, 7 Jun 2022 14:14:24 +0100 [thread overview]
Message-ID: <20220607131427.1164881-1-maz@kernel.org> (raw)
This is a followup from [1], which aims at fixing userspace access to
interrupt pending state for HW interrupts.
* From v1 [1]:
- Keep some of the GICv3-specifics around to avoid regressing the
line vs latch distinction (Eric).
[1] https://lore.kernel.org/r/20220602083025.1110433-1-maz@kernel.org
Marc Zyngier (3):
KVM: arm64: Don't read a HW interrupt pending state in user context
KVM: arm64: Replace vgic_v3_uaccess_read_pending with
vgic_uaccess_read_pending
KVM: arm64: Warn if accessing timer pending state outside of vcpu
context
arch/arm64/kvm/arch_timer.c | 3 +++
arch/arm64/kvm/vgic/vgic-mmio-v2.c | 4 +--
arch/arm64/kvm/vgic/vgic-mmio-v3.c | 40 ++----------------------------
arch/arm64/kvm/vgic/vgic-mmio.c | 40 +++++++++++++++++++++++++++---
arch/arm64/kvm/vgic/vgic-mmio.h | 3 +++
5 files changed, 46 insertions(+), 44 deletions(-)
--
2.34.1
next reply other threads:[~2022-06-07 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:14 Marc Zyngier [this message]
2022-06-07 13:14 ` [PATCH v2 1/3] KVM: arm64: Don't read a HW interrupt pending state in user context Marc Zyngier
2022-06-07 13:14 ` [PATCH v2 2/3] KVM: arm64: Replace vgic_v3_uaccess_read_pending with vgic_uaccess_read_pending Marc Zyngier
2022-06-07 19:28 ` Eric Auger
2022-06-07 13:14 ` [PATCH v2 3/3] KVM: arm64: Warn if accessing timer pending state outside of vcpu context Marc Zyngier
2022-06-07 15:27 ` (subset) [PATCH v2 0/3] KVM: arm64: Fix userspace access to HW pending state 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=20220607131427.1164881-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@google.com \
--cc=ricarkol@google.com \
--cc=suzuki.poulose@arm.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