All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch 06/11] [PATCH v2 06/10] Linux Patch #6
Date: Fri, 20 Apr 2018 11:58:09 -0400	[thread overview]
Message-ID: <20180420155804.GA808@localhost.localdomain> (raw)
In-Reply-To: <491430fb-c47a-5335-2b43-67c625901fb0@redhat.com>

On Fri, Apr 20, 2018 at 11:33:05AM -0400, speck for Jon Masters wrote:
> (your mail was unreadable by enigmail on Thunderbird for some reason,
> manually extracted using GPG, excuse any copy+paste errors below)

Use mutt :-)
> 
> On 04/20/2018 07:21 AM, speck for Peter Zijlstra wrote:
> On Thu, Apr 19, 2018 at 10:25:46PM -0400, speck for konrad.wilk_at_oracle.c=
> om wrote:
> >> We provide two sets of knobs. The first are x86 specific:
> >>
> >>  nomdd
> >>  mdd=3D[off,auto,on]
> >>
> >> We also support cross-architecture versions of these:
> >>
> >>  nossbd
> >>  ssbd=3D[off,auto,on]
> 
> > So why does x86 have to be different? Can't it simply use the generic
> > named ones? I didn't see a rationale for that.
> 
> x86 doesn't have to be different. I originally proposed keeping also
> "mdd" just to keep everyone happy on the x86 side in case they cared.
> But "ssbd" is a nice industry neutral term and also works for x86. It
> also will fit with the language that Google will use in their text.

Ugh, another web-page. ssbdattack.com?

Let me rip out the mdd from the documentation and the code.

  reply	other threads:[~2018-04-20 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20  2:25 [MODERATED] [patch 06/11] [PATCH v2 06/10] Linux Patch #6 konrad.wilk
2018-04-20  5:28 ` [MODERATED] " Jon Masters
2018-04-20 11:21 ` Peter Zijlstra
2018-04-20 15:33   ` Jon Masters
2018-04-20 15:58     ` Konrad Rzeszutek Wilk [this message]
2018-04-20 16:11       ` Jon Masters
2018-04-20 17:25 ` Borislav Petkov
2018-04-21  9:21 ` Borislav Petkov

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=20180420155804.GA808@localhost.localdomain \
    --to=konrad.wilk@oracle.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.