From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751730AbeAPVus (ORCPT + 1 other); Tue, 16 Jan 2018 16:50:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56626 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182AbeAPVur (ORCPT ); Tue, 16 Jan 2018 16:50:47 -0500 Subject: Re: [PATCH v2] arm64: Branch predictor hardening for Cavium ThunderX2 To: Jayachandran C , Will Deacon References: <20180108164651.GQ25869@arm.com> <1515502022-7376-1-git-send-email-jnair@caviumnetworks.com> Cc: marc.zyngier@arm.com, linux-arm-kernel@lists.infradead.org, lorenzo.pieralisi@arm.com, ard.biesheuvel@linaro.org, catalin.marinas@arm.com, linux-kernel@vger.kernel.org, labbott@redhat.com, christoffer.dall@linaro.org Newsgroups: gmane.linux.kernel,gmane.linux.ports.arm.kernel From: Jon Masters Organization: World Organi{s,z}ation of Broken Dreams Message-ID: <468ac3c5-48bf-26d7-0fc5-cf2d833bdfa7@jonmasters.org> Date: Tue, 16 Jan 2018 16:50:38 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <1515502022-7376-1-git-send-email-jnair@caviumnetworks.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 16 Jan 2018 21:50:47 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 01/09/2018 07:47 AM, Jayachandran C wrote: > Use PSCI based mitigation for speculative execution attacks targeting > the branch predictor. The approach is similar to the one used for > Cortex-A CPUs, but in case of ThunderX2 we add another SMC call to > test if the firmware supports the capability. > > If the secure firmware has been updated with the mitigation code to > invalidate the branch target buffer, we use the PSCI version call to > invoke it. What's the status of this patch for TX2? Previously you were holding on the new SMC number, but I think the consensus was to pull this in now? Jon. -- Computer Architect