From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
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>,
Jon Masters <jcm@redhat.com>, Waiman Long <longman9394@gmail.com>,
Dave Stewart <david.c.stewart@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/speculation: Revert turning on STIBP all the time
Date: Thu, 22 Nov 2018 07:58:50 +0100 [thread overview]
Message-ID: <20181122065850.GA11963@kroah.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1811212149080.21108@cbobk.fhfr.pm>
On Wed, Nov 21, 2018 at 09:51:19PM +0100, Jiri Kosina wrote:
> On Wed, 21 Nov 2018, Tim Chen wrote:
>
> > Commit 53c613fe "x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation"
> > turns on STIBP all the time.
> >
> > This causes large performance regression in many workloads.
> >
> > One case is perlbench in the SpecInt Rate 2006 test suite which shows a
> > 21% reduction in throughput.
> > There're also other reports of drop in performance on Python and PHP benchmarks:
> > https://www.phoronix.com/scan.php?page=article&item=linux-420-bisect&num=2
> >
> > STIBP on all the time should not be the default option.
> >
> > Turn off STIBP all the time for now till STIBP can be applied on
> > a per task basis.
> >
> > Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
> > ---
> > arch/x86/kernel/cpu/bugs.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bugs.c
> > index c37e66e..21a8f39 100644
> > --- a/arch/x86/kernel/cpu/bugs.c
> > +++ b/arch/x86/kernel/cpu/bugs.c
> > @@ -332,7 +332,7 @@ static bool stibp_needed(void)
> > if (!boot_cpu_has(X86_FEATURE_STIBP))
> > return false;
> >
> > - return true;
> > + return false;
> > }
>
> For -stable, which actually makes it to production, I already asked Greg
> to drop it.
It's in the latest stable -rc releases, and if all goes well, they will
be released tomorrow.
thanks,
greg k-h
prev parent reply other threads:[~2018-11-22 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 20:00 [PATCH] x86/speculation: Revert turning on STIBP all the time Tim Chen
2018-11-21 20:51 ` Jiri Kosina
2018-11-21 21:02 ` Linus Torvalds
2018-11-22 6:58 ` Greg KH [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=20181122065850.GA11963@kroah.com \
--to=gregkh@linuxfoundation.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=david.c.stewart@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=jcm@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman9394@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--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