historical-speck.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 2/2] more sampling fun 2
Date: Tue, 25 Feb 2020 08:18:52 -0600	[thread overview]
Message-ID: <20200225141852.wqjdulg46dfztxe4@treble> (raw)
In-Reply-To: <20200225104658.GA6012@zn.tnic>

On Tue, Feb 25, 2020 at 11:46:58AM +0100, speck for Borislav Petkov wrote:
> On Mon, Feb 24, 2020 at 07:26:41PM -0600, speck for Josh Poimboeuf wrote:
> > Why not just srbds= ?  That's what Intel calls it, and it would be
> > consistent with some of the other options like mds= and l1tf=.
> 
> For the same reason we did "spec_store_bypass_disable=" and not "ssbd=".
> Although former is a bit longish for my taste, it doesn't make you go
> look it up as "ssbd" does. And with "mds" and "l1tf" we dropped the ball
> again. :-\
> 
> Over time, they would all become a letters jumble which we all would
> have to go look up.
> 
> So I think at least *trying* to make them a bit more
> understandable/parseable for humans, would be beneficial in the long
> run.
> 
> So, for example, when I see "srb_sampling=off" at least I know, oh, ok,
> it disables sampling of that SRB thing. "srbds" tells me exactly nothing
> and the potential for flipping those letters' position is high.

Well, I see it the opposite way.  Those jumbles of letters do actually
mean something.  I still call them "MDS", "L1TF", "SSBD".  If you google
for "l1tf" or "mds vulnerability" they show up.  I'd expect to call this
one "SRBDS" a year from now.  I find "srb_sampling" to be confusing and
hard to remember because it renames something that already has an
industry standard name.

-- 
Josh

  reply	other threads:[~2020-02-25 14:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 17:31 Konrad Rzeszutek Wilk
2020-02-24 18:17 ` [MODERATED] " Borislav Petkov
2020-02-24 21:39   ` mark gross
2020-02-24 23:10     ` [MODERATED] " Borislav Petkov
2020-02-25  1:26       ` Josh Poimboeuf
2020-02-25 10:46         ` Borislav Petkov
2020-02-25 14:18           ` Josh Poimboeuf [this message]
2020-02-25 14:23             ` Jiri Kosina
2020-02-25 14:44               ` Josh Poimboeuf
2020-02-25 14:59             ` Borislav Petkov
2020-02-26 20:20               ` Josh Poimboeuf
2020-02-26 21:16                 ` Thomas Gleixner
2020-02-26 22:19                   ` [MODERATED] " Konrad Rzeszutek Wilk
     [not found] <c5bae80efe4694c81d9cbbce633a2228086a330c.158215=?utf-8?q?2322?= .git.mgross@linux.intel.com>
2020-02-20 19:06 ` Ben Hutchings
2020-02-20 19:35   ` mark gross
2020-02-21 22:25     ` mark gross

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=20200225141852.wqjdulg46dfztxe4@treble \
    --to=jpoimboe@redhat.com \
    --cc=speck@linutronix.de \
    --subject='[MODERATED] Re: [PATCH 2/2] more sampling fun 2' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).