From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: Doug Berger <opendmb@gmail.com>,
catalin.marinas@arm.com, Russell King <linux@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
bcm-kernel-feedback-list@broadcom.com, will@kernel.org,
Julien Thierry <julien.thierry.kdev@gmail.com>
Subject: Re: [PATCH] ARM: spectre-v2: remove Brahma-B53 from hardening
Date: Sun, 10 Nov 2019 19:33:09 -0800 [thread overview]
Message-ID: <64597efe-c5f5-4dc2-05c6-bf10f04ec148@gmail.com> (raw)
In-Reply-To: <20191031220053.2720-1-f.fainelli@gmail.com>
On 10/31/2019 3:00 PM, Florian Fainelli wrote:
> From: Doug Berger <opendmb@gmail.com>
>
> When the default processor handling was added to the function
> cpu_v7_spectre_init() it only excluded other ARM implemented processor
> cores. The Broadcom Brahma B53 core is not implemented by ARM so it
> ended up falling through into the set of processors that attempt to use
> the ARM_SMCCC_ARCH_WORKAROUND_1 service to harden the branch predictor.
>
> Since this workaround is not necessary for the Brahma-B53 this commit
> explicitly checks for it and prevents it from applying a branch
> predictor hardening workaround.
>
> Fixes: 10115105cb3a ("ARM: spectre-v2: add firmware based hardening")
> Signed-off-by: Doug Berger <opendmb@gmail.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Submitted:
https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=8937/1
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-11 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 22:00 [PATCH] ARM: spectre-v2: remove Brahma-B53 from hardening Florian Fainelli
2019-11-11 3:33 ` Florian Fainelli [this message]
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=64597efe-c5f5-4dc2-05c6-bf10f04ec148@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=opendmb@gmail.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).