All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v3 06/10] [PATCH v3 6/9] Linux Patch #6
Date: Mon, 23 Apr 2018 23:06:43 +0200	[thread overview]
Message-ID: <20180423210643.GO24245@pd.tnic> (raw)
In-Reply-To: <nycvar.YFH.7.76.1804232242250.28129@cbobk.fhfr.pm>

On Mon, Apr 23, 2018 at 10:45:10PM +0200, speck for Jiri Kosina wrote:
> Don't we really want it to appear in /proc/cpuinfo though?
> 
> At the end of the day, it really is about toggling an internal CPU feature 
> behavior, so I'd say it belongs there.
> 
> We even have PTI there, and this is way more actually really internal to 
> the CPU.

Well, the thing is that other CPUs have store bypassing too but they
don't necessarily have the disabling bit.

So if anything, we should use the X86_BUG_CPU_SPEC_STORE_BYPASS
bit so that it appears in the bugs: line.

I mean, one of the two: X86_FEATURE_STBUF_BYPASS or
X86_BUG_CPU_SPEC_STORE_BYPASS is redundant AFAICT so we can stick with
the X86_BUG one.

Also, we have the state in /sys/devices/system/cpu/vulnerabilities/ too,
in case something needs it.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

  reply	other threads:[~2018-04-23 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 17:11 [MODERATED] [PATCH v3 06/10] [PATCH v3 6/9] Linux Patch #6 konrad.wilk
2018-04-23 18:34 ` [MODERATED] " Borislav Petkov
2018-04-23 20:45   ` Jiri Kosina
2018-04-23 21:06     ` Borislav Petkov [this message]
2018-04-24  0:19   ` Konrad Rzeszutek Wilk
2018-04-23 18:57 ` Borislav Petkov
2018-04-23 19:08   ` Borislav Petkov

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=20180423210643.GO24245@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.