From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch 4/8] MDS basics 4
Date: Tue, 19 Feb 2019 08:08:30 -0800 [thread overview]
Message-ID: <20190219160829.GT16922@tassilo.jf.intel.com> (raw)
In-Reply-To: <7f92c34c-a3c4-1df2-c026-c7309c6ff3f2@citrix.com>
On Tue, Feb 19, 2019 at 01:54:55PM +0000, speck for Andrew Cooper wrote:
> On 19/02/2019 12:44, speck for Thomas Gleixner wrote:
> > Subject: [patch 4/8] x86/speculation/mds: Conditionaly clear CPU buffers on idle entry
> > From: Thomas Gleixner <tglx@linutronix.de>
> >
> > Add a static key which controls the invocation of the CPU buffer clear
> > mechanism on idle entry. This is independent of other MDS mitigations
> > because the idle entry invocation to mitigate the potential leakage due to
> > store buffer repartitioning is only necessary on SMT systems.
> >
> > Add the actual invocations to the different halt/mwait variants which
> > covers all usage sites. mwaitx is not patched as it's not available on
> > Intel CPUs.
> >
> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> Unfortunately, clearing is needed on the exit from idle as well as the
> entry.
Not with the full flush. There it would always clear on next kernel exit.
-Andi
next prev parent reply other threads:[~2019-02-19 16:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 12:44 [patch 0/8] MDS basics 0 Thomas Gleixner
2019-02-19 12:44 ` [patch 1/8] MDS basics 1 Thomas Gleixner
2019-02-19 14:00 ` [MODERATED] " Borislav Petkov
2019-02-19 12:44 ` [patch 2/8] MDS basics 2 Thomas Gleixner
2019-02-19 12:44 ` [patch 3/8] MDS basics 3 Thomas Gleixner
2019-02-19 16:04 ` [MODERATED] " Andi Kleen
2019-02-19 21:44 ` Thomas Gleixner
2019-02-19 22:13 ` Thomas Gleixner
2019-02-20 16:59 ` [MODERATED] " Andi Kleen
2019-02-20 21:28 ` Thomas Gleixner
2019-02-19 12:44 ` [patch 4/8] MDS basics 4 Thomas Gleixner
2019-02-19 13:54 ` [MODERATED] " Andrew Cooper
2019-02-19 14:02 ` Thomas Gleixner
2019-02-19 14:07 ` Thomas Gleixner
2019-02-19 16:09 ` [MODERATED] " Andi Kleen
2019-02-19 16:17 ` Peter Zijlstra
2019-02-19 17:16 ` Thomas Gleixner
2019-02-19 16:08 ` Andi Kleen [this message]
2019-02-19 16:23 ` [MODERATED] " Andrew Cooper
2019-02-19 16:07 ` Andi Kleen
2019-02-19 18:29 ` Thomas Gleixner
2019-02-19 12:44 ` [patch 5/8] MDS basics 5 Thomas Gleixner
2019-02-19 15:07 ` Thomas Gleixner
2019-02-19 16:13 ` [MODERATED] " Andi Kleen
2019-02-19 17:37 ` Thomas Gleixner
2019-02-20 0:05 ` Thomas Gleixner
2019-02-19 16:03 ` [MODERATED] " Andi Kleen
2019-02-19 17:40 ` Thomas Gleixner
2019-02-19 17:44 ` [MODERATED] " Andrew Cooper
2019-02-19 17:52 ` Thomas Gleixner
2019-02-19 12:44 ` [patch 6/8] MDS basics 6 Thomas Gleixner
2019-02-19 12:44 ` [patch 7/8] MDS basics 7 Thomas Gleixner
2019-02-19 12:44 ` [patch 8/8] MDS basics 8 Thomas Gleixner
2019-02-19 14:17 ` [MODERATED] " Greg KH
2019-02-19 14:22 ` Thomas Gleixner
2019-02-19 17:27 ` [MODERATED] " Andrew Cooper
2019-02-19 14:03 ` [MODERATED] Re: [patch 0/8] MDS basics 0 Andrew Cooper
2019-02-19 14:09 ` Thomas Gleixner
2019-02-19 14:10 ` [MODERATED] " Tyler Hicks
2019-02-19 15:56 ` Andi Kleen
2019-02-19 17:42 ` Thomas Gleixner
2019-02-21 16:14 ` [MODERATED] Encrypted Message Jon Masters
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=20190219160829.GT16922@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=speck@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.