From: Laszlo Ersek <lersek@redhat.com>
To: Jordan Justen <jordan.l.justen@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 1/2] OvmfPkg: disable build-time relocation for DXEFV modules
Date: Wed, 5 Jul 2017 19:55:12 +0200 [thread overview]
Message-ID: <669b6033-7914-4d20-66cd-04ed29b76f2b@redhat.com> (raw)
In-Reply-To: <149927689598.638.6499247930051801274@jljusten-skl>
On 07/05/17 19:48, Jordan Justen wrote:
> On 2017-06-28 20:32:54, Gao, Liming wrote:
>> Laszlo:
>> LMFA feature doesn't do PE image rebase at build time. Only XIP
>> module needs to be rebased at build time. LMFA feature will
>> specify the loaded memory address for each PE image. At build
>> time, build tool records the memory address into the one field of
>> PE image. It doesn't rebase PE image. At boot time,
>> PeiCore/DxeCore/SmmCore will parse PE image, and try to load it at
>> the preferred memory address. If the preferred memory address is
>> not available, PE image will be loaded to other memory address.
>> LMFA feature only supports the source build EFI image, not support
>> the binary EFI image. This is a debug feature.
>>
>> For this case, OvmfPkg DXEFV doesn't require to run as XIP. So, it
>> doesn't require rebase. I agree this change.
>>
>
> Liming,
>
> With this flag set to FALSE, do we attempt to rebase the images, but
> just not fail if we can't rebase one of the modules? Or, will this
> disable rebasing of all modules in the FV?
>
> I don't think we really make use of this debug feature in OVMF today,
> but I was wondering what potential impact it might have. I thought in
> some cases by loading the modules at a fixed address it can help with
> loading symbols for debug, right?
>
> Laszlo,
>
> I don't think you need to hold off on the patches for this answer, so
> you can add an Acked-by from me for your v2.
Thanks, will do.
Laszlo
next prev parent reply other threads:[~2017-07-05 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 22:06 [PATCH 0/2] OvmfPkg: refresh -D E1000_ENABLE (Intel proprietary driver for e1000) Laszlo Ersek
2017-06-28 22:06 ` [PATCH 1/2] OvmfPkg: disable build-time relocation for DXEFV modules Laszlo Ersek
2017-06-29 3:32 ` Gao, Liming
2017-07-01 20:36 ` Laszlo Ersek
2017-07-03 15:08 ` Gao, Liming
2017-07-03 17:53 ` Laszlo Ersek
2017-07-05 17:48 ` Jordan Justen
2017-07-05 17:55 ` Laszlo Ersek [this message]
2017-06-28 22:06 ` [PATCH 2/2] OvmfPkg: update -D E1000_ENABLE from Intel PROEFI v.07 to BootUtil v.22 Laszlo Ersek
2017-06-30 1:20 ` Wu, Jiaxin
2017-07-01 20:22 ` 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=669b6033-7914-4d20-66cd-04ed29b76f2b@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