From: "Laszlo Ersek" <lersek@redhat.com>
To: "Duran, Leo" <leo.duran@amd.com>, "Ni, Ray" <ray.ni@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Wu, Hao A" <hao.a.wu@intel.com>,
"Fu, Siyuan" <siyuan.fu@intel.com>
Cc: "Dong, Eric" <eric.dong@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/2] UefiCpuPkg/Library: Fix bug in MpInitLib
Date: Wed, 26 Feb 2020 18:45:21 +0100 [thread overview]
Message-ID: <f83afc79-ac6c-eba2-e155-8016bdded95e@redhat.com> (raw)
In-Reply-To: <BN6PR12MB1922DD0F0368539C86FEAED0F9EA0@BN6PR12MB1922.namprd12.prod.outlook.com>
On 02/26/20 17:39, Duran, Leo wrote:
>
>
>> -----Original Message-----
>> From: Laszlo Ersek [mailto:lersek@redhat.com]
>> Sent: Wednesday, February 26, 2020 11:21 AM
>> To: Duran, Leo <leo.duran@amd.com>; Ni, Ray <ray.ni@intel.com>;
>> devel@edk2.groups.io; Wu, Hao A <hao.a.wu@intel.com>; Fu, Siyuan
>> <siyuan.fu@intel.com>
>> Cc: Dong, Eric <eric.dong@intel.com>
>> Subject: Re: [edk2-devel] [PATCH 0/2] UefiCpuPkg/Library: Fix bug in
>> MpInitLib
>>
>> On 02/26/20 16:46, Duran, Leo wrote:
>>> BTW,
>>>
>>> I also considered adding a flag to CPU_MP_DATA to make the usage of
>> PlatformId a bit more explicit.
>>> E.g., something like CpuMpData-
>>> CpuData[ProcessorNumber].IsValidPlatformId... So the init code would look
>> like this:
>>>
>>> //
>>> // NOTE: PlatformId is not relevant on AMD platforms.
>>> //
>>> if (StandardSignatureIsAuthenticAMD ()) {
>>> CpuMpData->CpuData[ProcessorNumber].IsValidPlatformId = FALSE;
>>> else {
>>> PlatformIdMsr.Uint64 = AsmReadMsr64 (MSR_IA32_PLATFORM_ID);
>>> CpuMpData->CpuData[ProcessorNumber].PlatformId =
>> (UINT8)PlatformIdMsr.Bits.PlatformId;
>>> CpuMpData->CpuData[ProcessorNumber].IsValidPlatformId = TRUE;
>>> }
>>>
>>> This way "IsValidPlatformId" could be checked prior to using "PlatformId".
>>> Anyway, that seemed a bit overkill, so I opted against it... thoughts?
>>
>> I think a global flag is justified; in the above approach, "IsValidPlatformId"
>> would not vary across "ProcessorNumber", so it does look like useless
>> generality.
> [Duran, Leo]
> Great point, Laszlo.
> Indeed, global makes senses in the case!
> I can prepare a v2-set to incorporate that.
No, sorry, that wasn't what I meant. I didn't try to suggest a global
variable. Instead, I meant that a "global check" (conceptually, i.e.
regardless of particular processor number) made sense.
I'm also not particularly *against* a global variable. In other words, I
didn't try to comment on using a global variable *at all*.
Using a global variable might as well work, I just feel that your
current patches are good enough.
Thanks
Laszlo
next prev parent reply other threads:[~2020-02-26 17:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 19:39 [PATCH 0/2] UefiCpuPkg/Library: Fix bug in MpInitLib Leo Duran
2020-02-25 19:39 ` [PATCH 1/2] UefiCpuPkg: LocalApicLib: Export StandardSignatureIsAuthenticAMD function Leo Duran
2020-02-26 1:13 ` Dong, Eric
2020-02-26 2:41 ` Duran, Leo
2020-02-26 5:05 ` Dong, Eric
2020-02-26 10:13 ` [edk2-devel] " Laszlo Ersek
2020-02-26 15:03 ` Duran, Leo
2020-02-26 16:19 ` Laszlo Ersek
2020-02-26 15:59 ` Duran, Leo
2020-02-25 19:39 ` [PATCH 2/2] UefiCpuPkg: MpInitLib: Exclude code no pertinent to AMD processors Leo Duran
2020-02-26 7:45 ` Ni, Ray
2020-02-26 7:56 ` Siyuan, Fu
2020-02-26 0:54 ` [edk2-devel] [PATCH 0/2] UefiCpuPkg/Library: Fix bug in MpInitLib Laszlo Ersek
2020-02-26 7:57 ` Ni, Ray
2020-02-26 8:56 ` Liming Gao
2020-02-26 15:11 ` Duran, Leo
2020-02-26 16:24 ` Laszlo Ersek
2020-02-26 16:35 ` Duran, Leo
2020-02-26 15:25 ` Duran, Leo
2020-02-26 15:46 ` Duran, Leo
2020-02-26 16:20 ` Laszlo Ersek
2020-02-26 16:39 ` Duran, Leo
2020-02-26 16:46 ` Duran, Leo
2020-02-26 17:45 ` Laszlo Ersek [this message]
2020-02-26 17:51 ` Duran, Leo
2020-02-27 5:55 ` Ni, Ray
2020-02-27 18:17 ` Duran, Leo
2020-02-28 6:47 ` Ni, Ray
2020-02-28 16:38 ` Duran, Leo
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=f83afc79-ac6c-eba2-e155-8016bdded95e@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