From: Jiri Kosina <jikos@kernel.org>
To: Jon Masters <jcm@redhat.com>
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Andi Kleen <ak@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Casey Schaufler <casey.schaufler@intel.com>,
Asit Mallick <asit.k.mallick@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 2/2] x86/speculation: Provide application property based STIBP protection
Date: Tue, 2 Oct 2018 17:43:16 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1810021742540.14430@cbobk.fhfr.pm> (raw)
In-Reply-To: <1a501628-a232-a126-166e-814c26243f2d@redhat.com>
On Tue, 2 Oct 2018, Jon Masters wrote:
> > This patch provides an application property based spectre_v2
> > protection with STIBP against attack from another app from
> > a sibling hyper-thread. For security sensitive non-dumpable
> > app, STIBP will be turned on before switching to it for Intel
> > processors vulnerable to spectre_v2.
>
> A general comment. I think in practice this will be similar to the
> speculative store buffer bypass (aka "variant 4") issue in terms of
> opt-in mitigation. Many users won't want to take the performance hit of
> having STIBP by default for peer threads. We should make sure that we
> don't force users into a mitigation but retain an option. Whether it's
> default-on or not can be debated, though I think the vendors lean toward
> having default-off with an opt-in, and customers will probably agree. So
> anyway, I encourage a pragmatic approach similar to that for SSBD.
Which is what Tim's patchset is implementing on top.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2018-10-02 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 21:35 [PATCH 0/2] Provide options to enable spectre_v2 userspace-userspace protection Tim Chen
2018-09-19 21:35 ` [PATCH 1/2] x86/speculation: Option to select app to app mitigation for spectre_v2 Tim Chen
2018-09-19 21:35 ` [PATCH 2/2] x86/speculation: Provide application property based STIBP protection Tim Chen
2018-09-20 7:57 ` Peter Zijlstra
2018-09-20 17:17 ` Tim Chen
2018-09-20 8:00 ` Peter Zijlstra
2018-09-20 17:32 ` Tim Chen
2018-10-02 15:41 ` Jon Masters
2018-10-02 15:43 ` Jiri Kosina [this message]
2018-10-02 15:44 ` Jon Masters
2018-09-20 21:38 ` [PATCH 0/2] Provide options to enable spectre_v2 userspace-userspace protection Lendacky, Thomas
2018-09-21 15:44 ` Lendacky, Thomas
2018-09-21 17:14 ` Tim Chen
2018-09-21 17:44 ` Lendacky, Thomas
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=nycvar.YFH.7.76.1810021742540.14430@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=asit.k.mallick@intel.com \
--cc=casey.schaufler@intel.com \
--cc=dave.hansen@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=jcm@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--cc=x86@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).