From: "Gao, Liming" <liming.gao@intel.com>
To: "Bi, Dandan" <dandan.bi@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Dmitry Antipov <dmanti@microsoft.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: [patch 0/2] Enahnce Perf data transfer between Dxe Perf Lib and driver
Date: Fri, 3 Aug 2018 09:39:50 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E2C555D@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20180730070016.10396-1-dandan.bi@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
>-----Original Message-----
>From: Bi, Dandan
>Sent: Monday, July 30, 2018 3:00 PM
>To: edk2-devel@lists.01.org
>Cc: Dmitry Antipov <dmanti@microsoft.com>; Kinney, Michael D
><michael.d.kinney@intel.com>; Gao, Liming <liming.gao@intel.com>; Zeng,
>Star <star.zeng@intel.com>
>Subject: [patch 0/2] Enahnce Perf data transfer between Dxe Perf Lib and
>driver
>
>Add an internal protocol Firmware Boot Performance Table protocol to
>get the performance data from DxeCorePerformanceLib.
>Thus the FirmwarePerformanceDxe driver can call the API in the
>new protocl to get the performance data instead of through
>hook status code.
>
>Cc: Dmitry Antipov <dmanti@microsoft.com>
>Cc: Michael D Kinney <michael.d.kinney@intel.com>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Star Zeng <star.zeng@intel.com>
>Dandan Bi (2):
> MdeModulePkg: Add definition of Boot Performance Table protocol
> MdeModulePkg: Implement/use Boot Performance Table protocol
>
> .../Include/Guid/FirmwareBootPerformanceTable.h | 47 ++++++++++++++
> .../DxeCorePerformanceLib/DxeCorePerformanceLib.c | 74 ++++++-----------
>-----
> .../DxeCorePerformanceLib.inf | 6 +-
> .../DxeCorePerformanceLibInternal.h | 15 +++++
> MdeModulePkg/MdeModulePkg.dec | 4 ++
> .../FirmwarePerformanceDxe.c | 71 ++++++++++++++++-----
> .../FirmwarePerformanceDxe.inf | 5 +-
> 7 files changed, 144 insertions(+), 78 deletions(-)
> create mode 100644
>MdeModulePkg/Include/Guid/FirmwareBootPerformanceTable.h
>
>--
>2.14.3.windows.1
prev parent reply other threads:[~2018-08-03 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 7:00 [patch 0/2] Enahnce Perf data transfer between Dxe Perf Lib and driver Dandan Bi
2018-07-30 7:00 ` [patch 1/2] MdeModulePkg: Add definition of Boot Performance Table protocol Dandan Bi
2018-07-30 7:00 ` [patch 2/2] MdeModulePkg: Implement/use " Dandan Bi
2018-08-03 9:39 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E2C555D@SHSMSX104.ccr.corp.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