From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Is: Sleep states ?Was:Re: SSB status - V18 pushed out
Date: Fri, 18 May 2018 09:54:57 -0400 [thread overview]
Message-ID: <20180518135457.GB18423@char.us.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805172245510.1698@nanos.tec.linutronix.de>
On Thu, May 17, 2018 at 10:53:28PM +0200, speck for Thomas Gleixner wrote:
> Folks,
>
> we finally reached a stable state with the SSB patches. I've updated all 3
> branches master/linux-4.16.y/linux-4.14.y in the repo and attached the
> resulting git bundles. They merge cleanly on top of the current HEADs of
> the relevant trees.
>
> The lot survived light testing on my side and it would be great if everyone
> involved could expose it to their test scenarios.
>
> Thanks to everyone who participated in that effort (patches, review,
> testing ...)!
Yeey! Thank you.
I was reading the updated Intel doc today (instead of skim reading it) and it mentioned:
"Intel recommends that the SSBD MSR bit be cleared when in a sleep state on such processors."
We don't seem to be doing that?
To do that we would need to:
1) Revert 4b59bdb56945 x86/bugs: Remove x86_spec_ctrl_set()
2) Peppering
if (static_cpu_has(X86_FEATURE_SPEC_STORE_BYPASS_DISABLE))
x86_spec_ctrl_set(~SPEC_CTRL_SSBD);
[when enterring sleep state]
and:
if (static_cpu_has(X86_FEATURE_SPEC_STORE_BYPASS_DISABLE))
x86_spec_ctrl_set(SPEC_CTRL_SSBD);
[when coming out]
in mwait_idle_with_hints, mwait_idle, and native_play_dead
Or alternatively fiddle with the MSR directly.
3) And then uhuh, I am not sure how you would want to deal when the applications
are running. That is when the !static_cpu_has(X86_FEATURE_SPEC_STORE_BYPASS_DISABLE)
but still want the MSR toggled.
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2018-05-18 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 20:53 SSB status - V18 pushed out Thomas Gleixner
2018-05-18 13:54 ` Konrad Rzeszutek Wilk [this message]
2018-05-18 14:29 ` Is: Sleep states ?Was:Re: " Thomas Gleixner
2018-05-18 19:50 ` [MODERATED] Encrypted Message Tim Chen
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=20180518135457.GB18423@char.us.oracle.com \
--to=konrad.wilk@oracle.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.