From: Mathieu Chouquet-Stringer <me@mathieu.digital>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Borislav Petkov <bp@alien8.de>,
Stephen Kitt <steve@sk2.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
"Guilherme G. Piccoli" <gpiccoli@canonical.com>,
Eric Biggers <ebiggers@google.com>,
Qais Yousef <qais.yousef@arm.com>,
Naoki Hayama <naoki.hayama@lineo.co.jp>,
Yue Hu <huyue2@yulong.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Update documentation to reflect what TAINT_CPU_OUT_OF_SPEC means nowadays
Date: Wed, 9 Dec 2020 00:11:36 +0100 [thread overview]
Message-ID: <20201208231136.GA1455290@weirdfishes> (raw)
In-Reply-To: <1254edd7-25ee-b73d-da2c-194d38ba7890@infradead.org>
Hello,
On Tue, Dec 08, 2020 at 09:58:32AM -0800, Randy Dunlap wrote:
> On 12/8/20 9:54 AM, Jonathan Corbet wrote:
> > On Wed, 2 Dec 2020 16:32:43 +0100
> > Mathieu Chouquet-Stringer <me@mathieu.digital> wrote:
> >> Signed-off-by: Mathieu Chouquet-Stringer <me@mathieu.digital>
> >
> > Hearing no objection, I've applied this.
Thanks Jon.
> Hm, I was glad to read this new info since my old testing laptop
> now tells me that it needs a microcode update. :(
In my case I first saw the error because tuned uses
x86_energy_perf_policy which uses to poke at MSRs [1]. And that was
tainting my kernel and I initially couldn't understand why.
It's been fixed but will be released in an upcoming kernel version (it's
in tip at the moment [2]).
Thanks to Borislav for work and for helping me out!
[1] https://lore.kernel.org/lkml/20201117210018.GA4247@weirdfishes/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=fe0a5788624c8b8f113a35bbe4636e37f9321241
--
Mathieu Chouquet-Stringer me@mathieu.digital
The sun itself sees not till heaven clears.
-- William Shakespeare --
prev parent reply other threads:[~2020-12-08 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:32 [PATCH] Update documentation to reflect what TAINT_CPU_OUT_OF_SPEC means nowadays Mathieu Chouquet-Stringer
2020-12-08 17:54 ` Jonathan Corbet
2020-12-08 17:58 ` Randy Dunlap
2020-12-08 23:11 ` Mathieu Chouquet-Stringer [this message]
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=20201208231136.GA1455290@weirdfishes \
--to=me@mathieu.digital \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=ebiggers@google.com \
--cc=gpiccoli@canonical.com \
--cc=huyue2@yulong.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naoki.hayama@lineo.co.jp \
--cc=qais.yousef@arm.com \
--cc=rdunlap@infradead.org \
--cc=steve@sk2.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