From: Ben Hutchings <ben@decadent.org.uk>
To: Borislav Petkov <bp@alien8.de>,
Evalds Iodzevics <evalds.iodzevics@gmail.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
tglx@linutronix.de
Subject: Re: [PATCH] x86/microcode/intel: replace sync_core() with native_cpuid_reg(eax)
Date: Mon, 20 Apr 2020 14:33:30 +0100 [thread overview]
Message-ID: <7fb8e9ac69a1c03a673875dc39fcd8f94407abca.camel@decadent.org.uk> (raw)
In-Reply-To: <20200420093129.GA21839@zn.tnic>
[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]
On Mon, 2020-04-20 at 11:31 +0200, Borislav Petkov wrote:
> On Mon, Apr 20, 2020 at 03:00:37PM +0300, Evalds Iodzevics wrote:
> > sync_core() always jums past cpuid instruction on 32 bit machines
> > because data structure boot_cpu_data are not populated so early in boot.
>
> I'm guessing because boot_cpu_data.cpuid_level is not properly set and
> very early code in head_32.S sets it to -1 temporarily until the highest
> CPUID level has been detected (or not).
>
> But the microcode loading happens *before* that.
[...]
> Hrm, the original patch of mine did use native_cpuid_eax():
>
> 4167709bbf82 ("x86/microcode/intel: Add a helper which gives the microcode revision")
>
> but the backport:
>
> commit 98cc1464cfd6edf9dc7fa96aaaf596aae952029b
> Author: Borislav Petkov <bp@suse.de>
> Date: Mon Jan 9 12:41:45 2017 +0100
>
> x86/microcode/intel: Add a helper which gives the microcode revision
>
> commit 4167709bbf826512a52ebd6aafda2be104adaec9 upstream.
>
> Since on Intel we're required to do CPUID(1) first, before reading
> the microcode revision MSR, let's add a special helper which does the
> required steps so that we don't forget to do them next time, when we
> want to read the microcode revision.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Link: http://lkml.kernel.org/r/20170109114147.5082-4-bp@alien8.de
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> [bwh: Backported to 4.4:
> - Don't touch prev_rev variable in apply_microcode()
> - Keep using sync_core(), which will alway includes the necessary CPUID
> ^^^^^^^^^^^^^^^^^^^
>
> decided to use sync_core() for whatever reason. Perhaps because the
> native_cpuid* things weren't there. Adding Ben to Cc.
This commit didn't introduce the call to native_cpuid_eax(), but only
moved it. So I didn't think it made sense for the backport to change
from sync_core().
If it's important to use native_cpuid_eax() then these older branches
should presumably get backports of:
484d0e5c7943 x86/microcode/intel: Replace sync_core() with native_cpuid()
f3e2a51f568d x86/microcode: Use native CPUID to tickle out microcode revision
Ben.
> I believe this is the background info Greg needed to figure out *why*
> you're doing this.
>
--
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy others.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-20 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 12:00 Evalds Iodzevics
2020-04-20 9:31 ` Borislav Petkov
2020-04-20 13:33 ` Ben Hutchings [this message]
2020-04-20 14:01 ` Evalds Iodzevics
2020-04-20 9:57 ` Greg KH
2020-04-21 8:53 ` [PATCH v2] " Evalds Iodzevics
2020-04-21 5:59 ` Greg KH
2020-04-21 6:41 ` Evalds Iodzevics
2020-04-21 7:19 ` Greg KH
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=7fb8e9ac69a1c03a673875dc39fcd8f94407abca.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=bp@alien8.de \
--cc=evalds.iodzevics@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®