From: "Wang Fan" <fan.wang@intel.com>
To: "Gao, Liming" <gaoliming@byosoft.com.cn>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>
Cc: "Wang, Fan" <fan.wang@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Jiang, Guomin" <guomin.jiang@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH v5 0/2] Support customized FV Migration Information
Date: Thu, 14 Dec 2023 14:15:18 +0000 [thread overview]
Message-ID: <DM8PR11MB5752222BD40E112015F86667978CA@DM8PR11MB5752.namprd11.prod.outlook.com> (raw)
In-Reply-To: <17A0B71F68A6EB8F.11381@groups.io>
Hi Liming and Kumar
Could you help review this v5 patch:
MdeModulePkg: Support customized FV Migration Information:
https://github.com/fanwang2intel/edk2/commit/83c55a73107bfb13df1d8b522e0ea1d18ef3d86b
SecurityPkg: Support customized FV Migration Information
https://github.com/fanwang2intel/edk2/commit/6f7e955f1d63a875f69ebc084885e76610acc722
v5:
- Remove RemoveFvHobsInTemporaryMemory() since no consumer will call this API now.
- Separate patches to different packages.
Best Regards
Fan
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Wang Fan
Sent: Thursday, December 14, 2023 9:53 PM
To: devel@edk2.groups.io
Cc: Wang, Fan <fan.wang@intel.com>
Subject: [edk2-devel] [PATCH v5 0/2] Support customized FV Migration Information
There are use cases which not all FVs need be migrated from TempRam to permanent memory before TempRam tears down. This new guid is introduced to avoid unnecessary FV migration to improve boot performance. Platform can publish MigrationInfo hob with this guid to customize FV migration info, and PeiCore will only migrate FVs indicated by this Hob info.
This is a backwards compatible change, PeiCore will check MigrationInfo hob before migration. If MigrationInfo hobs exists, only migrate FVs recorded by hobs. If MigrationInfo hobs not exists, migrate all FVs to permanent memory.
In Tcg driver, when MigratedFvInfo hob is detected, existing code logic is assuming FV raw data is already copied, and raw data base address is also recorded. Due to the new PeiCore change, the platform can publish hob to indicate raw data need be copied or not along with FV migration.
Two cases need be considered to skip copy for boot performance: The first case is FV is not expected to be measured in post-mem phase, we should use MeasurementExcludedPpiGuid to skip measurement. The second case is FV raw data has no need to do rebase operation after migration, then measurement should calculate hash directly from FV base address.
Fan Wang (2):
MdeModulePkg: Support customized FV Migration Information
SecurityPkg: Support customized FV Migration Information
MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c | 84 ++++++++++++++----- MdeModulePkg/Core/Pei/Memory/MemoryServices.c | 40 ---------
MdeModulePkg/Core/Pei/PeiMain.h | 11 ---
MdeModulePkg/Core/Pei/PeiMain.inf | 1 +
MdeModulePkg/Include/Guid/MigratedFvInfo.h | 42 +++++++++-
MdeModulePkg/MdeModulePkg.dec | 3 +-
SecurityPkg/Tcg/Tcg2Pei/Tcg2Pei.c | 7 +-
SecurityPkg/Tcg/TcgPei/TcgPei.c | 7 +-
8 files changed, 116 insertions(+), 79 deletions(-)
--
2.29.2.windows.2
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112536): https://edk2.groups.io/g/devel/message/112536
Mute This Topic: https://groups.io/mt/103169821/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next parent reply other threads:[~2023-12-14 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17A0B71F68A6EB8F.11381@groups.io>
2023-12-14 14:15 ` Wang Fan [this message]
2023-12-19 6:27 ` 回复: [edk2-devel] [PATCH v5 0/2] Support customized FV Migration Information gaoliming via groups.io
2023-12-20 8:16 ` Ni, Ray
2023-12-21 7:37 ` Wang Fan
2023-12-14 13:53 Wang Fan
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=DM8PR11MB5752222BD40E112015F86667978CA@DM8PR11MB5752.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