Re: [PATCH RFC 1/5] cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options

From
Michael Ellerman <mpe@ellerman.id.au>
Date
2019-04-12 02:41:25
Also in
linux-arch, linux-arm-kernel, linux-s390, lkml
Reply to
Josh Poimboeuf, 2019-04-11
Josh Poimboeuf [off-list ref] writes:
On Wed, Apr 10, 2019 at 02:10:01PM +0200, Thomas Gleixner wrote:
quoted
On Wed, 10 Apr 2019, Michael Ellerman wrote:
quoted
Josh Poimboeuf [off-list ref] writes:
quoted
On Fri, Apr 05, 2019 at 06:01:36PM +0200, Borislav Petkov wrote:
quoted
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...
Sure, I'm ok with renaming it to that, if there are no objections.
What about when we have a mitigation for a non-speculation related bug :)
Those kind of silicon bugs are usually mitigated unconditionally.
Right.

But at least "mitigations=" is nice and short.  We could clarify in the
documentation that it doesn't apply to *all* mitigations, only the ones
which are optional and which can affect performance.

And it would give us the freedom to include any future "optional"
mitigations, spec or not.

I kind of like it.  But I could go either way.
Some of the published SMT attacks are not speculation based.

And arguably we already have an optional mitigation for those, ie. nosmt.

cheers
Thread (33 messages) 33 messages, 10 authors, last reply 2019-04-12
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help