From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch 0/7] SSB v2.1-jcm
Date: Sun, 22 Apr 2018 13:40:44 -0400 [thread overview]
Message-ID: <20180422174043.GA8212@localhost.localdomain> (raw)
In-Reply-To: <20180422093523.048337870@washington.bos.jonmasters.org>
On Sun, Apr 22, 2018 at 05:35:23AM -0400, speck for jcm_at_redhat.com wrote:
> Hi Konrad,
>
> I've taken the liberty of reworking some of the patches with feedback so far.
Thank you. I spent most of the day yesterday and today being outside so
appreciate you doing all the work :-)
In the future - please mangle the subject of the patches in the git tree as
GPG does not encrypt the Subject: header nor the inline GPG
(filename=0006-x86-spec_store_bypass-Provide-boot-parameters-to-sel.patch)
so all the names of the patches are visible.
> Please feel free to do whatever you like with these if it helps you, and
> you're the owner of the series so review can wait for your next batch.
Tomorrow morning. After I enjoy the rocky beach.
>
> I didn't include the AMD part. It'll need reworking in any case since you want
> to make sure you don't use the X86_FEATURE_MDD like it was. They don't have
> that SPEC_CTRL bit. My update adds a synthetic X86_FEATURE_USE_MDD and we
> should probably further fix that, and add a similar one for AMD's feature.
Borislav wants it to be inline with Intel's MDD so will use the same
name.
>
> The KVM part won't change much so I didn't repost that part either.
>
> Since v2.0:
> - Reworked patches 1-7 with feedback (except for Bosilav's goto comments in #5)
>
> Jon.
next prev parent reply other threads:[~2018-04-22 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 9:35 [MODERATED] [patch 0/7] SSB v2.1-jcm jcm
2018-04-22 17:40 ` Konrad Rzeszutek Wilk [this message]
2018-04-22 19:24 ` [MODERATED] " Borislav Petkov
2018-04-22 19:54 ` Jon Masters
2018-04-23 0:13 ` Linus Torvalds
2018-04-23 1:24 ` 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=20180422174043.GA8212@localhost.localdomain \
--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 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.