From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v3 0/6] KVM: arm64: Restrict host hypercalls when pKVM is enabled
Date: Mon, 11 Oct 2021 09:23:03 +0100 [thread overview]
Message-ID: <163394056714.532004.7796153574955915700.b4-ty@kernel.org> (raw)
In-Reply-To: <20211008135839.1193-1-will@kernel.org>
On Fri, 8 Oct 2021 14:58:33 +0100, Will Deacon wrote:
> 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:
>
> [...]
Applied to next, thanks!
[1/6] KVM: arm64: Turn __KVM_HOST_SMCCC_FUNC_* into an enum (mostly)
commit: a78738ed1d9bf40d09109599b884508c69d188b8
[2/6] arm64: Prevent kexec and hibernation if is_protected_kvm_enabled()
commit: 8f4566f18db5d1257fc2d5442e16274424a529c1
[3/6] KVM: arm64: Reject stub hypercalls after pKVM has been initialised
commit: 8579a185bacaa64c65e43e251ceede2f7600f7e2
[4/6] KVM: arm64: Propagate errors from __pkvm_prot_finalize hypercall
commit: 2f2e1a5069679491d18cf9021da19b40c56a17f3
[5/6] KVM: arm64: Prevent re-finalisation of pKVM for a given CPU
commit: 07036cffe17ec07e8fb630d86f8ea21832d9e57d
[6/6] KVM: arm64: Disable privileged hypercalls after pKVM finalisation
commit: 057bed206f70d624c2eacb43ec56551950a26832
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2021-10-11 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 13:58 [PATCH v3 0/6] KVM: arm64: Restrict host hypercalls when pKVM is enabled Will Deacon
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 ` Marc Zyngier [this message]
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=163394056714.532004.7796153574955915700.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@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