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 10:07:44 -0400	[thread overview]
Message-ID: <1c1c86c5-664b-42a4-44bb-fd8853a55e41@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1804181552350.1534@nanos.tec.linutronix.de>

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

On 04/18/2018 10:04 AM, speck for Thomas Gleixner wrote:
> On Wed, 18 Apr 2018, speck for Jon Masters wrote:
>> On 04/18/2018 04:54 AM, speck for Thomas Gleixner wrote:
>>> On Tue, 17 Apr 2018, 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 fine with SBBD as well. It's the same semantics as the other knobs as
>>> it controls the mitigation.
>>
>> Great. Might I recommend keeping what I sent to Konrad (both mdd and
>> ssbd recognized), but do whichever you like Konrad ;)
>>
>>> So can we for now just start with the minimal set of auto, off, on and then
>>> hash out the prctl or not question. The big hammer is the most important
>>> piece we need to have ready for merging when the embargo is lifted.
>>
>> I've sent the big hammer patches last night. Konrad's original set with
>> a few fixes, and just does "auto", "off", "on", and tested working ok.
> 
> Can we please have proper mail submitted patches? These tarballs are a
> PITA.

Leaving the ball with Konrad to review/post when he's happy.

Jon.

-- 
Computer Architect | Sent from my Fedora powered laptop


  reply	other threads:[~2018-04-18 14:07 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
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                             ` Jon Masters [this message]
2018-04-18 14:52                               ` [MODERATED] GPZv4 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=1c1c86c5-664b-42a4-44bb-fd8853a55e41@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.