public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Dandan Bi <dandan.bi@intel.com>, Hao A Wu <hao.a.wu@intel.com>,
	Jeff Brasen <jbrasen@nvidia.com>,
	Jian J Wang <jian.j.wang@intel.com>,
	Leif Lindholm <leif@nuviainc.com>,
	Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [PATCH] MdeModulePkg/Core/Dxe: log memory base and length, after lib ctors again
Date: Tue, 3 Nov 2020 19:12:57 +0100	[thread overview]
Message-ID: <2ab23452-64d2-be67-10e3-7b94c390683f@redhat.com> (raw)
In-Reply-To: <20201103161557.30621-1-lersek@redhat.com>

On 11/3/20 5:15 PM, Laszlo Ersek wrote:
> CoreInitializeMemoryServices() logs "BaseAddress" and "Length" with
> DEBUG() before DxeMain() calls ProcessLibraryConstructorList()
> explicitly. (Library construction is not an automatic part of the DXE
> Core entry point.)
> 
> So those DEBUG()s in CoreInitializeMemoryServices() are issued against
> an un-constructed DebugLib, and also against a -- possibly underlying --
> un-constructed SerialPortLib.

Uh...

> 
> Some DebugLib instances can deal with this (see for example commit
> 91a5b1365075, "OvmfPkg/PlatformDebugLibIoPort: fix port detection for
> use in the DXE Core", 2018-08-06), while some others can't (see for
> example the DebugLib instance
> "MdePkg/Library/BaseDebugLibSerialPort/BaseDebugLibSerialPort.inf"
> coupled with the SerialPortLib instance
> "ArmVirtPkg/Library/FdtPL011SerialPortLib/FdtPL011SerialPortLib.inf").

Yes.

> 
> Addressing this issue in a SerialPortLib instance that underlies
> BaseDebugLibSerialPort seems wrong; either the DebugLib instance should
> cope directly with being called un-constructed (see again commit
> 91a5b1365075), or the DXE Core should log relevant information *at
> least* after library instances have been constructed. This patch
> implements the latter (only for the "BaseAddress" and "Length" values
> calculated by CoreInitializeMemoryServices()).

Sounds good.

Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>

> 
> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
> Cc: Dandan Bi <dandan.bi@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Jeff Brasen <jbrasen@nvidia.com>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Leif Lindholm <leif@nuviainc.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> ---
> 
> Notes:
>     Repo:   https://pagure.io/lersek/edk2.git
>     Branch: dxecore_report_mem
> 
>  MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c b/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c
> index 5ee4cd10b436..db21311f9352 100644
> --- a/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c
> +++ b/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c
> @@ -297,8 +297,16 @@ DxeMain (
>    ProcessLibraryConstructorList (gDxeCoreImageHandle, gDxeCoreST);
>    PERF_CROSSMODULE_END   ("PEI");
>    PERF_CROSSMODULE_BEGIN ("DXE");
>  
> +  //
> +  // Log MemoryBaseAddress and MemoryLength again (from
> +  // CoreInitializeMemoryServices()), now that library constructors have
> +  // executed.
> +  //
> +  DEBUG ((DEBUG_INFO, "%a: MemoryBaseAddress=0x%Lx MemoryLength=0x%Lx\n",
> +    __FUNCTION__, MemoryBaseAddress, MemoryLength));
> +
>    //
>    // Report DXE Core image information to the PE/COFF Extra Action Library
>    //
>    ZeroMem (&ImageContext, sizeof (ImageContext));
> 


  reply	other threads:[~2020-11-03 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 16:15 [PATCH] MdeModulePkg/Core/Dxe: log memory base and length, after lib ctors again Laszlo Ersek
2020-11-03 18:12 ` Philippe Mathieu-Daudé [this message]
2020-11-05  2:07   ` 回复: " gaoliming
2020-11-06 21:20     ` [edk2-devel] " Laszlo Ersek

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=2ab23452-64d2-be67-10e3-7b94c390683f@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