From: Tim Chen <tim.c.chen@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch V7 15/15] SBB 15
Date: Mon, 30 Apr 2018 13:12:28 -0700 [thread overview]
Message-ID: <bf96b696-641c-7130-94e8-56f0937cd174@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1804302134290.1596@nanos.tec.linutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1286 bytes --]
On 04/30/2018 12:36 PM, speck for Thomas Gleixner wrote:
> On Mon, 30 Apr 2018, speck for Tim Chen wrote:
>
>> On 04/29/2018 12:31 PM, speck for Thomas Gleixner wrote:
>>
>>> +static int sbb_prctl_set(unsigned long ctrl)
>>> +{
>>> + bool rds = !!test_tsk_thread_flag(current, TIF_RDS);
>>> +
>>> + if (ssb_mode != SPEC_STORE_BYPASS_PRCTL)
>>> + return -ENXIO;
>>
>> Perhaps we should not use the prctl if we don't have
>> the SSB bug. Something like:
>>
>> if (ssb_mode != SPEC_STORE_BYPASS_PRCTL ||
>> !boot_cpu_has_bug(X86_BUG_SPEC_STORE_BYPASS))
>> return -ENXIO;
>
> What? If the CPU does not have the bug then the kernel does not enable
> PRCTL mode at all unless
>
> 1) RDS is available
>
> AND
>
> 2) The user enforced PRTCL mode on the kernel command line.
>
> So what exactly are you trying to solve?
Right, we will only do the PRCTL only for the case when
admin explicitly ask for it at kernel command line.
We'll let the admin have the choice to do prctl, if he
explicitly ask for it. Even though it
is unnecessary for cpus that don't have the SSB bug and
there will be some added cost in changing the MSR on context
switches. Just want to clear in my mind that this is the choice
we are making.
Tim
next prev parent reply other threads:[~2018-04-30 20:12 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 19:30 [patch V7 00/15] SBB 0 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 01/15] SBB 1 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 02/15] SBB 2 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 03/15] SBB 3 Thomas Gleixner
2018-04-29 23:31 ` [MODERATED] " Linus Torvalds
2018-04-30 2:50 ` Konrad Rzeszutek Wilk
2018-04-30 7:09 ` David Woodhouse
2018-04-29 19:30 ` [patch V7 04/15] SBB 4 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 05/15] SBB 5 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 06/15] SBB 6 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 07/15] SBB 7 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 08/15] SBB 8 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 09/15] SBB 9 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 10/15] SBB 10 Thomas Gleixner
2018-04-30 0:16 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-30 7:49 ` Thomas Gleixner
2018-04-29 19:30 ` [patch V7 11/15] SBB 11 Thomas Gleixner
2018-04-29 19:30 ` [patch V7 12/15] SBB 12 Thomas Gleixner
2018-04-30 1:33 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-29 19:30 ` [patch V7 13/15] SBB 13 Thomas Gleixner
2018-04-30 1:48 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-30 2:39 ` Konrad Rzeszutek Wilk
2018-04-30 3:17 ` Jon Masters
2018-04-30 8:35 ` Thomas Gleixner
2018-04-30 2:20 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-30 2:36 ` Konrad Rzeszutek Wilk
2018-04-30 17:28 ` Konrad Rzeszutek Wilk
2018-04-29 19:30 ` [patch V7 14/15] SBB 14 Thomas Gleixner
2018-04-30 2:14 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-30 5:57 ` Thomas Gleixner
2018-04-30 15:49 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-29 19:31 ` [patch V7 15/15] SBB 15 Thomas Gleixner
2018-04-30 2:32 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-30 15:56 ` Konrad Rzeszutek Wilk
2018-04-30 16:07 ` Thomas Gleixner
2018-04-30 19:30 ` [MODERATED] " Tim Chen
2018-04-30 19:36 ` Thomas Gleixner
2018-04-30 20:12 ` Tim Chen [this message]
2018-04-30 20:20 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-30 20:44 ` Tim Chen
2018-04-30 20:28 ` Thomas Gleixner
2018-04-30 20:09 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-29 20:14 ` [patch V7 00/15] SBB 0 Thomas Gleixner
2018-04-29 20:35 ` [MODERATED] " Borislav Petkov
2018-04-29 20:46 ` Konrad Rzeszutek Wilk
2018-04-29 20:57 ` Thomas Gleixner
2018-04-29 21:40 ` [MODERATED] " Borislav Petkov
2018-04-29 20:55 ` Thomas Gleixner
2018-04-29 22:05 ` Thomas Gleixner
2018-04-30 0:06 ` [MODERATED] " Jon Masters
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=bf96b696-641c-7130-94e8-56f0937cd174@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--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.