public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Ni, Ray" <ray.ni@intel.com>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [PATCH V3 0/8] Enable SMM perf-logging
Date: Thu, 15 Jun 2023 10:03:35 +0000	[thread overview]
Message-ID: <MN6PR11MB82442D75FA566C5564BAA74E8C5BA@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1768233E81BDED74.16517@groups.io>

I haven't got "Reviewed-by" for MdeModulePkg changes. Can Jian or Liming approve?

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ni, Ray
> Sent: Tuesday, June 13, 2023 2:13 PM
> To: devel@edk2.groups.io
> Subject: [edk2-devel] [PATCH V3 0/8] Enable SMM perf-logging
> 
> To avoid impacting runtime performance, the perf-logging is
> disabled upon ExitBootServices.
> 
> Ray Ni (8):
>   UefiCpuPkg/CpuSmm: Add perf-logging for time-consuming BSP procedures
>   UefiCpuPkg/CpuSmm: Add perf-logging for MP procedures
>   MdeModulePkg/SmmCore: Add perf-logging for time-consuming procedures
>   MdeModulePkg/SmmCore: Add perf-logging for SmmDriverDispatchHandler
>   MdeModulePkg/SmmPerformanceLib: Disable perf-logging after ExitBS
>   MdeModulePkg/SmmCorePerformanceLib: Disable perf-logging at runtime
>   UefiCpuPkg/SmmCpu: Add PcdSmmApPerfLogEnable control AP perf-logging
>   MdeModulePkg/SmmCore: Perf-log PlatformHookBefore/AfterSmmDispatch
> 
>  MdeModulePkg/Core/PiSmmCore/Dispatcher.c      |   5 +-
>  MdeModulePkg/Core/PiSmmCore/PiSmmCore.c       |  19 +++-
>  MdeModulePkg/Core/PiSmmCore/Smi.c             |   6 ++
>  .../SmmCorePerformanceLib.c                   |  48 ++++++++-
>  .../SmmCorePerformanceLib.inf                 |   3 +-
>  .../SmmPerformanceLib/SmmPerformanceLib.c     |  63 ++++++++++-
>  .../SmmPerformanceLib/SmmPerformanceLib.inf   |   4 +
>  UefiCpuPkg/PiSmmCpuDxeSmm/MpService.c         |  42 +++++++-
>  UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.c    |  38 +++++++
>  UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h    |   2 +
>  UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf  |   4 +
>  .../PiSmmCpuDxeSmm/SmmCpuMemoryManagement.c   |  13 ++-
>  UefiCpuPkg/PiSmmCpuDxeSmm/SmmMpPerf.c         | 100
> ++++++++++++++++++
>  UefiCpuPkg/PiSmmCpuDxeSmm/SmmMpPerf.h         |  83
> +++++++++++++++
>  UefiCpuPkg/PiSmmCpuDxeSmm/SmmProfile.c        |   4 +-
>  UefiCpuPkg/UefiCpuPkg.dec                     |   6 ++
>  16 files changed, 429 insertions(+), 11 deletions(-)
>  create mode 100644 UefiCpuPkg/PiSmmCpuDxeSmm/SmmMpPerf.c
>  create mode 100644 UefiCpuPkg/PiSmmCpuDxeSmm/SmmMpPerf.h
> 
> --
> 2.39.1.windows.1
> 
> 
> 
> 
> 


           reply	other threads:[~2023-06-15 10:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1768233E81BDED74.16517@groups.io>]

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=MN6PR11MB82442D75FA566C5564BAA74E8C5BA@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