From: "Guo Dong" <guo.dong@intel.com>
To: "Ni, Ray" <ray.ni@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Ma, Maurice" <maurice.ma@intel.com>,
"You, Benjamin" <benjamin.you@intel.com>
Subject: Re: [`edk2-devel][PATCH] UefiPayloadPkg: Build a HOB from bootloader ACPI table
Date: Tue, 28 Sep 2021 17:19:42 +0000 [thread overview]
Message-ID: <DM6PR11MB362711836E8B99D0CA842ABB9EA89@DM6PR11MB3627.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CY4PR1101MB2072EB6ACE9531525F5648818CA89@CY4PR1101MB2072.namprd11.prod.outlook.com>
Sure. I updated the patch per comments.
Thanks,
Guo
-----Original Message-----
From: Ni, Ray <ray.ni@intel.com>
Sent: Monday, September 27, 2021 7:11 PM
To: Dong, Guo <guo.dong@intel.com>; devel@edk2.groups.io
Cc: Ma, Maurice <maurice.ma@intel.com>; You, Benjamin <benjamin.you@intel.com>
Subject: RE: [`edk2-devel][PATCH] UefiPayloadPkg: Build a HOB from bootloader ACPI table
I prefer we still let caller to provide the HOB pointer.
This also eliminates a global variable "mAcpiBoardInfo".
You could change the BuildHobFromAcpi() to return the HOB pointer.
So that the pointer can be directly passed to ParseMemoryInfo().
Thanks,
Ray
> -----Original Message-----
> From: Dong, Guo <guo.dong@intel.com>
> Sent: Monday, September 27, 2021 2:32 AM
> To: Ni, Ray <ray.ni@intel.com>; devel@edk2.groups.io
> Cc: Ma, Maurice <maurice.ma@intel.com>; You, Benjamin <benjamin.you@intel.com>
> Subject: RE: [`edk2-devel][PATCH] UefiPayloadPkg: Build a HOB from bootloader ACPI table
>
>
> Hi Ray,
>
> In this patch, we added a shared file AcpiTable.c for both universal payload and non-universal payload.
> The exposed API from this file is: EFI_STATUS BuildHobFromAcpi ( IN UINT64 AcpiTableBase);
> This function will build an ACPI board HOB based on the information from ACPI table.
>
> For universal payload, it calls this function to build a hob for other modules. The main function is very simple and clear.
>
> For non-universal payload, ACPI board HOB is used in the ParseMemoryInfo() callback for PCIE base info.
> So we could get this HOB from the caller, or get this HOB inside the callback. I select to do it inside the callback.
>
> Thanks,
> Guo
>
> -----Original Message-----
> From: Ni, Ray <ray.ni@intel.com>
> Sent: Saturday, September 25, 2021 7:48 PM
> To: Dong, Guo <guo.dong@intel.com>; devel@edk2.groups.io
> Cc: Ma, Maurice <maurice.ma@intel.com>; You, Benjamin <benjamin.you@intel.com>
> Subject: RE: [`edk2-devel][PATCH] UefiPayloadPkg: Build a HOB from bootloader ACPI table
>
>
> - Status = ParseMemoryInfo (MemInfoCallbackMmio, &AcpiBoardInfo);
>
> + Status = ParseMemoryInfo (MemInfoCallbackMmio, NULL);
>
> Guo,
> I am curious why you changed this part.
> Without this change, MemInfoCallbackMmio() can get the AcpiBoardInfo from the parameter.
> With the change, it has to locate the Guided HOB itself.
>
>
> Other parts look good to me.
>
> Thanks,
> Ray
next prev parent reply other threads:[~2021-09-28 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 3:59 [`edk2-devel][PATCH] UefiPayloadPkg: Build a HOB from bootloader ACPI table Guo Dong
2021-09-26 2:47 ` Ni, Ray
2021-09-26 18:32 ` Guo Dong
2021-09-28 2:10 ` Ni, Ray
2021-09-28 17:19 ` Guo Dong [this message]
2021-09-29 2:41 ` 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=DM6PR11MB362711836E8B99D0CA842ABB9EA89@DM6PR11MB3627.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