From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: turn off xgene branch prediction while in kernel space
Date: Wed, 24 Jan 2018 16:43:24 +0000 [thread overview]
Message-ID: <20180124164324.GA30462@arm.com> (raw)
In-Reply-To: <1516811703.2957.47.camel@redhat.com>
On Wed, Jan 24, 2018 at 11:35:03AM -0500, Mark Salter wrote:
> On Wed, 2018-01-24 at 10:58 +0000, Marc Zyngier wrote:
> > Khuong,
> >
> > On 24/01/18 02:13, Khuong Dinh wrote:
> > > Aliasing attacks against CPU branch predictors can allow an attacker to
> > > redirect speculative control flow on some CPUs and potentially divulge
> > > information from one context to another.
> > >
> > > This patch only supports for XGene processors.
> > >
> > > Signed-off-by: Mark Salter <msalter@redhat.com>
> > > Signed-off-by: Khuong Dinh <kdinh@apm.com>
> > > ---
> > > arch/arm64/include/asm/cpucaps.h | 3 ++-
> > > arch/arm64/include/asm/fixmap.h | 4 ++++
> > > arch/arm64/kernel/cpu_errata.c | 18 ++++++++++++++++++
> > > arch/arm64/kernel/entry.S | 28 ++++++++++++++++++++++++++++
> > > arch/arm64/kernel/smp.c | 34 ++++++++++++++++++++++++++++++++++
> > > 5 files changed, 86 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/arch/arm64/include/asm/cpucaps.h b/arch/arm64/include/asm/cpucaps.h
> > > index bb26382..dc9ada1 100644
> > > --- a/arch/arm64/include/asm/cpucaps.h
> > > +++ b/arch/arm64/include/asm/cpucaps.h
> > > @@ -45,7 +45,8 @@
> > > #define ARM64_HARDEN_BRANCH_PREDICTOR 24
> > > #define ARM64_HARDEN_BP_POST_GUEST_EXIT 25
> > > #define ARM64_HAS_RAS_EXTN 26
> > > +#define ARM64_XGENE_HARDEN_BRANCH_PREDICTOR 27
> > >
> >
> > Why isn't this using the infrastructure that is already in place?
>
> That infrastructure relies on a cpu-specific flush of the branch
> predictor. XGene does not have the ability to flush the branch
> predictor. It can only turn it on or off.
So how does this patch protect one user application from another? Sounds
like you need to turn the thing off at boot and leave it that way, or find
a sequence of branch instructions to effectively do the invalidation.
Will
next prev parent reply other threads:[~2018-01-24 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 2:13 [PATCH] arm64: turn off xgene branch prediction while in kernel space Khuong Dinh
2018-01-24 10:58 ` Marc Zyngier
2018-01-24 16:35 ` Mark Salter
2018-01-24 16:43 ` Will Deacon [this message]
2018-01-25 12:44 ` David Laight
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=20180124164324.GA30462@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).