From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 0/5] refine Smm range code in BoardX58Ich10
Date: Wed, 26 Apr 2023 09:19:55 +0000 [thread overview]
Message-ID: <MN6PR11MB82443BC6BCFB742576CBE0478C659@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230426061549.1254-1-zhiguang.liu@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Zhiguang
> Liu
> Sent: Wednesday, April 26, 2023 2:16 PM
> To: devel@edk2.groups.io
> Cc: Liu, Zhiguang <zhiguang.liu@intel.com>
> Subject: [edk2-devel] [PATCH v2 0/5] refine Smm range code in
> BoardX58Ich10
>
> In BoardX58Ich10 platform, two modules has hard-code about how SMM
> range should be, and this causes a issue since PEI phase may change
> SMM ranges now. This patch set refine Smm range related code.
> v2
> refine comments and commit message
>
> Zhiguang Liu (5):
> SimicsOpenBoardPkg: Build gEfiSmmSmramMemoryGuid Hob in S3 path
> SimicsOpenBoardPkg: Move AcpiVariableGuid hob to MemDetect
> SimicsOpenBoardPkg: Use SmmAccessLib instead of SmmAccessPei.inf
> SimicsOpenBoardPkg: Use another SmmAccess Driver
> SimicsX58SktPkg: Remove unused Smm related modules
>
> .../BoardX58Ich10/OpenBoardPkg.dsc | 11 +-
> .../BoardX58Ich10/OpenBoardPkg.fdf | 3 +-
> .../SimicsOpenBoardPkg/SimicsPei/MemDetect.c | 136 +++----
> .../SimicsPei/SimicsPei.inf | 5 +-
> .../SimicsX58SktPkg/SktUefiBootInclude.fdf | 4 +-
> .../Smm/Access/SmmAccess2Dxe.c | 148 --------
> .../Smm/Access/SmmAccess2Dxe.inf | 54 ---
> .../SimicsX58SktPkg/Smm/Access/SmmAccessPei.c | 346 ------------------
> .../Smm/Access/SmmAccessPei.inf | 65 ----
> .../Smm/Access/SmramInternal.c | 200 ----------
> .../Smm/Access/SmramInternal.h | 82 -----
> 11 files changed, 79 insertions(+), 975 deletions(-)
> delete mode 100644
> Silicon/Intel/SimicsX58SktPkg/Smm/Access/SmmAccess2Dxe.c
> delete mode 100644
> Silicon/Intel/SimicsX58SktPkg/Smm/Access/SmmAccess2Dxe.inf
> delete mode 100644
> Silicon/Intel/SimicsX58SktPkg/Smm/Access/SmmAccessPei.c
> delete mode 100644
> Silicon/Intel/SimicsX58SktPkg/Smm/Access/SmmAccessPei.inf
> delete mode 100644
> Silicon/Intel/SimicsX58SktPkg/Smm/Access/SmramInternal.c
> delete mode 100644
> Silicon/Intel/SimicsX58SktPkg/Smm/Access/SmramInternal.h
>
> --
> 2.31.1.windows.1
>
>
>
>
>
prev parent reply other threads:[~2023-04-26 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 6:15 [PATCH v2 0/5] refine Smm range code in BoardX58Ich10 Zhiguang Liu
2023-04-26 6:15 ` [PATCH v2 1/5] SimicsOpenBoardPkg: Build gEfiSmmSmramMemoryGuid Hob in S3 path Zhiguang Liu
2023-04-26 6:15 ` [PATCH v2 2/5] SimicsOpenBoardPkg: Move AcpiVariableGuid hob to MemDetect Zhiguang Liu
2023-04-26 6:15 ` [PATCH v2 3/5] SimicsOpenBoardPkg: Use SmmAccessLib instead of SmmAccessPei.inf Zhiguang Liu
2023-04-26 6:15 ` [PATCH v2 4/5] SimicsOpenBoardPkg: Use another SmmAccess Driver Zhiguang Liu
2023-04-26 6:15 ` [PATCH v2 5/5] SimicsX58SktPkg: Remove unused Smm related modules Zhiguang Liu
2023-04-26 9:19 ` Ni, Ray [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=MN6PR11MB82443BC6BCFB742576CBE0478C659@MN6PR11MB8244.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