From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Subject: Re: [PATCH 1/2] OvmfPkg: disable build-time relocation for DXEFV modules
Date: Mon, 3 Jul 2017 19:53:31 +0200 [thread overview]
Message-ID: <c6f1c831-2771-e0a3-a4ed-743129c6e031@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14D750C3D@shsmsx102.ccr.corp.intel.com>
On 07/03/17 17:08, Gao, Liming wrote:
> PI spec has no limitation that XIP is for PEIM only. DXE driver may be
> built as XIP for other purpose. For example, if DXE driver image
> address is not zero, DxeCore will try allocating the preferred address
> and load it. In another case, once DXE driver is relocated at build
> time, DxeCore will dispatch it and start it directly without loading,
> it may save boot performance.
OK, I'll update the commit message on patch #1 and repost the series.
Thanks
Laszlo
next prev parent reply other threads:[~2017-07-03 17:51 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 [this message]
2017-07-05 17:48 ` Jordan Justen
2017-07-05 17:55 ` Laszlo Ersek
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=c6f1c831-2771-e0a3-a4ed-743129c6e031@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