From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v4 06/10] [PATCH v4 6/9] Linux Patch #6
Date: Wed, 25 Apr 2018 19:25:02 +0200 [thread overview]
Message-ID: <20180425172502.GF32574@pd.tnic> (raw)
In-Reply-To: <20180425153206.GA27641@localhost.localdomain>
On Wed, Apr 25, 2018 at 11:32:23AM -0400, speck for Konrad Rzeszutek Wilk wrote:
> We need two CPU bit flags. First to say:
>
> 1). I am able to mitigate. This will be via X86_FEATURE_RDS for both
> AMD and Intel.
>
> 2). I _want_ to mitigate. This will be via X86_FEATURE_SPEC_STORE_BYPASS_DISABLE
> to tell the init_amd_bd,init_amd_zn,init_amd_jg, and init_intel
> to do its magic.
Lemme paste from my earlier mail:
"
X86_BUG_SPEC_STORE_BYPASS - CPU is affected by bug
X86_FEATURE_SPEC_STORE_BYPASS_DISABLE - CPU can disable store bypassing
X86_FEATURE_SPEC_STORE_BYPASS_IN_USE - CPU has disabled store bypassing
"
So I meant to use X86_FEATURE_SPEC_STORE_BYPASS_DISABLE for "I am able
to mitigate".
You want to use it to denote "IN_USE". I think "IN_USE" is more telling:
if (... X86_FEATURE_SPEC_STORE_BYPASS_IN_USE)
disable MD
So we can do
X86_BUG_SPEC_STORE_BYPASS
X86_FEATURE_RDS
X86_FEATURE_SPEC_STORE_BYPASS_IN_USE
or
X86_BUG_SPEC_STORE_BYPASS
X86_FEATURE_RDS
X86_FEATURE_SPEC_STORE_BYPASS_DISABLE
as you want it.
Whatever - I'm all out of energy for bikeshedding so pick one and
document what it means.
--
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-25 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 3:16 [MODERATED] [PATCH v4 06/10] [PATCH v4 6/9] Linux Patch #6 konrad.wilk
2018-04-24 13:21 ` [MODERATED] " Borislav Petkov
2018-04-24 15:13 ` Linus Torvalds
2018-04-24 15:46 ` Konrad Rzeszutek Wilk
2018-04-24 16:36 ` Borislav Petkov
2018-04-24 18:07 ` Konrad Rzeszutek Wilk
2018-04-24 18:46 ` Borislav Petkov
2018-04-25 15:32 ` Konrad Rzeszutek Wilk
2018-04-25 17:25 ` Borislav Petkov [this message]
2018-04-25 16:12 ` Konrad Rzeszutek Wilk
2018-04-25 16:19 ` Konrad Rzeszutek Wilk
2018-04-25 17:29 ` Borislav Petkov
2018-04-25 17:26 ` Borislav Petkov
2018-04-25 16:51 ` Tim Chen
2018-04-25 17:38 ` Konrad Rzeszutek Wilk
2018-04-25 20:25 ` Tim Chen
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=20180425172502.GF32574@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.