All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: GPZv4
Date: Wed, 18 Apr 2018 00:09:06 -0400	[thread overview]
Message-ID: <ba539d56-6d53-07c1-167a-a8951ac5b3c8@redhat.com> (raw)
In-Reply-To: <a5617d61-652c-da5f-e657-504867693d11@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On 04/17/2018 11:44 PM, Jon Masters wrote:
> On 04/17/2018 10:48 PM, speck for Konrad Rzeszutek Wilk wrote:

>> 2). SBB vs MDD vs SBBD.
>>
>> MDD = Memory Disambiguation Disable
>> SBB = Speculative Store Bypass
>> SBBD = Speculative Store Bypass Disable
>>
>> Thomas likes 'MDD', Jon likes 'SBB', but he is also fine with 'SBBD'.
> 
> I'm refactoring your patches to recognize either "mdd" or "ssbd" (double
> s, not sbb :) ) on x86 and then other arches can target the latter one.

I'm also changing "md_mitigation" to "mdd_mitigation" and standardizing
on "md_" and "MDD_" prefixes. If we are to "enable" mitigations rather
than disabling features, then let's make sure that's what we're always
referring to it in that manner. Otherwise it's confusing to see "MD_ON"
meaning that MDD is set and we are actually not enabling MD. So I change
that to "MDD_ON", etc.

Jon.

-- 
Computer Architect | Sent from my Fedora powered laptop


  reply	other threads:[~2018-04-18  4:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 18:26 [MODERATED] GPZv4 Jon Masters
2018-04-17 19:31 ` [MODERATED] GPZv4 Borislav Petkov
2018-04-17 19:56   ` Jon Masters
2018-04-17 20:37     ` Borislav Petkov
2018-04-17 21:03       ` Jon Masters
2018-04-17 21:20         ` Borislav Petkov
2018-04-17 21:22         ` GPZv4 Thomas Gleixner
2018-04-17 21:25           ` [MODERATED] GPZv4 Jiri Kosina
2018-04-17 21:38             ` Jon Masters
2018-04-17 21:43               ` Jiri Kosina
2018-04-17 22:01                 ` GPZv4 Thomas Gleixner
2018-04-17 22:02                   ` [MODERATED] GPZv4 Jon Masters
2018-04-18  2:48                     ` Konrad Rzeszutek Wilk
2018-04-18  3:44                       ` Jon Masters
2018-04-18  4:09                         ` Jon Masters [this message]
2018-04-18  4:18                           ` Jon Masters
2018-04-18  4:56                         ` Jon Masters
2018-04-18  7:06                         ` Jon Masters
2018-04-18  8:54                       ` GPZv4 Thomas Gleixner
2018-04-18 13:22                         ` [MODERATED] GPZv4 Jon Masters
2018-04-18 14:04                           ` GPZv4 Thomas Gleixner
2018-04-18 14:07                             ` [MODERATED] GPZv4 Jon Masters
2018-04-18 14:52                               ` Konrad Rzeszutek Wilk
2018-04-18 15:02                                 ` Jon Masters
2018-04-18 21:12                                   ` Konrad Rzeszutek Wilk
2018-04-18 21:20                                     ` Jon Masters
2018-04-17 21:36           ` Jon Masters

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=ba539d56-6d53-07c1-167a-a8951ac5b3c8@redhat.com \
    --to=jcm@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 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.