Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp153832yba; Fri, 5 Apr 2019 04:06:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqzVLx9P3yChjN/8sR9tDjXI45Dc3x2fHhLJUIw6Vi3a3Xx0HPFm2EfIKnIb7i0bRGFNlg0W X-Received: by 2002:a65:5249:: with SMTP id q9mr11468887pgp.104.1554462388524; Fri, 05 Apr 2019 04:06:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554462388; cv=none; d=google.com; s=arc-20160816; b=h49ZyKSvTGF/V0CtWtThjqdpEeiqc4Oj5pXPdpBYv3stYm8WxraxHK5/XQabozKS5e YzATvOSsuXSElP0BCK9bjG38wRTryokqGvP19w6VrrrcjqPqaI7hDtSqijUujKV4I19P UUfCkpO2ia2DpHBIqX2Sg1s4wM4CiuhrWkGOj8iOzk2OYyA26Wo9czcuaSv94cTEOdv8 gLA68MULFBtCmPwH1zeJkZw/9ySqguCXeGsRK9iYGOGhnCmCj6+38s4vXHrn06FKCe2e hbto8qI1LGCFU66AL907M8nmvFdJjkD/Iil5Bbpebp7PLIJB2eFxk1j1QTj5mTHKK+Z7 9TIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=n7nB/LUiuajKinx3MY1miFF9h3+lLLyk/Up8nFYvrvg=; b=voJ+togL3/iqKDzE0heT7yflKq54cBAU0frhNzk3jHQeaGmCdL0LWhLA71QpKG+qw9 bp5YBjX4japxWD66hcZBtPqIXxUZQSM0m+Z0kUQM4wW9GgvzIB7MBz9IXFDZDUVp7FnC 85zBnSmrWrUhtUhYB+KmFbhtGSLX+kLlvcHp3fnga3l0+httj1oFdAmKsMpEK+k50iyj oJvwAXrYotuG9DzVm7uFJZS421oWeYsteKo1OA4bwU8tRLanoaVVyWUqqqofM4bgBhWf GMBeBgXC8JktYYNK3y+gVI1V0eIW78O7IWLI+kTB/0YjIo6t5jd4rZWJKkjr6ovokJXU w9vA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m2si18281443pgp.463.2019.04.05.04.06.13; Fri, 05 Apr 2019 04:06:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730969AbfDELE2 (ORCPT + 99 others); Fri, 5 Apr 2019 07:04:28 -0400 Received: from foss.arm.com ([217.140.101.70]:46130 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730497AbfDELE1 (ORCPT ); Fri, 5 Apr 2019 07:04:27 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 365D4168F; Fri, 5 Apr 2019 04:04:27 -0700 (PDT) Received: from e103592.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 8D7A73F557; Fri, 5 Apr 2019 04:04:25 -0700 (PDT) Date: Fri, 5 Apr 2019 12:04:23 +0100 From: Dave Martin To: Amit Daniel Kachhap Cc: linux-arm-kernel@lists.infradead.org, Marc Zyngier , Catalin Marinas , Will Deacon , Kristina Martsenko , kvmarm@lists.cs.columbia.edu, Ramana Radhakrishnan , linux-kernel@vger.kernel.org Subject: Re: [kvmtool PATCH v8 9/9] KVM: arm/arm64: Add a vcpu feature for pointer authentication Message-ID: <20190405110423.GV3567@e103592.cambridge.arm.com> References: <1554172037-4516-1-git-send-email-amit.kachhap@arm.com> <1554172037-4516-10-git-send-email-amit.kachhap@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1554172037-4516-10-git-send-email-amit.kachhap@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 02, 2019 at 07:57:17AM +0530, Amit Daniel Kachhap wrote: > This is a runtime capabality for KVM tool to enable Arm64 8.3 Pointer > Authentication in guest kernel. Two vcpu features > KVM_ARM_VCPU_PTRAUTH_[ADDRESS/GENERIC] are supplied together to enable > Pointer Authentication in KVM guest after checking the capability. > > A command line option --ptrauth is also required to select this feature. > > Signed-off-by: Amit Daniel Kachhap > --- > > Changes since v7: > * Added check for capability KVM_CAP_ARM_PTRAUTH_GENERIC > > arm/aarch32/include/kvm/kvm-cpu-arch.h | 1 + > arm/aarch64/include/asm/kvm.h | 2 ++ > arm/aarch64/include/kvm/kvm-config-arch.h | 4 +++- > arm/aarch64/include/kvm/kvm-cpu-arch.h | 2 ++ > arm/include/arm-common/kvm-config-arch.h | 1 + > arm/kvm-cpu.c | 7 +++++++ > include/linux/kvm.h | 2 ++ > 7 files changed, 18 insertions(+), 1 deletion(-) > > diff --git a/arm/aarch32/include/kvm/kvm-cpu-arch.h b/arm/aarch32/include/kvm/kvm-cpu-arch.h > index d28ea67..520ea76 100644 > --- a/arm/aarch32/include/kvm/kvm-cpu-arch.h > +++ b/arm/aarch32/include/kvm/kvm-cpu-arch.h > @@ -13,4 +13,5 @@ > #define ARM_CPU_ID 0, 0, 0 > #define ARM_CPU_ID_MPIDR 5 > > +#define ARM_VCPU_PTRAUTH_FEATURE 0 > #endif /* KVM__KVM_CPU_ARCH_H */ > diff --git a/arm/aarch64/include/asm/kvm.h b/arm/aarch64/include/asm/kvm.h > index 97c3478..d4d0d8c 100644 > --- a/arm/aarch64/include/asm/kvm.h > +++ b/arm/aarch64/include/asm/kvm.h > @@ -102,6 +102,8 @@ struct kvm_regs { > #define KVM_ARM_VCPU_EL1_32BIT 1 /* CPU running a 32bit VM */ > #define KVM_ARM_VCPU_PSCI_0_2 2 /* CPU uses PSCI v0.2 */ > #define KVM_ARM_VCPU_PMU_V3 3 /* Support guest PMUv3 */ > +#define KVM_ARM_VCPU_PTRAUTH_ADDRESS 4 /* CPU uses address pointer authentication */ > +#define KVM_ARM_VCPU_PTRAUTH_GENERIC 5 /* CPU uses generic pointer authentication */ > > struct kvm_vcpu_init { > __u32 target; > diff --git a/arm/aarch64/include/kvm/kvm-config-arch.h b/arm/aarch64/include/kvm/kvm-config-arch.h > index 04be43d..2074684 100644 > --- a/arm/aarch64/include/kvm/kvm-config-arch.h > +++ b/arm/aarch64/include/kvm/kvm-config-arch.h > @@ -8,7 +8,9 @@ > "Create PMUv3 device"), \ > OPT_U64('\0', "kaslr-seed", &(cfg)->kaslr_seed, \ > "Specify random seed for Kernel Address Space " \ > - "Layout Randomization (KASLR)"), > + "Layout Randomization (KASLR)"), \ > + OPT_BOOLEAN('\0', "ptrauth", &(cfg)->has_ptrauth, \ > + "Enable address authentication"), This should probably say "pointer", not "address" now, since we enable both kinds of ptrauth together. (Sorry!) When discussing how to control SVE, I was eventually convinced that it is more user-friendly to make SVE default to on if present, and maybe provide two options --disable-sve, --enable-sve, in case the user wants to force it off or on instead of just getting what the host supports. Passing --enable-sve on a host that doesn't support SVE would then lead to kvmtool bailing out with an error, which is probably better then silently turning it off. I don't have this change in my kvmtool patches yet. What's your view? It makes sense to do things the same way for all features if we can. > #include "arm-common/kvm-config-arch.h" > > diff --git a/arm/aarch64/include/kvm/kvm-cpu-arch.h b/arm/aarch64/include/kvm/kvm-cpu-arch.h > index a9d8563..fcc2107 100644 > --- a/arm/aarch64/include/kvm/kvm-cpu-arch.h > +++ b/arm/aarch64/include/kvm/kvm-cpu-arch.h > @@ -17,4 +17,6 @@ > #define ARM_CPU_CTRL 3, 0, 1, 0 > #define ARM_CPU_CTRL_SCTLR_EL1 0 > > +#define ARM_VCPU_PTRAUTH_FEATURE ((1UL << KVM_ARM_VCPU_PTRAUTH_ADDRESS) \ > + | (1UL << KVM_ARM_VCPU_PTRAUTH_GENERIC)) > #endif /* KVM__KVM_CPU_ARCH_H */ > diff --git a/arm/include/arm-common/kvm-config-arch.h b/arm/include/arm-common/kvm-config-arch.h > index 5734c46..5badcbd 100644 > --- a/arm/include/arm-common/kvm-config-arch.h > +++ b/arm/include/arm-common/kvm-config-arch.h > @@ -10,6 +10,7 @@ struct kvm_config_arch { > bool aarch32_guest; > bool has_pmuv3; > u64 kaslr_seed; > + bool has_ptrauth; > enum irqchip_type irqchip; > u64 fw_addr; > }; > diff --git a/arm/kvm-cpu.c b/arm/kvm-cpu.c > index 7780251..398c9d6 100644 > --- a/arm/kvm-cpu.c > +++ b/arm/kvm-cpu.c > @@ -68,6 +68,13 @@ struct kvm_cpu *kvm_cpu__arch_init(struct kvm *kvm, unsigned long cpu_id) > vcpu_init.features[0] |= (1UL << KVM_ARM_VCPU_PSCI_0_2); > } > > + /* Set KVM_ARM_VCPU_PTRAUTH_[ADDRESS/GENERIC] if available */ > + if (kvm__supports_extension(kvm, KVM_CAP_ARM_PTRAUTH_ADDRESS) && > + kvm__supports_extension(kvm, KVM_CAP_ARM_PTRAUTH_GENERIC)) { > + if (kvm->cfg.arch.has_ptrauth) > + vcpu_init.features[0] |= ARM_VCPU_PTRAUTH_FEATURE; > + } > + > /* > * If the preferred target ioctl is successful then > * use preferred target else try each and every target type > diff --git a/include/linux/kvm.h b/include/linux/kvm.h > index 6d4ea4b..500ac2b 100644 > --- a/include/linux/kvm.h > +++ b/include/linux/kvm.h > @@ -988,6 +988,8 @@ struct kvm_ppc_resize_hpt { > #define KVM_CAP_ARM_VM_IPA_SIZE 165 > #define KVM_CAP_MANUAL_DIRTY_LOG_PROTECT 166 > #define KVM_CAP_HYPERV_CPUID 167 > +#define KVM_CAP_ARM_PTRAUTH_ADDRESS 168 > +#define KVM_CAP_ARM_PTRAUTH_GENERIC 169 (Note, 168 will probably be KVM_CAP_ARM_SVE, now that the SVE patches are in kvmarm/next.) Cheers ---Dave