From: Laszlo Ersek <lersek@redhat.com>
To: Liming Gao <liming.gao@intel.com>, edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>
Subject: Re: [Patch] MdeModulePkg PeiCore: Add error message to describe PEIM load failure
Date: Thu, 8 Feb 2018 10:30:34 +0100 [thread overview]
Message-ID: <f1b9a1f2-a819-7ab5-c262-c70effa8d0f9@redhat.com> (raw)
In-Reply-To: <1518077919-10176-1-git-send-email-liming.gao@intel.com>
On 02/08/18 09:18, Liming Gao wrote:
> If PEIM image address doesn't meet with its section alignment, it will
> load fail. PeiCore adds more debug message to report it.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
> ---
> MdeModulePkg/Core/Pei/Image/Image.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/MdeModulePkg/Core/Pei/Image/Image.c b/MdeModulePkg/Core/Pei/Image/Image.c
> index 1985411..f41d3ac 100644
> --- a/MdeModulePkg/Core/Pei/Image/Image.c
> +++ b/MdeModulePkg/Core/Pei/Image/Image.c
> @@ -1,7 +1,7 @@
> /** @file
> Pei Core Load Image Support
>
> -Copyright (c) 2006 - 2017, Intel Corporation. All rights reserved.<BR>
> +Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
> This program and the accompanying materials
> are licensed and made available under the terms and conditions of the BSD License
> which accompanies this distribution. The full text of the license may be found at
> @@ -506,6 +506,9 @@ LoadAndRelocatePeCoffImage (
> //
> Status = PeCoffLoaderLoadImage (&ImageContext);
> if (EFI_ERROR (Status)) {
> + if (ImageContext.ImageError == IMAGE_ERROR_INVALID_SECTION_ALIGNMENT) {
> + DEBUG ((DEBUG_ERROR, "PEIM Image Address 0x%11p doesn't meet with section alignment 0x%x.\n", (VOID*)(UINTN)ImageContext.ImageAddress, ImageContext.SectionAlignment));
> + }
Just curious, is there any particular reason for the 11 chars field
width? Personally I would print ImageContext.ImageAddress (which has
type PHYSICAL_ADDRESS, i.e. UINT64), without any type conversion, and
with the following format string:
0x%Lx
or maybe
0x%16Lx
... There's no need to resubmit the patch because of my question; I'm
just curious if I'm missing something.
Thanks!
Laszlo
> return Status;
> }
> //
> @@ -612,6 +615,8 @@ PeiLoadImageLoadImage (
> }
> }
>
> + DEBUG ((DEBUG_INFO, "Loading PEIM %g\n", FileHandle));
> +
> //
> // If memory is installed, perform the shadow operations
> //
>
I'
next prev parent reply other threads:[~2018-02-08 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 8:18 [Patch] MdeModulePkg PeiCore: Add error message to describe PEIM load failure Liming Gao
2018-02-08 9:30 ` Laszlo Ersek [this message]
2018-02-08 10:24 ` Gao, Liming
2018-02-08 10:31 ` Laszlo Ersek
2018-02-15 20:20 ` Brian J. Johnson
2018-02-08 10:11 ` Zeng, Star
2018-02-08 10:24 ` Gao, Liming
2018-02-08 10:30 ` Zeng, Star
2018-02-08 10:39 ` Gao, Liming
2018-02-09 2:03 ` Zeng, Star
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=f1b9a1f2-a819-7ab5-c262-c70effa8d0f9@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