From: Borislav Petkov <bp@alien8.de>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Kosina <jikos@kernel.org>, Waiman Long <longman@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Jon Masters <jcm@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-s390@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tyler Hicks <tyhicks@canonical.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH RFC 1/5] cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options
Date: Fri, 5 Apr 2019 18:01:36 +0200 [thread overview]
Message-ID: <20190405160136.GI23348@zn.tnic> (raw)
Message-ID: <20190405160136.4tt7RfRZIEc9AAQ_k2zJ0AX2Oh1p-cAAYSJuQZnqAA0@z> (raw)
In-Reply-To: <20190405152059.GG23348@zn.tnic>
Thinking about this more, we can shave off the first 4 chars and have it
be:
spec_mitigations=
I think it is painfully clear which speculation mitigations we mean. And
the other switches don't have "cpu_" prefixes too so...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-04-05 16:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190404164410.FyWPYQnV_AC5qVM5C3Jcx1ysIg_8piJ6yY46gIDHjZU@z>
2019-04-04 16:44 ` [PATCH RFC 0/5] cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options Josh Poimboeuf
[not found] ` <20190404164411.Gy3S4HmcWfyKhBREvXHY5FPLSwAUc9Z1y2KsB07Pmm4@z>
2019-04-04 16:44 ` [PATCH RFC 1/5] " Josh Poimboeuf
[not found] ` <20190404164908.r4AYeBs3-dkedAjA4YfFz402EZXqM30A9pdq22wsHN4@z>
2019-04-04 16:49 ` Josh Poimboeuf
[not found] ` <20190405131211.Q2NjuOAdnJlvlrA0AG2RZhInDwko2zhWKJScqKXcYKQ@z>
2019-04-05 13:12 ` Borislav Petkov
[not found] ` <20190405142048.qJvWe7mR5XJIzpc5altU1UI3DVF6Fm9Yjvd8BKsNEy4@z>
2019-04-05 14:20 ` Josh Poimboeuf
[not found] ` <20190405152059.08_dCkDXzn8b5SW1QVcJq5DyPHq85ZVw5ngPousboME@z>
2019-04-05 15:20 ` Borislav Petkov
[not found] ` <20190405160136.4tt7RfRZIEc9AAQ_k2zJ0AX2Oh1p-cAAYSJuQZnqAA0@z>
2019-04-05 16:01 ` Borislav Petkov [this message]
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
[not found] ` <20190404164412.goQjNbtLtNK5Xhety5Y2SrWdf5jOoB1EZ0aqJLJdxHw@z>
2019-04-04 16:44 ` [PATCH RFC 2/5] x86/speculation: Add support for " Josh Poimboeuf
[not found] ` <20190405135712.h8C5NFnWFSMYwkqvOodZqwvUhkB0wm8DZ17FpWjVXoY@z>
2019-04-05 13:57 ` Borislav Petkov
[not found] ` <20190405143101.ehopmxN-UUs4udfFq_s3rur7f147JR8sKQYe2BlTfXQ@z>
2019-04-05 14:31 ` Josh Poimboeuf
[not found] ` <20190405152650.DqBCc8B5pVR8hG3DaAapjrpOZ6Bf20rzQgqS0JGbMCs@z>
2019-04-05 15:26 ` Borislav Petkov
2019-04-05 16:05 ` Josh Poimboeuf
[not found] ` <20190405151809.loO3BRPkxdSIbjhaOkHcgSzX7AEXml11-UID3nahj9s@z>
2019-04-05 15:18 ` Randy Dunlap
[not found] ` <20190405153048.O_Br143nVxVMU9csW4aOtbQpM08-f4KvQ02DvzZx_s8@z>
2019-04-05 15:30 ` Josh Poimboeuf
[not found] ` <20190404164413.IgIvLuMu4GLkDdvSHFyBaGh9dXrNjMsr8AmhWG65Rf0@z>
2019-04-04 16:44 ` [PATCH RFC 3/5] powerpc/speculation: " Josh Poimboeuf
[not found] ` <20190404194905.qR9T-btAf0BVt0YfG6H0h19JLAE1AXADvXFhopuL0f4@z>
2019-04-04 19:49 ` Jiri Kosina
[not found] ` <20190404200104.INe2nbO9Bg__dm-H_nSr2d4XkjWKVig0XnWHSYky-mk@z>
2019-04-04 20:01 ` Timothy Pearson
2019-04-10 6:06 ` Michael Ellerman
2019-04-11 4:02 ` Josh Poimboeuf
[not found] ` <20190404164414.cktiJTWLfAEnxNs2wsW9YNTw8sV7S6dkTOl6n1bXI5U@z>
2019-04-04 16:44 ` [PATCH RFC 4/5] s390/speculation: " Josh Poimboeuf
[not found] ` <20190404164415.7sB56buW6sV8GzaJvfyTl6CefUF2WNywA7izu14xWn8@z>
2019-04-04 16:44 ` [PATCH RFC 5/5] arm64/speculation: " Josh Poimboeuf
[not found] ` <20190405143958.68mhX8hptXUHk3hwMQ9WfDPhB-0ONhSHKqYsnMrEJjs@z>
2019-04-05 14:39 ` Steven Price
[not found] ` <20190405144356.9p1BhXsIjOJE5oKY8oqxUMAecWPbYA158YjKfCNCYAk@z>
2019-04-05 14:43 ` Josh Poimboeuf
[not found] ` <20190405144414.nk-UumeN0sm2XyB05ZZDspKvSwX8qAkPSsQ9oDw_tKQ@z>
2019-04-05 14:44 ` Will Deacon
2019-04-05 16:03 ` Josh Poimboeuf
[not found] ` <20190404165054.iJV6ETT60vreD-Rl1FsxCk4pKUcybxmjvQFzn5MlZDs@z>
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=20190405160136.GI23348@zn.tnic \
--to=bp@alien8.de \
--cc=aarcange@redhat.com \
--cc=benh@kernel.crashing.org \
--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=jpoimboe@redhat.com \
--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=mpe@ellerman.id.au \
--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