From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: Marc Zyngier <maz@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
kvmarm@lists.cs.columbia.edu
Subject: [PATCH v3 0/6] KVM: arm64: Restrict host hypercalls when pKVM is enabled
Date: Fri, 8 Oct 2021 14:58:33 +0100 [thread overview]
Message-ID: <20211008135839.1193-1-will@kernel.org> (raw)
Hi again folks,
This is version three of the patches I previously posted here:
v1: https://lore.kernel.org/r/20210923112256.15767-1-will@kernel.org
v2: https://lore.kernel.org/r/20211005113721.29441-1-will@kernel.org
Changes since v3 are:
- Included proposed cleanup (using an enum) from Marc
- Rebased onto -rc4
Cheers,
Will
Cc: Marc Zyngier <maz@kernel.org>
Cc: Quentin Perret <qperret@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: kvmarm@lists.cs.columbia.edu
--->8
Marc Zyngier (1):
KVM: arm64: Turn __KVM_HOST_SMCCC_FUNC_* into an enum (mostly)
Will Deacon (5):
arm64: Prevent kexec and hibernation if is_protected_kvm_enabled()
KVM: arm64: Reject stub hypercalls after pKVM has been initialised
KVM: arm64: Propagate errors from __pkvm_prot_finalize hypercall
KVM: arm64: Prevent re-finalisation of pKVM for a given CPU
KVM: arm64: Disable privileged hypercalls after pKVM finalisation
arch/arm64/include/asm/kvm_asm.h | 47 ++++++++++++---------
arch/arm64/kernel/smp.c | 3 +-
arch/arm64/kvm/arm.c | 61 ++++++++++++++++++---------
arch/arm64/kvm/hyp/nvhe/host.S | 26 ++++++++----
arch/arm64/kvm/hyp/nvhe/hyp-main.c | 37 +++++++++++-----
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 3 ++
6 files changed, 117 insertions(+), 60 deletions(-)
--
2.33.0.882.g93a45727a2-goog
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2021-10-08 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 13:58 Will Deacon [this message]
2021-10-08 13:58 ` [PATCH v3 1/6] KVM: arm64: Turn __KVM_HOST_SMCCC_FUNC_* into an enum (mostly) Will Deacon
2021-10-08 13:58 ` [PATCH v3 2/6] arm64: Prevent kexec and hibernation if is_protected_kvm_enabled() Will Deacon
2021-10-08 13:58 ` [PATCH v3 3/6] KVM: arm64: Reject stub hypercalls after pKVM has been initialised Will Deacon
2021-10-08 13:58 ` [PATCH v3 4/6] KVM: arm64: Propagate errors from __pkvm_prot_finalize hypercall Will Deacon
2021-10-08 13:58 ` [PATCH v3 5/6] KVM: arm64: Prevent re-finalisation of pKVM for a given CPU Will Deacon
2021-10-08 13:58 ` [PATCH v3 6/6] KVM: arm64: Disable privileged hypercalls after pKVM finalisation Will Deacon
2021-10-11 8:23 ` [PATCH v3 0/6] KVM: arm64: Restrict host hypercalls when pKVM is enabled 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=20211008135839.1193-1-will@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
/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