From: "Ni, Ray" <ray.ni@intel.com>
To: "Tan, Dun" <dun.tan@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Dong, Eric" <eric.dong@intel.com>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] [PATCH 2/6] UefiCpuPkg: Build MpInfo2HOB in CpuMpPei
Date: Wed, 6 Dec 2023 09:24:12 +0000 [thread overview]
Message-ID: <MN6PR11MB82442A7A6B0BCD1CDA208BDA8C84A@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231205054900.926-3-dun.tan@intel.com>
4 minor comments:
> + DEBUG ((DEBUG_INFO, "BuildMpInformationHob\n"));
1. DEBUG ("Creating MpInformation2 HOB...\n")
> +
> + for (Index = 0; Index < NumberOfProcessorsInHob; Index++) {
> + MpInformation2Entry = GET_MP_INFORMATION_ENTRY
> (MpInformation2HobData, Index);
2. Since EntrySize equals to sizeof (MP_INFORMATION2_ENTRY), is it ok to just use MpInformation2HobData->Entry[Index]?
3. Do you think "Entry[0]" is more proper than "MpInformation[0]"?
> + DEBUG ((
> + DEBUG_INFO,
> + "ProcessorIndex = %x, ProcessorId = %lx, StatusFlag = %x\n",
> + Index + ProcessorIndex,
> + MpInformation2Entry->ProcessorInfo.ProcessorId,
> + MpInformation2Entry->ProcessorInfo.StatusFlag
> + ));
4. How about the debug messages are as follows:
<space><space>Processor[0000]: ProcessorId = 0x00000000, StatusFlag = 0x00000001\n
<space><space><space><space>Location = Package:0 Core:0 Thread:0\n
<space><space><space><space>Location2 = Package:0 Die:0 Tile:0 Module:0 Core:0 Thread:0\n
If a number has "0x" prefix, it uses hex format, otherwise it uses dec format. The debug message should
clearly tell what format the number follows.
Extra 2 spaces in Location/Location2 are to tell that these are extra info for the processor #0.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112102): https://edk2.groups.io/g/devel/message/112102
Mute This Topic: https://groups.io/mt/102987138/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-12-06 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 5:48 [edk2-devel] [PATCH 0/6] Create and consume a new gMpInformationHobGuid2 in UefiCpuPkg duntan
2023-12-05 5:48 ` [edk2-devel] [PATCH 1/6] UefiCpuPkg: Create " duntan
2023-12-06 9:09 ` Ni, Ray
2023-12-07 0:21 ` duntan
2023-12-05 5:48 ` [edk2-devel] [PATCH 2/6] UefiCpuPkg: Build MpInfo2HOB in CpuMpPei duntan
2023-12-06 9:24 ` Ni, Ray [this message]
2023-12-07 0:21 ` duntan
2023-12-05 5:48 ` [edk2-devel] [PATCH 3/6] UefiCpuPkg: Consume MpInfo2Hob in PiSmmCpuDxe duntan
2023-12-06 9:55 ` Ni, Ray
2023-12-07 0:22 ` duntan
2023-12-07 1:26 ` Ni, Ray
2023-12-05 5:48 ` [edk2-devel] [PATCH 4/6] UefiCpuPkg: Add a new field in MpInfo2 HOB duntan
2023-12-06 9:55 ` Ni, Ray
2023-12-05 5:48 ` [edk2-devel] [PATCH 5/6] UefiCpuPkg: Cache core type " duntan
2023-12-06 10:01 ` Ni, Ray
2023-12-07 0:23 ` duntan
2023-12-05 5:49 ` [edk2-devel] [PATCH 6/6] UefiCpuPkg: Avoid assuming only one smmbasehob duntan
2023-12-06 10:14 ` Ni, Ray
2023-12-07 0:37 ` duntan
2023-12-07 1:25 ` Ni, Ray
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=MN6PR11MB82442A7A6B0BCD1CDA208BDA8C84A@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