From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>,
Joey Gouly <joey.gouly@arm.com>, Fuad Tabba <tabba@google.com>,
Mostafa Saleh <smostafa@google.com>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: [PATCH v4 00/15] KVM/arm64: Add NV support for ERET and PAuth
Date: Fri, 19 Apr 2024 11:29:20 +0100 [thread overview]
Message-ID: <20240419102935.1935571-1-maz@kernel.org> (raw)
This is the fourth version of this series introducing ERET and PAuth
support for NV guests, and now the base prefix for the NV support
series.
Unless someone shouts, I intend to take this in for 6.10.
* From v3 [3]
- Check for NV support before checking for HCR_EL2.NV on vpcu exit
- Rebased on 6.9-rc1
* From v2 [2]
- Enforce that both Address and Generic authentication use the same
algorithm
- Reduce PAuth trapping by eagerly setting the HCR_EL2.API/APK bits
- Collected RBs, with thanks
- Rebased on kvmarm-6.9
* From v1 [1]:
- Don't repaint the ISS_ERET* definitions, but provide reasonable
helpers instead
- Dropped superfluous VNCR_EL2 definition
- Amended comments and creative spelling
[1] https://lore.kernel.org/r/20240219092014.783809-1-maz@kernel.org
[2] https://lore.kernel.org/r/20240226100601.2379693-1-maz@kernel.org
[3] https://lore.kernel.org/r/20240321155356.3236459-1-maz@kernel.org
Marc Zyngier (15):
KVM: arm64: Harden __ctxt_sys_reg() against out-of-range values
KVM: arm64: Add helpers for ESR_ELx_ERET_ISS_ERET*
KVM: arm64: Constraint PAuth support to consistent implementations
KVM: arm64: nv: Drop VCPU_HYP_CONTEXT flag
KVM: arm64: nv: Configure HCR_EL2 for FEAT_NV2
KVM: arm64: nv: Add trap forwarding for ERET and SMC
KVM: arm64: nv: Fast-track 'InHost' exception returns
KVM: arm64: nv: Honor HFGITR_EL2.ERET being set
KVM: arm64: nv: Handle HCR_EL2.{API,APK} independently
KVM: arm64: nv: Reinject PAC exceptions caused by HCR_EL2.API==0
KVM: arm64: nv: Add kvm_has_pauth() helper
KVM: arm64: nv: Add emulation for ERETAx instructions
KVM: arm64: nv: Handle ERETA[AB] instructions
KVM: arm64: nv: Advertise support for PAuth
KVM: arm64: Drop trapping of PAuth instructions/keys
arch/arm64/include/asm/esr.h | 12 ++
arch/arm64/include/asm/kvm_emulate.h | 10 --
arch/arm64/include/asm/kvm_host.h | 26 +++-
arch/arm64/include/asm/kvm_nested.h | 13 ++
arch/arm64/include/asm/kvm_ptrauth.h | 21 +++
arch/arm64/include/asm/pgtable-hwdef.h | 1 +
arch/arm64/kvm/Makefile | 1 +
arch/arm64/kvm/arm.c | 83 +++++++++-
arch/arm64/kvm/emulate-nested.c | 66 +++++---
arch/arm64/kvm/handle_exit.c | 36 ++++-
arch/arm64/kvm/hyp/include/hyp/switch.h | 62 +-------
arch/arm64/kvm/hyp/nvhe/switch.c | 4 +-
arch/arm64/kvm/hyp/vhe/switch.c | 96 +++++++++++-
arch/arm64/kvm/nested.c | 8 +-
arch/arm64/kvm/pauth.c | 196 ++++++++++++++++++++++++
15 files changed, 514 insertions(+), 121 deletions(-)
create mode 100644 arch/arm64/kvm/pauth.c
--
2.39.2
next reply other threads:[~2024-04-19 10:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 10:29 Marc Zyngier [this message]
2024-04-19 10:29 ` [PATCH v4 01/15] KVM: arm64: Harden __ctxt_sys_reg() against out-of-range values Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 02/15] KVM: arm64: Add helpers for ESR_ELx_ERET_ISS_ERET* Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 03/15] KVM: arm64: Constraint PAuth support to consistent implementations Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 04/15] KVM: arm64: nv: Drop VCPU_HYP_CONTEXT flag Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 05/15] KVM: arm64: nv: Configure HCR_EL2 for FEAT_NV2 Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 06/15] KVM: arm64: nv: Add trap forwarding for ERET and SMC Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 07/15] KVM: arm64: nv: Fast-track 'InHost' exception returns Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 08/15] KVM: arm64: nv: Honor HFGITR_EL2.ERET being set Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 09/15] KVM: arm64: nv: Handle HCR_EL2.{API,APK} independently Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 10/15] KVM: arm64: nv: Reinject PAC exceptions caused by HCR_EL2.API==0 Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 11/15] KVM: arm64: nv: Add kvm_has_pauth() helper Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 12/15] KVM: arm64: nv: Add emulation for ERETAx instructions Marc Zyngier
2024-04-23 9:22 ` Jon Hunter
2024-04-23 9:40 ` Zenghui Yu
2024-04-23 11:42 ` Marc Zyngier
2024-04-23 12:30 ` Jon Hunter
2024-04-23 12:09 ` Jon Hunter
2024-04-19 10:29 ` [PATCH v4 13/15] KVM: arm64: nv: Handle ERETA[AB] instructions Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 14/15] KVM: arm64: nv: Advertise support for PAuth Marc Zyngier
2024-04-19 10:29 ` [PATCH v4 15/15] KVM: arm64: Drop trapping of PAuth instructions/keys Marc Zyngier
2024-04-19 17:59 ` [PATCH v4 00/15] KVM/arm64: Add NV support for ERET and PAuth Oliver Upton
2024-04-20 11:49 ` Marc Zyngier
2024-04-20 12:18 ` 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=20240419102935.1935571-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=smostafa@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).