From: Laszlo Ersek <lersek@redhat.com>
To: "Chasel, Chiu" <chasel.chiu@intel.com>, edk2-devel@lists.01.org
Cc: Eric Dong <eric.dong@intel.com>, Ray Ni <ray.ni@intel.com>
Subject: Re: [PATCH 3/3] UefiCpuPkg/SecCore: Support EFI_PEI_CORE_FV_LOCATION_PPI
Date: Tue, 12 Feb 2019 14:57:13 +0100 [thread overview]
Message-ID: <dfbb43c3-970a-6c40-86d9-e8e2e8e89f7c@redhat.com> (raw)
In-Reply-To: <20190212131957.2576-4-chasel.chiu@intel.com>
On 02/12/19 14:19, Chasel, Chiu wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1524
>
> EFI_PEI_CORE_FV_LOCATION_PPI may be passed by platform
> when PeiCore not in BFV so SecCore has to search PeiCore
> either from the FV location provided by
> EFI_PEI_CORE_FV_LOCATION_PPI or from BFV.
>
> Test: Verified on internal platform and booting successfully.
>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
> ---
> UefiCpuPkg/SecCore/SecMain.c | 35 +++++++++++++++++++++++++++++------
> UefiCpuPkg/SecCore/SecCore.inf | 3 ++-
> UefiCpuPkg/SecCore/SecMain.h | 3 ++-
> 3 files changed, 33 insertions(+), 8 deletions(-)
Thank you for the CC. OVMF doesn't consume this module, so I'll pass on
this review.
Thanks,
Laszlo
prev parent reply other threads:[~2019-02-12 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 13:19 [PATCH 0/3] Support EFI_PEI_CORE_FV_LOCATION_PPI Chasel, Chiu
2019-02-12 13:19 ` [PATCH 1/3] MdePkg: " Chasel, Chiu
2019-02-13 9:20 ` Zeng, Star
2019-02-14 8:06 ` Ni, Ray
2019-02-12 13:19 ` [PATCH 2/3] MdeModulePkg/PeiMain: " Chasel, Chiu
2019-02-13 1:14 ` Wang, Jian J
2019-02-13 3:58 ` Chiu, Chasel
2019-02-13 9:33 ` Zeng, Star
2019-02-14 8:13 ` Ni, Ray
2019-02-14 8:20 ` Ni, Ray
2019-02-14 10:32 ` Chiu, Chasel
2019-02-12 13:19 ` [PATCH 3/3] UefiCpuPkg/SecCore: " Chasel, Chiu
2019-02-12 13:57 ` Laszlo Ersek [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=dfbb43c3-970a-6c40-86d9-e8e2e8e89f7c@redhat.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