From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch 07/11] [PATCH v2 07/10] Linux Patch #7
Date: Sat, 21 Apr 2018 21:25:10 +0200 [thread overview]
Message-ID: <20180421192509.GD18575@pd.tnic> (raw)
In-Reply-To: <20180421122117.GA5337@localhost.localdomain>
On Sat, Apr 21, 2018 at 08:21:17AM -0400, speck for Konrad Rzeszutek Wilk wrote:
> Perhaps instead of X86_FEATURE_MDD we should set on AMD only this CPU flag:
> X86_FEATURE_SSBD
>
> And on Intel have both:
> X86_FEATURE_MDD
> X86_FEATURE_SSBD
I prefer X86_FEATURE_MDD and X86_FEATURE_USE_MDD which is
straight-forward and in line with the other mitigations. And we query
the USE_MDD flag only. The MDD one will be for /proc/cpuinfo and USE_MDD
used by the code.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2018-04-21 19:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 2:25 [MODERATED] [patch 07/11] [PATCH v2 07/10] Linux Patch #7 konrad.wilk
2018-04-20 17:42 ` [MODERATED] " Borislav Petkov
2018-04-21 3:27 ` Konrad Rzeszutek Wilk
2018-04-21 9:03 ` Borislav Petkov
2018-04-21 12:21 ` Konrad Rzeszutek Wilk
2018-04-21 19:25 ` Borislav Petkov [this message]
2018-04-21 21:41 ` Linus Torvalds
2018-04-21 22:09 ` Borislav Petkov
2018-04-21 22:13 ` Jon Masters
2018-04-21 22:35 ` Borislav Petkov
2018-04-21 22:54 ` Jon Masters
2018-04-22 1:26 ` Linus Torvalds
2018-04-22 3:18 ` Jon Masters
2018-04-22 9:35 ` Borislav Petkov
2018-04-22 9:53 ` Jon Masters
2018-04-22 10:34 ` Borislav Petkov
2018-04-22 15:16 ` Jon Masters
2018-04-23 14:30 ` Thomas Gleixner
2018-04-23 14:34 ` [MODERATED] " Jon Masters
2018-04-23 17:06 ` Jon Masters
2018-04-23 17:51 ` Konrad Rzeszutek Wilk
2018-04-23 18:01 ` Jon Masters
2018-04-23 18:02 ` Jon Masters
2018-04-23 18:05 ` Linus Torvalds
2018-04-23 18:09 ` Jon Masters
2018-04-23 22:23 ` Thomas Gleixner
2018-04-23 22:30 ` [MODERATED] " Jiri Kosina
2018-04-23 23:03 ` Andi Kleen
2018-04-24 5:32 ` Jiri Kosina
2018-04-23 22:31 ` Andi Kleen
2018-04-24 0:44 ` Jon Masters
2018-04-23 23:36 ` Tim Chen
2018-04-23 21:13 ` Konrad Rzeszutek Wilk
2018-04-23 21:23 ` Linus Torvalds
2018-04-23 21:33 ` Jiri Kosina
2018-04-23 22:18 ` Andi Kleen
2018-04-24 0:34 ` Jon Masters
2018-04-21 22:09 ` 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=20180421192509.GD18575@pd.tnic \
--to=bp@suse.de \
--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.