From: Josh Poimboeuf <jpoimboe@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 2/2] more sampling fun 2
Date: Wed, 26 Feb 2020 14:20:10 -0600 [thread overview]
Message-ID: <20200226202010.k42cf4625ckk6ym6@treble> (raw)
In-Reply-To: <20200225145906.GB6012@zn.tnic>
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.
--
Josh
next prev parent reply other threads:[~2020-02-26 20:20 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 [this message]
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=20200226202010.k42cf4625ckk6ym6@treble \
--to=jpoimboe@redhat.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 NNTP newsgroup(s).