From: "Laszlo Ersek" <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Mike Turner <miketur@microsoft.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
"Bi, Dandan" <dandan.bi@intel.com>
Subject: Re: [edk2-devel] [Patch] MdeModulePkg DxeCore: Fix for missing MAT update
Date: Fri, 16 Aug 2019 17:18:27 +0200 [thread overview]
Message-ID: <684cdd50-88d7-500e-ca56-c59f11e0e615@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4D101F@SHSMSX104.ccr.corp.intel.com>
On 08/14/19 17:55, Gao, Liming wrote:
> If Platform PEIM doesn't build HOB, DxeIpl will not build HOB,
My reading of the code is the opposite. If the platform PEIM does not build the HOB, then the DXE IPL PEIM will attempt to build the HOB, from the UEFI variable.
At commit caa7d3a896f6, in file "MdeModulePkg/Core/DxeIplPeim/DxeLoad.c", function DxeLoadCore(), we have:
363 if (GetFirstGuidHob ((CONST EFI_GUID *)&gEfiMemoryTypeInformationGuid) == NULL) {
364 //
365 // Don't build GuidHob if GuidHob has been installed.
366 //
367 Status = PeiServicesLocatePpi (
368 &gEfiPeiReadOnlyVariable2PpiGuid,
369 0,
370 NULL,
371 (VOID **)&Variable
372 );
373 if (!EFI_ERROR (Status)) {
374 DataSize = sizeof (MemoryData);
375 Status = Variable->GetVariable (
376 Variable,
377 EFI_MEMORY_TYPE_INFORMATION_VARIABLE_NAME,
378 &gEfiMemoryTypeInformationGuid,
379 NULL,
380 &DataSize,
381 &MemoryData
382 );
383 if (!EFI_ERROR (Status) && ValidateMemoryTypeInfoVariable(MemoryData, DataSize)) {
384 //
385 // Build the GUID'd HOB for DXE
386 //
387 BuildGuidDataHob (
388 &gEfiMemoryTypeInformationGuid,
389 MemoryData,
390 DataSize
391 );
392 }
393 }
394 }
Thanks
Laszlo
next prev parent reply other threads:[~2019-08-16 15:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 14:10 [Patch] MdeModulePkg DxeCore: Fix for missing MAT update Liming Gao
2019-08-12 5:10 ` [edk2-devel] " Wang, Jian J
2019-08-12 16:24 ` Laszlo Ersek
2019-08-12 23:22 ` Michael D Kinney
2019-08-13 9:47 ` Laszlo Ersek
2019-08-14 14:00 ` Liming Gao
2019-08-14 15:12 ` Laszlo Ersek
2019-08-14 15:55 ` Liming Gao
2019-08-16 15:18 ` Laszlo Ersek [this message]
2019-08-16 15:24 ` Liming Gao
2019-08-16 18:54 ` Laszlo Ersek
2019-08-19 0:40 ` Liming Gao
2019-08-21 8:46 ` Laszlo Ersek
2019-08-21 14:14 ` Liming Gao
2019-08-22 11:56 ` Laszlo Ersek
2019-08-22 14:52 ` Liming Gao
2019-08-23 12:40 ` Laszlo Ersek
[not found] <15B9950E072DB087.17773@groups.io>
2019-08-10 14:16 ` Liming Gao
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=684cdd50-88d7-500e-ca56-c59f11e0e615@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