All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch 06/11] [PATCH v2 06/10] Linux Patch #6
Date: Fri, 20 Apr 2018 19:25:05 +0200	[thread overview]
Message-ID: <20180420172505.GN13977@pd.tnic> (raw)
In-Reply-To: <20180420022613.203909041@localhost.localdomain>

On Thu, Apr 19, 2018 at 10:25:46PM -0400, speck for konrad.wilk_at_oracle.com wrote:
> x86/ssb: Provide boot parameters to select which SSB/MD mitigation to use
> 
> mdd stands for "Memory Disambiguation Disable". It is used to disable
> a common industry performance optimization known as "Speculative
> Store Bypass" in which loads from addresses to which a recent store
> has occurred may (speculatively) see an older value. Intel refers
> to this feature as "Memory Disambiguation", which is part of their
> "Smart Memory Access" capability in Haswell and later processors.

...

> +static enum ssb_mitigation_cmd __init ssb_parse_cmdline(void)
> +{
> +	char arg[20];
> +	int ret, i;
> +	enum ssb_mitigation_cmd cmd = SSB_CMD_AUTO;
> +
> +	/*
> +	 * On Intel it is exposed in CPUID as Memory Disambiguation Disable
> +	 * bit.
> +	 */
> +	if (!boot_cpu_has(X86_FEATURE_MDD))
> +                return SSB_CMD_NONE;

Some whitespace damage?

ERROR: code indent should use tabs where possible
#247: FILE: arch/x86/kernel/cpu/bugs.c:391:
+                return SSB_CMD_NONE;$

WARNING: please, no spaces at the start of a line
#247: FILE: arch/x86/kernel/cpu/bugs.c:391:
+                return SSB_CMD_NONE;$


-- 
Regards/Gruss,
    Boris.

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

  parent reply	other threads:[~2018-04-20 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20  2:25 [MODERATED] [patch 06/11] [PATCH v2 06/10] Linux Patch #6 konrad.wilk
2018-04-20  5:28 ` [MODERATED] " Jon Masters
2018-04-20 11:21 ` Peter Zijlstra
2018-04-20 15:33   ` Jon Masters
2018-04-20 15:58     ` Konrad Rzeszutek Wilk
2018-04-20 16:11       ` Jon Masters
2018-04-20 17:25 ` Borislav Petkov [this message]
2018-04-21  9:21 ` 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=20180420172505.GN13977@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.