From: "Dong, Eric" <eric.dong@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Fu, Siyuan" <siyuan.fu@intel.com>
Cc: "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [Patch 1/1] UefiCpuPkg: Always load microcode patch on AP processor.
Date: Tue, 7 Jan 2020 08:05:29 +0000 [thread overview]
Message-ID: <ED077930C258884BBCB450DB737E662259F9B03A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20200103065927.2148-1-siyuan.fu@intel.com>
Hi Siyuan,
Thanks for your patch.
Reviewed-by: Eric Dong <eric.dong@intel.com>
Thanks,
Eric
> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Siyuan, Fu
> Sent: Friday, January 3, 2020 2:59 PM
> To: devel@edk2.groups.io
> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>
> Subject: [edk2-devel] [Patch 1/1] UefiCpuPkg: Always load microcode patch
> on AP processor.
>
> This patch updates the microcode loader to always perform a microcode
> detect and load on both BSP and AP processor. This is to fix a potential
> microcode revision mismatch issue in below situation:
> 1. Assume there are two microcode co-exists in flash: one production version
> and one debug version microcode.
> 2. FIT loads production microcode to BSP and all AP.
> 3. UefiCpuPkg loader loads debug microcode to BSP, and skip the loading on
> AP.
> As a result, different microcode patches are loaded to BSP and AP, and
> trigger microcode mismatch error during OS boot.
>
> Bugzilla: https://bugzilla.tianocore.org/show_bug.cgi?id=2431
>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Signed-off-by: Siyuan Fu <siyuan.fu@intel.com>
> ---
> UefiCpuPkg/Library/MpInitLib/Microcode.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/UefiCpuPkg/Library/MpInitLib/Microcode.c
> b/UefiCpuPkg/Library/MpInitLib/Microcode.c
> index 3da5bfb9cf2f..fa6f9681e55a 100644
> --- a/UefiCpuPkg/Library/MpInitLib/Microcode.c
> +++ b/UefiCpuPkg/Library/MpInitLib/Microcode.c
> @@ -1,7 +1,7 @@
> /** @file
> Implementation of loading microcode on processors.
>
> - Copyright (c) 2015 - 2019, Intel Corporation. All rights reserved.<BR>
> + Copyright (c) 2015 - 2020, Intel Corporation. All rights
> + reserved.<BR>
> SPDX-License-Identifier: BSD-2-Clause-Patent
>
> **/
> @@ -105,12 +105,6 @@ MicrocodeDetect (
>
> CurrentRevision = GetCurrentMicrocodeSignature ();
> IsBspCallIn = (ProcessorNumber == (UINTN)CpuMpData->BspNumber) ?
> TRUE : FALSE;
> - if (CurrentRevision != 0 && !IsBspCallIn) {
> - //
> - // Skip loading microcode if it has been loaded successfully
> - //
> - return;
> - }
>
> GetProcessorLocationByApicId (GetInitialApicId (), NULL, NULL, &ThreadId);
> if (ThreadId != 0) {
> --
> 2.19.1.windows.1
>
>
>
prev parent reply other threads:[~2020-01-07 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 6:59 [Patch 1/1] UefiCpuPkg: Always load microcode patch on AP processor Siyuan, Fu
2020-01-07 8:05 ` Dong, Eric [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-list 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=ED077930C258884BBCB450DB737E662259F9B03A@shsmsx102.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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