From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: [PATCH 3/5] SSB extra 1
Date: Fri, 4 May 2018 18:32:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1805041831590.1675@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180504162813.GH75137@tassilo.jf.intel.com>
On Fri, 4 May 2018, speck for Andi Kleen wrote:
> On Fri, May 04, 2018 at 06:09:04PM +0200, speck for Thomas Gleixner wrote:
> > On Fri, 4 May 2018, speck for Andi Kleen wrote:
> >
> > > > > Ahhh, that's an interesting point. Are you thinking that we add a BPF
> > > > > "instruction" to enable or disable the mitigations, and then have the
> > > > > verifier insert it as the first instruction and then before any exit
> > > > > instructions? Is there some precedent for doing this?
> > > >
> > > > Dunno, but it would be the obvious thing to do I think.
> > >
> > > Other option would be a preempt notifier migrating the SSB state?
> >
> > Why so? Because it's more complex than just using the TIF_RDS flag which
> > gets evaluated anyway?
>
> The flag doesn't know anything about the timer. You would
> need another flag that says "start a delay timer on the new CPU
> too".
Color me confused. I dont see a timer anywhere.
next prev parent reply other threads:[~2018-05-04 16:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 22:29 [MODERATED] [PATCH 0/5] SSB extra 0 Dave Hansen
2018-05-03 22:29 ` [MODERATED] [PATCH 1/5] SSB extra 2 Dave Hansen
2018-05-03 22:29 ` [MODERATED] [PATCH 2/5] SSB extra 3 Dave Hansen
2018-05-03 22:29 ` [MODERATED] [PATCH 3/5] SSB extra 1 Dave Hansen
2018-05-03 22:29 ` [MODERATED] [PATCH 4/5] SSB extra 5 Dave Hansen
2018-05-03 22:29 ` [MODERATED] [PATCH 5/5] SSB extra 4 Dave Hansen
2018-05-03 23:27 ` [MODERATED] Re: [PATCH 0/5] SSB extra 0 Kees Cook
2018-05-04 1:37 ` Dave Hansen
2018-05-04 22:26 ` Kees Cook
2018-05-23 7:17 ` [MODERATED] cBPF affectedness (was Re: [PATCH 0/5] SSB extra 0) Jiri Kosina
2018-05-23 13:56 ` [MODERATED] " Alexei Starovoitov
2018-05-04 9:20 ` [MODERATED] Re: [PATCH 1/5] SSB extra 2 Peter Zijlstra
2018-05-04 14:04 ` Dave Hansen
2018-05-04 15:50 ` Peter Zijlstra
2018-05-04 15:54 ` Linus Torvalds
2018-05-04 13:33 ` [PATCH 3/5] SSB extra 1 Thomas Gleixner
2018-05-04 14:22 ` [MODERATED] " Dave Hansen
2018-05-04 14:26 ` Thomas Gleixner
2018-05-04 16:04 ` [MODERATED] " Andi Kleen
2018-05-04 16:09 ` Thomas Gleixner
2018-05-04 16:28 ` [MODERATED] " Andi Kleen
2018-05-04 16:32 ` Thomas Gleixner [this message]
2018-05-04 16:43 ` Dave Hansen
2018-05-04 18:39 ` Thomas Gleixner
2018-05-06 8:32 ` Thomas Gleixner
2018-05-06 21:48 ` Thomas Gleixner
2018-05-06 22:40 ` [MODERATED] " Dave Hansen
2018-05-07 6:19 ` Thomas Gleixner
2018-05-04 17:01 ` [MODERATED] Re: [PATCH 4/5] SSB extra 5 Konrad Rzeszutek Wilk
2018-05-21 9:56 ` [MODERATED] Re: [PATCH 5/5] SSB extra 4 Jiri Kosina
2018-05-21 13:38 ` Thomas Gleixner
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.DEB.2.21.1805041831590.1675@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--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.