From: "Ni, Ray" <ray.ni@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Sughosh Ganu <sughosh.ganu@arm.com>,
Achin Gupta <achin.gupta@arm.com>,
Achin Gupta <achin.gupta@arm.com>,
Supreeth Venkatesh <supreeth.venkatesh@arm.com>
Cc: "Zimmer, Vincent" <vincent.zimmer@intel.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Chaganty, Rangasai V" <rangasai.v.chaganty@intel.com>,
"Tan, Dun" <dun.tan@intel.com>
Subject: [edk2-devel] Regarding StandaloneMmPkg/Include/Guid/MpInformation.h
Date: Wed, 6 Sep 2023 06:39:42 +0000 [thread overview]
Message-ID: <MN6PR11MB8244C9C91F580BFB1075F18B8CEFA@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
All,
StandaloneMmPkg/Include/Guid/MpInformation.h contains the MP_INFORMATION_HOB_DATA HOB definition.
This HOB is used for transfering MP information collected in non-SMM phase to standalone MM environment.
#pragma pack(1)
typedef struct {
UINT64 NumberOfProcessors;
UINT64 NumberOfEnabledProcessors;
EFI_PROCESSOR_INFORMATION ProcessorInfoBuffer[];
} MP_INFORMATION_HOB_DATA;
#pragma pack()
extern EFI_GUID gMpInformationHobGuid;
Is there any reason that the MP_INFORMATION_HOB_DATA HOB definition not documented in PI spec?
If no reason, I do feel that PI spec needs to carry the HOB definition.
Thoughts?
Thanks,
Ray
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108307): https://edk2.groups.io/g/devel/message/108307
Mute This Topic: https://groups.io/mt/101187873/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 7966 bytes --]
next reply other threads:[~2023-09-06 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 6:39 Ni, Ray [this message]
2023-09-06 16:10 ` [edk2-devel] Regarding StandaloneMmPkg/Include/Guid/MpInformation.h Oliver Smith-Denny
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=MN6PR11MB8244C9C91F580BFB1075F18B8CEFA@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