From: Josh Poimboeuf <jpoimboe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Paul Mackerras <paulus@samba.org>,
"H . Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-s390@vger.kernel.org, x86@kernel.org,
Will Deacon <will.deacon@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Waiman Long <longman@redhat.com>,
linux-arch@vger.kernel.org, Jon Masters <jcm@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tyler Hicks <tyhicks@canonical.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH RFC 0/5] cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options
Date: Thu, 4 Apr 2019 11:44:10 -0500 [thread overview]
Message-ID: <cover.1554396090.git.jpoimboe@redhat.com> (raw)
Keeping track of the number of mitigations for all the CPU speculation
bugs has become overwhelming for many users. It's getting more and more
complicated to decide which mitigations are needed for a given
architecture. Complicating matters is the fact that each arch tends to
it own custom way to mitigate the same vulnerability.
Most users fall into a few basic categories:
a) they want all CPU speculation mitigations off;
b) they want all reasonable mitigations on, with SMT enabled even if
it's vulnerable; or
c) they want all reasonable mitigations on, with SMT disabled if
vulnerable.
Define a set of curated, arch-independent options, each of which is an
aggregation of existing options:
- cpu_spec_mitigations=off: Disable all mitigations.
- cpu_spec_mitigations=auto: [default] Enable all the default
mitigations, but leave SMT enabled, even if it's vulnerable.
- cpu_spec_mitigations=auto,nosmt: Enable all the default mitigations,
disabling SMT if needed by a mitigation.
Josh Poimboeuf (5):
cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options
x86/speculation: Add support for 'cpu_spec_mitigations=' cmdline
options
powerpc/speculation: Add support for 'cpu_spec_mitigations=' cmdline
options
s390/speculation: Add support for 'cpu_spec_mitigations=' cmdline
options
arm64/speculation: Add support for 'cpu_spec_mitigations=' cmdline
options
.../admin-guide/kernel-parameters.txt | 42 +++++++++++++++++++
arch/arm64/kernel/cpu_errata.c | 4 ++
arch/arm64/kernel/cpufeature.c | 6 +++
arch/powerpc/kernel/security.c | 6 +--
arch/powerpc/kernel/setup_64.c | 2 +-
arch/s390/kernel/nospec-branch.c | 4 +-
arch/x86/include/asm/processor.h | 1 +
arch/x86/kernel/cpu/bugs.c | 32 ++++++++++++--
arch/x86/kvm/vmx/vmx.c | 2 +
arch/x86/mm/pti.c | 4 +-
include/linux/cpu.h | 8 ++++
kernel/cpu.c | 15 +++++++
12 files changed, 116 insertions(+), 10 deletions(-)
--
2.17.2
next reply other threads:[~2019-04-04 16:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 16:44 Josh Poimboeuf [this message]
2019-04-04 16:44 ` [PATCH RFC 1/5] cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options Josh Poimboeuf
2019-04-04 16:49 ` Josh Poimboeuf
2019-04-05 13:12 ` Borislav Petkov
2019-04-05 14:20 ` Josh Poimboeuf
2019-04-05 15:20 ` Borislav Petkov
2019-04-05 16:01 ` Borislav Petkov
2019-04-05 16:18 ` Josh Poimboeuf
2019-04-10 5:48 ` Michael Ellerman
2019-04-10 8:30 ` Borislav Petkov
2019-04-10 12:10 ` Thomas Gleixner
2019-04-11 13:15 ` Josh Poimboeuf
2019-04-12 2:41 ` Michael Ellerman
2019-04-12 2:29 ` Michael Ellerman
2019-04-04 16:44 ` [PATCH RFC 2/5] x86/speculation: Add support for " Josh Poimboeuf
2019-04-05 13:57 ` Borislav Petkov
2019-04-05 14:31 ` Josh Poimboeuf
2019-04-05 15:26 ` Borislav Petkov
2019-04-05 16:05 ` Josh Poimboeuf
2019-04-05 15:18 ` Randy Dunlap
2019-04-05 15:30 ` Josh Poimboeuf
2019-04-04 16:44 ` [PATCH RFC 3/5] powerpc/speculation: " Josh Poimboeuf
2019-04-04 19:49 ` Jiri Kosina
2019-04-04 20:01 ` Timothy Pearson
2019-04-10 6:06 ` Michael Ellerman
2019-04-11 4:02 ` Josh Poimboeuf
2019-04-04 16:44 ` [PATCH RFC 4/5] s390/speculation: " Josh Poimboeuf
2019-04-04 16:44 ` [PATCH RFC 5/5] arm64/speculation: " Josh Poimboeuf
2019-04-05 14:39 ` Steven Price
2019-04-05 14:43 ` Josh Poimboeuf
2019-04-05 14:44 ` Will Deacon
2019-04-05 16:03 ` Josh Poimboeuf
2019-04-04 16:50 ` [PATCH RFC 0/5] cpu/speculation: Add " Waiman Long
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=cover.1554396090.git.jpoimboe@redhat.com \
--to=jpoimboe@redhat.com \
--cc=aarcange@redhat.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=jcm@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tyhicks@canonical.com \
--cc=will.deacon@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).