From: Star Zeng <star.zeng@intel.com>
To: edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>,
Liming Gao <liming.gao@intel.com>, Jeff Fan <jeff.fan@intel.com>
Subject: [PATCH 0/3] Add SecPerformancePpiCallBack to get SEC performance data in SecCore
Date: Mon, 31 Jul 2017 11:31:54 +0800 [thread overview]
Message-ID: <1501471917-11272-1-git-send-email-star.zeng@intel.com> (raw)
Current SEC performance data getting code in FirmwarePerformancePei
may get wrong SEC performance data if FirmwarePerformancePei executes
after memory discovered, it can be removed after SecPerformancePpiCallBack
is added in SecCore.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Jeff Fan <jeff.fan@intel.com>
Star Zeng (3):
UefiCpuPkg SecCore: Adjust PeiTemporaryRamBase&Size to be 8byte
aligned
UefiCpuPkg SecCore: Add SecPerformancePpiCallBack
MdeModulePkg FirmwarePerfPei: Remove SEC performance data getting code
.../FirmwarePerformancePei.c | 39 ++--------------
.../FirmwarePerformancePei.inf | 9 +---
.../FirmwarePerformancePei.uni | 6 +--
UefiCpuPkg/SecCore/SecCore.inf | 7 +++
UefiCpuPkg/SecCore/SecMain.c | 53 +++++++++++++++++++++-
UefiCpuPkg/SecCore/SecMain.h | 25 +++++++++-
6 files changed, 89 insertions(+), 50 deletions(-)
--
2.7.0.windows.1
next reply other threads:[~2017-07-31 3:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 3:31 Star Zeng [this message]
2017-07-31 3:31 ` [PATCH 1/3] UefiCpuPkg SecCore: Adjust PeiTemporaryRamBase&Size to be 8byte aligned Star Zeng
2017-07-31 4:55 ` Fan, Jeff
2017-07-31 3:31 ` [PATCH 2/3] UefiCpuPkg SecCore: Add SecPerformancePpiCallBack Star Zeng
2017-07-31 4:56 ` Fan, Jeff
2017-07-31 3:31 ` [PATCH 3/3] MdeModulePkg FirmwarePerfPei: Remove SEC performance data getting code Star Zeng
2017-08-01 9:01 ` [PATCH 0/3] Add SecPerformancePpiCallBack to get SEC performance data in SecCore Gao, Liming
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=1501471917-11272-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