[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v12 6/8] arm64: kvm: Expose KVM_ARM_CAP_MTE
From: |
Marc Zyngier |
Subject: |
Re: [PATCH v12 6/8] arm64: kvm: Expose KVM_ARM_CAP_MTE |
Date: |
Mon, 17 May 2021 18:40:22 +0100 |
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (Gojō) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
On Mon, 17 May 2021 13:32:37 +0100,
Steven Price <steven.price@arm.com> wrote:
>
> It's now safe for the VMM to enable MTE in a guest, so expose the
> capability to user space.
>
> Signed-off-by: Steven Price <steven.price@arm.com>
> ---
> arch/arm64/kvm/arm.c | 9 +++++++++
> arch/arm64/kvm/sys_regs.c | 3 +++
> 2 files changed, 12 insertions(+)
>
> diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> index 1cb39c0803a4..e89a5e275e25 100644
> --- a/arch/arm64/kvm/arm.c
> +++ b/arch/arm64/kvm/arm.c
> @@ -93,6 +93,12 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm,
> r = 0;
> kvm->arch.return_nisv_io_abort_to_user = true;
> break;
> + case KVM_CAP_ARM_MTE:
> + if (!system_supports_mte() || kvm->created_vcpus)
> + return -EINVAL;
> + r = 0;
> + kvm->arch.mte_enabled = true;
As far as I can tell from the architecture, this isn't valid for a
32bit guest.
M.
--
Without deviation from the norm, progress is not possible.
- Re: [PATCH v12 4/8] arm64: kvm: Introduce MTE VM feature, (continued)
[PATCH v12 5/8] arm64: kvm: Save/restore MTE registers, Steven Price, 2021/05/17
[PATCH v12 6/8] arm64: kvm: Expose KVM_ARM_CAP_MTE, Steven Price, 2021/05/17
- Re: [PATCH v12 6/8] arm64: kvm: Expose KVM_ARM_CAP_MTE,
Marc Zyngier <=
[PATCH v12 7/8] KVM: arm64: ioctl to fetch/store tags in a guest, Steven Price, 2021/05/17