From: "Laszlo Ersek" <lersek@redhat.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>, "Ni, Ray" <ray.ni@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Zeng, Star" <star.zeng@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Dong, Eric" <eric.dong@intel.com>,
"Brian J . Johnson" <brian.johnson@hpe.com>
Subject: Re: [edk2-devel] [PATCH v2] UefiCpuPkg/MpInitLib DXE: Add PCD to control AP status check interval
Date: Wed, 25 Mar 2020 17:33:29 +0100 [thread overview]
Message-ID: <3a077caf-23e7-9d99-1161-0f96e48d8ce3@redhat.com> (raw)
In-Reply-To: <B80AF82E9BFB8E4FBD8C89DA810C6A093C9C129E@SHSMSX104.ccr.corp.intel.com>
On 03/25/20 02:24, Wu, Hao A wrote:
>> -----Original Message-----
>> From: Ni, Ray
>> Sent: Wednesday, March 25, 2020 8:46 AM
>> To: Kinney, Michael D; Zeng, Star; Wu, Hao A; devel@edk2.groups.io
>> Cc: Dong, Eric; Laszlo Ersek; Brian J . Johnson
>> Subject: RE: [edk2-devel] [PATCH v2] UefiCpuPkg/MpInitLib DXE: Add PCD to
>> control AP status check interval
>>
>> Mike, Hao,
>> I searched all edk2 code using regex pattern "Pcd.*Timeout.*", "Pcd.*Timer.*",
>> "Pcd.*Delay.*"
>> and found below PCDs:
>>
>> gEfiMdePkgTokenSpaceGuid.PcdSpinLockTimeout: in tick unit depending on the
>> TimerLib used
>> gEfiMdePkgTokenSpaceGuid.PcdUsbTransferTimeoutValue: in 1ms unit
>> gPcAtChipsetPkgTokenSpaceGuid.PcdHpetDefaultTimerPeriod: in 100ns unit
>>
>> gEfiMdeModulePkgTokenSpaceGuid.PcdSataSpinUpDelayInSecForRecoveryPat
>> h: in 1s unit
>> gUefiCpuPkgTokenSpaceGuid.PcdCpuInitIpiDelayInMicroSeconds: in 1us unit
>> gUefiCpuPkgTokenSpaceGuid.PcdCpuSmmApSyncTimeout: in 1us unit
>> gEfiSourceLevelDebugPkgTokenSpaceGuid.PcdUsbXhciDebugDetectTimeout: in
>> 1us unit
>>
>> 1 uses timer ticks as unit.
>> 1 uses as unit.
>> 1 uses ms as unit.
>> 3 use us as unit.
>> 1 uses 100ns as unit.
>>
>> UefiCpuPkg uses us consistently as the unit.
>> So how about using us for this PCD as well?
>> And don't forget to name the PCD as
>> "PcdCpuApStatusCheckIntervalInMicroSeconds" so developers who set the PCD
>> can be aware by reading the name.
>
>
> Hello Ray,
>
> Agree with your suggestion.
> I will follow up with this approach and provide a new version of the patch.
Works for me, too.
Thanks!
Laszlo
next prev parent reply other threads:[~2020-03-25 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 6:33 [PATCH v2] UefiCpuPkg/MpInitLib DXE: Add PCD to control AP status check interval Wu, Hao A
2020-03-24 7:01 ` [edk2-devel] " Zeng, Star
2020-03-24 7:11 ` Wu, Hao A
2020-03-24 7:29 ` Zeng, Star
2020-03-24 7:52 ` Ni, Ray
2020-03-24 15:59 ` Michael D Kinney
2020-03-25 0:46 ` Ni, Ray
2020-03-25 1:24 ` Wu, Hao A
2020-03-25 16:33 ` Laszlo Ersek [this message]
2020-03-25 1:37 ` Laszlo Ersek
2020-03-25 1:50 ` Wu, Hao A
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=3a077caf-23e7-9d99-1161-0f96e48d8ce3@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