From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Tan, Dun" <dun.tan@intel.com>
Subject: Re: [edk2-devel] [Patch V3 0/2] Update ProcTrace feature code for new requirements.
Date: Wed, 26 Apr 2023 02:02:45 +0000 [thread overview]
Message-ID: <MN6PR11MB82442123688A3A1E08B7DDA18C659@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230426015429.3117-1-dun.tan@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of duntan
> Sent: Wednesday, April 26, 2023 9:54 AM
> To: devel@edk2.groups.io
> Subject: [edk2-devel] [Patch V3 0/2] Update ProcTrace feature code for new
> requirements.
>
> In V3 patch set:
> 1. Add more comments in 'Update code to support enable ProcTrace only on
> BSP'
> 2. Rename some local varibles and remove a uneeded if check in 'Update PT
> code to support enable collect performance'
>
> Dun Tan (2):
> UefiCpuPkg: Update code to support enable ProcTrace only on BSP
> UefiCpuPkg: Update PT code to support enable collect performance
>
> UefiCpuPkg/Library/CpuCommonFeaturesLib/CpuCommonFeaturesLib.inf |
> 12 +++++++-----
> UefiCpuPkg/Library/CpuCommonFeaturesLib/ProcTrace.c | 210
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> +++++++++++++++++++++++---------------------------------------------------------
> --------------
> UefiCpuPkg/UefiCpuPkg.dec | 15 +++++++++++++++
> 3 files changed, 161 insertions(+), 76 deletions(-)
>
> --
> 2.39.1.windows.1
>
>
>
>
>
prev parent reply other threads:[~2023-04-26 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 1:54 [Patch V3 0/2] Update ProcTrace feature code for new requirements duntan
2023-04-26 1:54 ` [Patch V3 1/2] UefiCpuPkg: Update code to support enable ProcTrace only on BSP duntan
2023-04-26 1:54 ` [Patch V3 2/2] UefiCpuPkg: Update PT code to support enable collect performance duntan
2023-04-26 2:02 ` 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=MN6PR11MB82442123688A3A1E08B7DDA18C659@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