All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 5/5] SSB extra v2 5
Date: Wed, 9 May 2018 11:04:14 -1000 (HST)	[thread overview]
Message-ID: <alpine.LFD.2.21.999.1805091054390.5740@xps13.linux-foundation.org> (raw)
In-Reply-To: <e2fa9047-93be-2ad9-1d56-30167e9001b2@linux.intel.com>



On Wed, 9 May 2018, speck for Dave Hansen wrote:
> 
> Frankly, I think it's mostly a waste of time to do it without having the
> BPF folks deeply involved from day one.  They were not fans of the way
> we (Intel) did Spectre V1 mitigations and I don't expect this to be any
> different.
> 
> They were deeply opposed to LFENCE getting used, for instance.

If the main worry is using the store buffer bypass to basically bypass 
type safety (by loading a pointer that was prevously stored as something 
else), I would assume that it could be done with something much more 
targeted than an lfence. 

But I do suspect that once they see a MSR write on each entry/exit, 
they'll say "we'll do the lfence". You can probably have some simple 
greedy model where you only do an lfence for pointer loads, and only if 
you did a store before, and maybe it won't be too painful.

But yes, we definitely should have Alexei involved. For some reason I 
thought he already was.

              Linus

      parent reply	other threads:[~2018-05-09 21:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 23:18 [MODERATED] [PATCH 0/5] SSB extra v2 0 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 1/5] SSB extra v2 1 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 2/5] SSB extra v2 2 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 3/5] SSB extra v2 3 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 4/5] SSB extra v2 4 Dave Hansen
2018-05-07 23:18 ` [MODERATED] [PATCH 5/5] SSB extra v2 5 Dave Hansen
2018-05-08  0:36 ` [MODERATED] " Andi Kleen
2018-05-08  0:46   ` Dave Hansen
2018-05-09 15:36     ` Thomas Gleixner
2018-05-09 15:43       ` [MODERATED] " Dave Hansen
2018-05-09 15:55         ` Greg KH
2018-05-09 16:03           ` Dave Hansen
2018-05-09 16:05             ` Jiri Kosina
2018-05-09 16:36               ` Dave Hansen
2018-05-16 15:23                 ` Jon Masters
2018-05-09 21:04         ` Linus Torvalds [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=alpine.LFD.2.21.999.1805091054390.5740@xps13.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --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.