From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 2/2] more sampling fun 2
Date: Wed, 26 Feb 2020 17:19:25 -0500 [thread overview]
Message-ID: <20200226221925.GB24083@char.us.oracle.com> (raw)
In-Reply-To: <875zftoxq9.fsf@nanos.tec.linutronix.de>
On Wed, Feb 26, 2020 at 10:16:46PM +0100, speck for Thomas Gleixner wrote:
> speck for Josh Poimboeuf <speck@linutronix.de> writes:
> > On Tue, Feb 25, 2020 at 03:59:06PM +0100, speck for Borislav Petkov wrote:
> >> > 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.
> >>
> >> srb_sampling *is* srbds - just more readable.
> >>
> >> We are not giving any new names to the vulns - we're simply making our command
> >> line options more readable so that when you have to type them, you either have
> >> to remember "srbds" - in that order - or "srb sampling".
> >>
> >> Latter is easier for me.
> >
> > But you're leaving out the "data" portion of the acronym/name.
> >
> > Either call it "srbds" or "special_register_buffer_data_sampling" -- but
> > *please* don't give it a new name. It will just create more confusion.
> >
> > If you can't remember what srbds stands for, that's why we have
> > documentation and search engines.
>
> Our command line options for this mess are inconsistent already, but for
> most of them we have actual acronyms used, so lets just go with srbds.
Sounds like shruberryds. I wonder if Google will autocorrect 'srbds' to
shrubbery or shrubs.
>
> Having a half correct, but more elaborate one does not really help. If
> at all you want to come up with a snarky one like:
>
> super_random_but_data_stolen = [hell_no, shrug, nsa]
Nah,
the_knights_of_ni=?
:-)
How about
rng_secure=on,off
Since that is all folks will care about.
And
mitigation=off will tweak it to off too.
>
> Thanks,
>
> tglx
>
next prev parent reply other threads:[~2020-02-26 22:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 17:31 [MODERATED] Re: [PATCH 2/2] more sampling fun 2 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
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 ` Konrad Rzeszutek Wilk [this message]
[not found] <c5bae80efe4694c81d9cbbce633a2228086a330c.158215=?utf-8?q?2322?= .git.mgross@linux.intel.com>
2020-02-20 19:06 ` [MODERATED] " 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=20200226221925.GB24083@char.us.oracle.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).