From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Zeng, Star" <star.zeng@intel.com>
Cc: Peter Jones <pjones@redhat.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Dong, Eric" <eric.dong@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [PATCH] MdeModulePkg/EsrtDxe: allocate ESRT table from RtServicesData memory
Date: Fri, 19 Oct 2018 13:11:20 +0800 [thread overview]
Message-ID: <CAKv+Gu80x53hNaKuA6CR1cyug=cspUk-JdhDMFWp7G9Bg13bMw@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu8-sRrOcVkkPMt0v51mtbqC45-6D17Hs8M8FWnN3xN2+w@mail.gmail.com>
On 19 October 2018 at 13:01, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 19 October 2018 at 12:48, Zeng, Star <star.zeng@intel.com> wrote:
>> Ok, thanks and got the case.
>>
>> DxeCapsuleLibVirtualAddressChangeEvent may be too late as it could not allocate pool to do caching.
>> I meant registering gEfiSystemResourceTableGuid event group notification(installconfigurationtable will trigger event group) and do caching in the notification function.
>>
>>
>
> OK, I will create a bugzilla for this.
>
As I understand it, the reason we require EfiBootServicesData for the
ESRT is because the OS may not care about this table, and so we don't
want to waste the memory. However, if we end up caching the entire
table in EfiRuntimeServicesData anyway [so that the firmware itself
can access it], is there still a point to keeping this requirement?
Shouldn't we update the spec regardless?
next prev parent reply other threads:[~2018-10-19 5:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 2:54 [PATCH] MdeModulePkg/EsrtDxe: allocate ESRT table from RtServicesData memory Ard Biesheuvel
2018-10-19 3:24 ` Ard Biesheuvel
2018-10-19 3:46 ` Zeng, Star
2018-10-19 3:48 ` Ard Biesheuvel
2018-10-19 4:39 ` Zeng, Star
2018-10-19 4:43 ` Ard Biesheuvel
2018-10-19 4:48 ` Zeng, Star
2018-10-19 5:01 ` Ard Biesheuvel
2018-10-19 5:11 ` Ard Biesheuvel [this message]
2018-10-19 5:25 ` Zeng, Star
2018-10-19 5:28 ` Ard Biesheuvel
2018-10-19 6:01 ` 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='CAKv+Gu80x53hNaKuA6CR1cyug=cspUk-JdhDMFWp7G9Bg13bMw@mail.gmail.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