public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "Fu, Siyuan" <siyuan.fu@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Dong, Eric" <eric.dong@intel.com>, "Ni, Ray" <ray.ni@intel.com>,
	"lersek@redhat.com" <lersek@redhat.com>
Subject: Re: [Patch 0/2] Shadow microcode patch according to FIT microcode table.
Date: Thu, 9 Jan 2020 02:04:22 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E58EC3F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20200108042525.408-1-siyuan.fu@intel.com>

Siyuan:
  This is new feature, please add it into https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

  And, FIT header file is moved from edk2-platform to edk2. After this change, you also need to remove the one in edk2-platform. Right?

Thanks
Liming
-----Original Message-----
From: Fu, Siyuan <siyuan.fu@intel.com> 
Sent: 2020年1月8日 12:25
To: devel@edk2.groups.io
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming <liming.gao@intel.com>; Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; lersek@redhat.com
Subject: [Patch 0/2] Shadow microcode patch according to FIT microcode table.

The existing MpInitLib will shadow the microcode update patches from flash to memory and this is done by searching microcode region specified by PCD PcdCpuMicrocodePatchAddress and PcdCpuMicrocodePatchRegionSize.
This brings a limition to platform FW that all the microcode patches must be placed in one continuous flash space.

This patch set shadows microcode update according to FIT microcode entries if it's present, otherwise it will fallback to original logic (by PCD).

Patch 1/2: Add FIT header file to MdePkg.
Patch 2/2: Update microcode loader to shadow microcode according to FIT.

Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>

Siyuan Fu (2):
  MdePkg: Add header file for Firmware Interface Table specification.
  UefiCpuPkg: Shadow microcode patch according to FIT microcode entry.

 .../IndustryStandard/FirmwareInterfaceTable.h |  76 ++++++
 UefiCpuPkg/Library/MpInitLib/Microcode.c      | 255 +++++++++++++-----
 UefiCpuPkg/Library/MpInitLib/MpLib.c          |   4 +-
 UefiCpuPkg/Library/MpInitLib/MpLib.h          |   7 +-
 4 files changed, 276 insertions(+), 66 deletions(-)  create mode 100644 MdePkg/Include/IndustryStandard/FirmwareInterfaceTable.h

--
2.19.1.windows.1


  parent reply	other threads:[~2020-01-09  2:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  4:25 [Patch 0/2] Shadow microcode patch according to FIT microcode table Siyuan, Fu
2020-01-08  4:25 ` [Patch 1/2] MdePkg: Add header file for Firmware Interface Table specification Siyuan, Fu
2020-01-08  4:25 ` [Patch 2/2] UefiCpuPkg: Shadow microcode patch according to FIT microcode entry Siyuan, Fu
2020-01-08  9:42 ` [Patch 0/2] Shadow microcode patch according to FIT microcode table Laszlo Ersek
2020-01-08 10:36   ` [edk2-devel] " Laszlo Ersek
2020-01-08 10:58   ` Siyuan, Fu
2020-01-08 12:18     ` Laszlo Ersek
2020-01-09  2:04 ` Liming Gao [this message]
2020-01-09  2:12   ` Siyuan, Fu

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E58EC3F@SHSMSX104.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