From: Star Zeng <star.zeng@intel.com>
To: edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>
Subject: [PATCH V2 0/7] Remove PcdPeiCoreMaxXXX PCDs
Date: Tue, 18 Dec 2018 14:07:59 +0800 [thread overview]
Message-ID: <1545113286-49760-1-git-send-email-star.zeng@intel.com> (raw)
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1405
V2:
1. Pick up some RB tags.
2. Handle the great comment from Jian for patch 1/7 at
https://lists.01.org/pipermail/edk2-devel/2018-December/034121.html.
Repo: git@github.com:lzeng14/edk2.git
Branch: RemovePcdPeiCoreMaxXXX_V2
Test done:
Make sure the Private->CurrentFvFileHandles content could be same.
V1:
Repo: git@github.com:lzeng14/edk2.git
Branch: RemovePcdPeiCoreMaxXXX
Background as below.
Problem:
As static configuration from the PCDs, the binary PeiCore (for example
in FSP binary with dispatch mode) could not predict how many FVs,
Files or PPIs for different platforms.
Burden:
Platform developers need configure the PCDs accordingly for different
platforms.
To solve the problem and remove the burden, we can update code to
remove the using of PcdPeiCoreMaxFvSupported, PcdPeiCoreMaxPeimPerFv
and PcdPeiCoreMaxPpiSupported by extending buffer dynamically for FV,
File and PPI management.
Test done:
Build code with VS2012, VS2015 and GCC49.
Boot Nt32, Ovmf (including 32, 3264 and 64 with no SMM) to UEFI SHELL.
Boot some internal platforms (including a platform with dispatch mode
FSP binary) to UEFI SHELL and Windows.
More test will be welcome and appreciated. :)
Patches to update edk2-platforms Repo will be sent out separately.
Star Zeng (7):
MdeModulePkg PeiCore: Remove the using of PcdPeiCoreMaxPeimPerFv
SecurityPkg Tcg(2)Pei: Remove the using of PcdPeiCoreMaxFvSupported
MdeModulePkg PeiCore: Remove the using of PcdPeiCoreMaxFvSupported
MdeModulePkg PeiCore: Remove the using of PcdPeiCoreMaxPpiSupported
OvmfPkg: Remove PcdPeiCoreMaxXXX PCDs' statement
Vlv2TbltDevicePkg: Remove PcdPeiCoreMaxXXX PCDs' statement
MdeModulePkg: Remove PcdPeiCoreMaxXXX PCDs
MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c | 181 +++++++------
MdeModulePkg/Core/Pei/FwVol/FwVol.c | 67 ++++-
MdeModulePkg/Core/Pei/PeiMain.h | 96 +++++--
MdeModulePkg/Core/Pei/PeiMain.inf | 3 -
MdeModulePkg/Core/Pei/PeiMain/PeiMain.c | 94 +++----
MdeModulePkg/Core/Pei/Ppi/Ppi.c | 355 ++++++++++++++------------
MdeModulePkg/MdeModulePkg.dec | 13 -
MdeModulePkg/MdeModulePkg.uni | 12 -
OvmfPkg/OvmfPkgIa32.dsc | 2 -
OvmfPkg/OvmfPkgIa32X64.dsc | 2 -
OvmfPkg/OvmfPkgX64.dsc | 2 -
SecurityPkg/Tcg/Tcg2Pei/Tcg2Pei.c | 59 +++--
SecurityPkg/Tcg/Tcg2Pei/Tcg2Pei.inf | 1 -
SecurityPkg/Tcg/TcgPei/TcgPei.c | 59 +++--
SecurityPkg/Tcg/TcgPei/TcgPei.inf | 1 -
Vlv2TbltDevicePkg/PlatformPkgGccX64.dsc | 2 -
Vlv2TbltDevicePkg/PlatformPkgIA32.dsc | 2 -
Vlv2TbltDevicePkg/PlatformPkgX64.dsc | 2 -
18 files changed, 539 insertions(+), 414 deletions(-)
--
2.7.0.windows.1
next reply other threads:[~2018-12-18 6:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 6:07 Star Zeng [this message]
2018-12-18 6:08 ` [PATCH V2 1/7] MdeModulePkg PeiCore: Remove the using of PcdPeiCoreMaxPeimPerFv Star Zeng
2018-12-19 3:21 ` Chiu, Chasel
2018-12-18 6:08 ` [PATCH V2 2/7] SecurityPkg Tcg(2)Pei: Remove the using of PcdPeiCoreMaxFvSupported Star Zeng
2018-12-18 6:08 ` [PATCH V2 3/7] MdeModulePkg PeiCore: " Star Zeng
2018-12-19 3:22 ` Chiu, Chasel
2018-12-18 6:08 ` [PATCH V2 4/7] MdeModulePkg PeiCore: Remove the using of PcdPeiCoreMaxPpiSupported Star Zeng
2018-12-19 3:22 ` Chiu, Chasel
2018-12-18 6:08 ` [PATCH V2 5/7] OvmfPkg: Remove PcdPeiCoreMaxXXX PCDs' statement Star Zeng
2018-12-18 6:08 ` [PATCH V2 6/7] Vlv2TbltDevicePkg: " Star Zeng
2018-12-18 6:08 ` [PATCH V2 7/7] MdeModulePkg: Remove PcdPeiCoreMaxXXX PCDs Star Zeng
2018-12-19 3:21 ` Chiu, Chasel
2018-12-18 7:21 ` [PATCH V2 0/7] " Wang, Jian J
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=1545113286-49760-1-git-send-email-star.zeng@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