From: "Ni, Ray" <ray.ni@intel.com>
To: "Yang, Longlong" <longlong.yang@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Dong, Eric" <eric.dong@intel.com>,
"Kumar, Rahul1" <rahul1.kumar@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Xu, Min M" <min.m.xu@intel.com>,
"Zhang, Qi1" <qi1.zhang@intel.com>
Subject: Re: [PATCH V3 1/1] UefiCpuPkg: Extend measurement of microcode patches to TPM
Date: Tue, 14 Dec 2021 01:56:51 +0000 [thread overview]
Message-ID: <BN0PR11MB569675CE35FB32CD992DFE8B8C759@BN0PR11MB5696.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f99c32de46b20b4c485efdbbfb9a05624213eca8.1639394322.git.longlong.yang@intel.com>
> +
> + //
> + // The order matters when packing all applied microcode patches to a single binary blob.
> + // Therefore it is a must to do sorting before packing.
> + // NOTE: We assumed that the order of address of every microcode patch in RAM is the same
> + // with the order of those in the Microcode Firmware Volume in FLASH. If any future updates
> + // made this assumption untenable, then needs a new solution to measure microcode patches.
> + //
Can you explain the above comments?
If you only measure the microcode which will be applied to CPU, why do you care about the order?
next prev parent reply other threads:[~2021-12-14 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1639394321.git.longlong.yang@intel.com>
2021-12-13 11:19 ` [PATCH V3 1/1] UefiCpuPkg: Extend measurement of microcode patches to TPM longlong.yang
2021-12-14 1:56 ` Ni, Ray [this message]
2021-12-14 3:02 ` Longlong Yang
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=BN0PR11MB569675CE35FB32CD992DFE8B8C759@BN0PR11MB5696.namprd11.prod.outlook.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