Received: by 10.223.185.116 with SMTP id b49csp2806747wrg; Mon, 5 Mar 2018 08:59:55 -0800 (PST) X-Google-Smtp-Source: AG47ELsF+CbUPY/TK51I/e3SzYRskEePtn4WtDN9JofjUgztGtiyDvQSNGOwmFAd5GFZNtDudY0W X-Received: by 10.101.64.197 with SMTP id u5mr12860099pgp.23.1520269195031; Mon, 05 Mar 2018 08:59:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520269194; cv=none; d=google.com; s=arc-20160816; b=wJmzSztHffn0Byz8RZPpMn9eJoUOeledom7i3+7iIZtjkNTu8ktK41ULk8JxZ6wO6D Peb469nZ1WJ53sDwy51Wg8PDfl1UufIo0jmvVhAWaI7+ZQhjvn/u4Vn+F/RkiFhggsl5 1ig1nCYkWAfaKwHPPVtR43xjIyOL/RgO09osrB4xDMbYnXZeLYg5KUc0bF8DRorWmsMc QURdGBgojTD4qU2D/5FyGAMewv2ec6t6mUMYi8D2KWmD53G+5XTrYvGeC9EBOEYRYSH6 /yWTOuAM9/fjTyHEMlmou2/bAHCjDEjwz9S65Qhag4MBJNQGT6YmLQfXz8VDXv1lfZbj bVrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:reply-to:dmarc-filter :dkim-signature:dkim-signature:arc-authentication-results; bh=J78E5zEJJTxcV45zr9i6ZxUm6hbTTZV/43Bnm7qBOCw=; b=O3qBLCcxxhudd26TeT/jM+E8q4sbRFYDzLy4A6IOSBSQJ7lCxMJ1JJB4DZErek099X kAqEIfTNL2vLFP0jvtsRtfXZJXGZaTkNZNlK+sXvYCt2+IUvHshvktI9n1rIhhh6hb2t QhjyRIyD3N6viHNrhTI0yVtyJ3rpIiWOV8R8sfdF7CS9t2rzcztzxpxkPE5rQi+fL+YJ Q5+66Tdyh8XiXGbX3hRNZGBcunplluwis//tdzE9ItiAKEiZiPIknhkPAuVPgKPYPgkg Y/aavZjcQ/ShXhcVq0kfLFIrIS/4ZgCZo4tC7Sbp8HhWifXNCBBd/VqL5ey+Myyyh+nj Eybg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=C1eXUMyD; dkim=pass header.i=@codeaurora.org header.s=default header.b=QMhREhwo; 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 92-v6si9606632pli.455.2018.03.05.08.59.40; Mon, 05 Mar 2018 08:59:54 -0800 (PST) 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; dkim=pass header.i=@codeaurora.org header.s=default header.b=C1eXUMyD; dkim=pass header.i=@codeaurora.org header.s=default header.b=QMhREhwo; 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 S1752810AbeCEQ6I (ORCPT + 99 others); Mon, 5 Mar 2018 11:58:08 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:56418 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751989AbeCEQ6F (ORCPT ); Mon, 5 Mar 2018 11:58:05 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 40F8B6022C; Mon, 5 Mar 2018 16:58:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1520269085; bh=UsOCpwactFRUdLlKceWLeJ1SWTvA5VMA9p8BELSYW/s=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To:From; b=C1eXUMyD5SrRNmZnSJCT6abJiBhCvPvcprmxxMFetBKazKRcWoqlNzqAQzGikXwyZ v7XdEpWw3oHoqJoXTRIFx8yCl6l5eV9BA8IiCSV9GmX1SaqF+FnPrJ71eiCUWrul+w +uXYA3DqQWT7gIa9sAfhoNtN/ul4DFhzmt/7X1Hc= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from [10.0.2.15] (global_nat1_iad_fw.qualcomm.com [129.46.232.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: shankerd@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 5F7226022C; Mon, 5 Mar 2018 16:58:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1520269084; bh=UsOCpwactFRUdLlKceWLeJ1SWTvA5VMA9p8BELSYW/s=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To:From; b=QMhREhwoZ1t6nDJIThLWxEsi/2GqFwD/pXkUhzd7FuRC8FT6bvnvs8iyY6HlwMJvp PLEAcgFFL/QFH9m1NYGZAF9mm4akc6zQd0U4G8ZEWON0JJ3IH+uBvgswhfZ3IMM43+ R4sjXQMTFn7Fe2lio5kj7KZ4WwiNQubVkATO1bWQ= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 5F7226022C Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=shankerd@codeaurora.org Reply-To: shankerd@codeaurora.org Subject: Re: [PATCH] arm64: KVM: Use SMCCC_ARCH_WORKAROUND_1 for Falkor BP hardening To: Will Deacon Cc: Thomas Speier , Vikram Sethi , Sean Campbell , Marc Zyngier , Catalin Marinas , linux-kernel , linux-arm-kernel , kvmarm , Christoffer Dall References: <1520027418-10646-1-git-send-email-shankerd@codeaurora.org> <20180305155614.GG6618@arm.com> From: Shanker Donthineni Message-ID: <05c25982-4939-593f-ad30-bf496e879885@codeaurora.org> Date: Mon, 5 Mar 2018 10:57:58 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20180305155614.GG6618@arm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Will, On 03/05/2018 09:56 AM, Will Deacon wrote: > Hi Shanker, > > On Fri, Mar 02, 2018 at 03:50:18PM -0600, Shanker Donthineni wrote: >> The function SMCCC_ARCH_WORKAROUND_1 was introduced as part of SMC >> V1.1 Calling Convention to mitigate CVE-2017-5715. This patch uses >> the standard call SMCCC_ARCH_WORKAROUND_1 for Falkor chips instead >> of Silicon provider service ID 0xC2001700. >> >> Signed-off-by: Shanker Donthineni >> --- >> arch/arm64/include/asm/cpucaps.h | 2 +- >> arch/arm64/include/asm/kvm_asm.h | 2 -- >> arch/arm64/kernel/bpi.S | 8 ------ >> arch/arm64/kernel/cpu_errata.c | 55 ++++++++++++++-------------------------- >> arch/arm64/kvm/hyp/entry.S | 12 --------- >> arch/arm64/kvm/hyp/switch.c | 10 -------- >> 6 files changed, 20 insertions(+), 69 deletions(-) > > I'm happy to take this via arm64 if I get an ack from Marc/Christoffer. > >> diff --git a/arch/arm64/include/asm/cpucaps.h b/arch/arm64/include/asm/cpucaps.h >> index bb26382..6ecc249 100644 >> --- a/arch/arm64/include/asm/cpucaps.h >> +++ b/arch/arm64/include/asm/cpucaps.h >> @@ -43,7 +43,7 @@ >> #define ARM64_SVE 22 >> #define ARM64_UNMAP_KERNEL_AT_EL0 23 >> #define ARM64_HARDEN_BRANCH_PREDICTOR 24 >> -#define ARM64_HARDEN_BP_POST_GUEST_EXIT 25 >> +/* #define ARM64_UNALLOCATED_ENTRY 25 */ >> #define ARM64_HAS_RAS_EXTN 26 >> >> #define ARM64_NCAPS 27 > > These aren't ABI, so I think you can just drop > ARM64_HARDEN_BP_POST_GUEST_EXIT and repack the others accordingly. > Sure, I'll remove it completely in v2 patch. >> diff --git a/arch/arm64/include/asm/kvm_asm.h b/arch/arm64/include/asm/kvm_asm.h >> index 24961b7..ab4d0a9 100644 >> --- a/arch/arm64/include/asm/kvm_asm.h >> +++ b/arch/arm64/include/asm/kvm_asm.h >> @@ -68,8 +68,6 @@ >> >> extern u32 __init_stage2_translation(void); >> >> -extern void __qcom_hyp_sanitize_btac_predictors(void); >> - >> #endif >> >> #endif /* __ARM_KVM_ASM_H__ */ >> diff --git a/arch/arm64/kernel/bpi.S b/arch/arm64/kernel/bpi.S >> index e5de335..dc4eb15 100644 >> --- a/arch/arm64/kernel/bpi.S >> +++ b/arch/arm64/kernel/bpi.S >> @@ -55,14 +55,6 @@ ENTRY(__bp_harden_hyp_vecs_start) >> .endr >> ENTRY(__bp_harden_hyp_vecs_end) >> >> -ENTRY(__qcom_hyp_sanitize_link_stack_start) >> - stp x29, x30, [sp, #-16]! >> - .rept 16 >> - bl . + 4 >> - .endr >> - ldp x29, x30, [sp], #16 >> -ENTRY(__qcom_hyp_sanitize_link_stack_end) >> - >> .macro smccc_workaround_1 inst >> sub sp, sp, #(8 * 4) >> stp x2, x3, [sp, #(8 * 0)] >> diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c >> index 52f15cd..d779ffd4 100644 >> --- a/arch/arm64/kernel/cpu_errata.c >> +++ b/arch/arm64/kernel/cpu_errata.c >> @@ -67,8 +67,6 @@ static int cpu_enable_trap_ctr_access(void *__unused) >> DEFINE_PER_CPU_READ_MOSTLY(struct bp_hardening_data, bp_hardening_data); >> >> #ifdef CONFIG_KVM >> -extern char __qcom_hyp_sanitize_link_stack_start[]; >> -extern char __qcom_hyp_sanitize_link_stack_end[]; >> extern char __smccc_workaround_1_smc_start[]; >> extern char __smccc_workaround_1_smc_end[]; >> extern char __smccc_workaround_1_hvc_start[]; >> @@ -115,8 +113,6 @@ static void __install_bp_hardening_cb(bp_hardening_cb_t fn, >> spin_unlock(&bp_lock); >> } >> #else >> -#define __qcom_hyp_sanitize_link_stack_start NULL >> -#define __qcom_hyp_sanitize_link_stack_end NULL >> #define __smccc_workaround_1_smc_start NULL >> #define __smccc_workaround_1_smc_end NULL >> #define __smccc_workaround_1_hvc_start NULL >> @@ -161,12 +157,25 @@ static void call_hvc_arch_workaround_1(void) >> arm_smccc_1_1_hvc(ARM_SMCCC_ARCH_WORKAROUND_1, NULL); >> } >> >> +static void qcom_link_stack_sanitization(void) >> +{ >> + u64 tmp; >> + >> + asm volatile("mov %0, x30 \n" >> + ".rept 16 \n" >> + "bl . + 4 \n" >> + ".endr \n" >> + "mov x30, %0 \n" >> + : "=&r" (tmp)); >> +} >> + >> static int enable_smccc_arch_workaround_1(void *data) >> { >> const struct arm64_cpu_capabilities *entry = data; >> bp_hardening_cb_t cb; >> void *smccc_start, *smccc_end; >> struct arm_smccc_res res; >> + u32 midr = read_cpuid_id(); >> >> if (!entry->matches(entry, SCOPE_LOCAL_CPU)) >> return 0; >> @@ -199,33 +208,15 @@ static int enable_smccc_arch_workaround_1(void *data) >> return 0; >> } >> >> + if (((midr & MIDR_CPU_MODEL_MASK) == MIDR_QCOM_FALKOR) || >> + ((midr & MIDR_CPU_MODEL_MASK) == MIDR_QCOM_FALKOR_V1)) >> + cb = qcom_link_stack_sanitization; > > Is this just a performance thing? Do you actually see an advantage over > always making the firmware call? We've seen minimal impact in our testing. > Yes, we've couple of advantages using the standard SMCCC_ARCH_WOKAROUND_1 framework. - Improves the code readability. - Avoid the unnecessary MIDR checks on each vCPU exit. - Validates ID_AA64PFR0_CVS2 feature for Falkor chips. - Avoids the 2nd link stack sanitization workaround in firmware. > Will > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- Shanker Donthineni Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.