From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
kvm@vger.kernel.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>
Subject: [PATCH 0/2] KVM/arm64 fixes for NV PAC support
Date: Tue, 28 May 2024 11:06:30 +0100 [thread overview]
Message-ID: <20240528100632.1831995-1-maz@kernel.org> (raw)
Here's a small series of fixes following the introduction of NV PAuth
support in 6.10:
- address the relative priorities of Instruction abort, Illegal
Execution state, and PAC failure (already posted)
- Expose BTI to a NV guest now that we have PAC up and running
Unless someone shouts, I'll take these patches in the next batch of
fixes.
M.
Marc Zyngier (2):
KVM: arm64: nv: Fix relative priorities of exceptions generated by
ERETAx
KVM: arm64: nv: Expose BTI and CSV_frac to a guest hypervisor
arch/arm64/kvm/emulate-nested.c | 21 +++++++++++----------
arch/arm64/kvm/nested.c | 6 ++++--
2 files changed, 15 insertions(+), 12 deletions(-)
--
2.39.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-05-28 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 10:06 Marc Zyngier [this message]
2024-05-28 10:06 ` [PATCH 1/2] KVM: arm64: nv: Fix relative priorities of exceptions generated by ERETAx Marc Zyngier
2024-05-29 14:27 ` Joey Gouly
2024-05-29 14:44 ` Marc Zyngier
2024-05-28 10:06 ` [PATCH 2/2] KVM: arm64: nv: Expose BTI and CSV_frac to a guest hypervisor Marc Zyngier
2024-05-30 7:58 ` [PATCH 0/2] KVM/arm64 fixes for NV PAC support Oliver Upton
2024-05-30 16:37 ` 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=20240528100632.1831995-1-maz@kernel.org \
--to=maz@kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).