All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Sneddon <daniel.sneddon@linux.intel.com>
To: Sean Christopherson <seanjc@google.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Subject: Re: [PATCH 0/3] x86/cpu: Fix SPECULATIVE_MITIGATION=n kernels
Date: Tue, 9 Apr 2024 11:55:43 -0700	[thread overview]
Message-ID: <976c385e-2174-464e-9afd-de4cb46f63b8@linux.intel.com> (raw)
In-Reply-To: <20240409175108.1512861-1-seanjc@google.com>

On 4/9/24 10:51, Sean Christopherson wrote:
> Fix the handling of SPECULATION_MITIGATIONS=n so that it actually does
> what it says it does: disable any and all mitigations.
> 
> And because I don't see a way to provide sane behavior for overriding
> SPECULATION_MITIGATIONS=n at runtime, explicitly disallow doing so via
> the "mitigations" kernel parameter, e.g. so that the user at least knows
> that their system is still likely vulnerable to a variety of issues.
> 
> Sean Christopherson (3):
>   x86/cpu: Actually turn off mitigations by default for
>     SPECULATION_MITIGATIONS=n
>   x86/cpu: Disable BHI mitigation by default when
>     SPECULATION_MITIGATIONS=n
>   x86/cpu: Ignore "mitigations" kernel parameter if
>     SPECULATION_MITIGATIONS=n
> 
>  Documentation/admin-guide/kernel-parameters.txt |  3 +++
>  arch/x86/Kconfig                                | 10 +++++++---
>  arch/x86/kernel/cpu/bugs.c                      |  6 +++---
>  kernel/cpu.c                                    |  5 ++++-
>  4 files changed, 17 insertions(+), 7 deletions(-)
> 
> 
> base-commit: 2c71fdf02a95b3dd425b42f28fd47fb2b1d22702

Reviewed-by: Daniel Sneddon <daniel.sneddon@linux.intel.com>

      parent reply	other threads:[~2024-04-09 18:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 17:51 [PATCH 0/3] x86/cpu: Fix SPECULATIVE_MITIGATION=n kernels Sean Christopherson
2024-04-09 17:51 ` [PATCH 1/3] x86/cpu: Actually turn off mitigations by default for SPECULATION_MITIGATIONS=n Sean Christopherson
2024-04-10 14:31   ` [tip: x86/urgent] " tip-bot2 for Sean Christopherson
2024-04-13  1:53   ` [PATCH 1/3] " Stephen Rothwell
2024-04-13  1:53     ` Stephen Rothwell
2024-04-13  9:27     ` Michael Ellerman
2024-04-13  9:27       ` Michael Ellerman
2024-04-13  9:38       ` Michael Ellerman
2024-04-13  9:38         ` Michael Ellerman
2024-04-14 22:42         ` Stephen Rothwell
2024-04-14 22:42           ` Stephen Rothwell
2024-04-15 11:16         ` Geert Uytterhoeven
2024-04-15 11:16           ` Geert Uytterhoeven
2024-04-15 14:31           ` Sean Christopherson
2024-04-15 14:31             ` Sean Christopherson
2024-04-16 11:06             ` Michael Ellerman
2024-04-16 11:06               ` Michael Ellerman
2024-04-19 14:03             ` Will Deacon
2024-04-19 14:03               ` Will Deacon
2024-04-19 14:06               ` Sean Christopherson
2024-04-19 14:06                 ` Sean Christopherson
2024-04-19 14:38                 ` Will Deacon
2024-04-19 14:38                   ` Will Deacon
2024-04-15 11:13   ` Geert Uytterhoeven
2024-04-15 11:13     ` Geert Uytterhoeven
2024-04-09 17:51 ` [PATCH 2/3] x86/cpu: Disable BHI mitigation by default when SPECULATION_MITIGATIONS=n Sean Christopherson
2024-04-10 14:31   ` [tip: x86/urgent] " tip-bot2 for Sean Christopherson
2024-04-09 17:51 ` [PATCH 3/3] x86/cpu: Ignore "mitigations" kernel parameter if SPECULATION_MITIGATIONS=n Sean Christopherson
2024-04-10 14:18   ` Ingo Molnar
2024-04-09 18:55 ` Daniel Sneddon [this message]

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=976c385e-2174-464e-9afd-de4cb46f63b8@linux.intel.com \
    --to=daniel.sneddon@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.