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 v2 0/5] KVM: arm64: Restrict host hypercalls when pKVM is enabled
Date: Tue, 5 Oct 2021 12:37:16 +0100 [thread overview]
Message-ID: <20211005113721.29441-1-will@kernel.org> (raw)
Hi all,
This is version two of the patches I previously posted here:
https://lore.kernel.org/r/20210923112256.15767-1-will@kernel.org
Changes since v2 include:
- Add a comment about pkvm_prot_finalize() returning -EPERM
- Fixed ordering of hypercalls in 'host_hcall' array
- Added reviewed-by tags
Patches based on -rc2. Feedback welcome.
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
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 | 43 ++++++++++---------
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, 113 insertions(+), 60 deletions(-)
--
2.33.0.800.g4c38ced690-goog
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Quentin Perret <qperret@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
kvmarm@lists.cs.columbia.edu
Subject: [PATCH v2 0/5] KVM: arm64: Restrict host hypercalls when pKVM is enabled
Date: Tue, 5 Oct 2021 12:37:16 +0100 [thread overview]
Message-ID: <20211005113721.29441-1-will@kernel.org> (raw)
Hi all,
This is version two of the patches I previously posted here:
https://lore.kernel.org/r/20210923112256.15767-1-will@kernel.org
Changes since v2 include:
- Add a comment about pkvm_prot_finalize() returning -EPERM
- Fixed ordering of hypercalls in 'host_hcall' array
- Added reviewed-by tags
Patches based on -rc2. Feedback welcome.
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
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 | 43 ++++++++++---------
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, 113 insertions(+), 60 deletions(-)
--
2.33.0.800.g4c38ced690-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-10-05 11:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 11:37 Will Deacon [this message]
2021-10-05 11:37 ` [PATCH v2 0/5] KVM: arm64: Restrict host hypercalls when pKVM is enabled Will Deacon
2021-10-05 11:37 ` [PATCH v2 1/5] arm64: Prevent kexec and hibernation if is_protected_kvm_enabled() Will Deacon
2021-10-05 11:37 ` Will Deacon
2021-10-05 11:37 ` [PATCH v2 2/5] KVM: arm64: Reject stub hypercalls after pKVM has been initialised Will Deacon
2021-10-05 11:37 ` Will Deacon
2021-10-05 11:37 ` [PATCH v2 3/5] KVM: arm64: Propagate errors from __pkvm_prot_finalize hypercall Will Deacon
2021-10-05 11:37 ` Will Deacon
2021-10-05 11:37 ` [PATCH v2 4/5] KVM: arm64: Prevent re-finalisation of pKVM for a given CPU Will Deacon
2021-10-05 11:37 ` Will Deacon
2021-10-05 11:37 ` [PATCH v2 5/5] KVM: arm64: Disable privileged hypercalls after pKVM finalisation Will Deacon
2021-10-05 11:37 ` Will Deacon
2021-10-07 12:56 ` Marc Zyngier
2021-10-07 12:56 ` Marc Zyngier
2021-10-08 7:27 ` Will Deacon
2021-10-08 7:27 ` Will Deacon
2021-10-08 7:31 ` Marc Zyngier
2021-10-08 7:31 ` 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=20211005113721.29441-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.