From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: devel@edk2.groups.io
Cc: ming.huang@linaro.org, hao.a.wu@intel.com, jian.j.wang@intel.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH resend] MdeModulePkg/EsrtDxe: allocate ESRT table from RtServicesData memory
Date: Fri, 19 Apr 2019 16:13:19 +0200 [thread overview]
Message-ID: <20190419141319.11084-1-ard.biesheuvel@linaro.org> (raw)
Given that the firmware itself may access the ESRT table when the OS
invokes the UpdateCapsule () boot service, it requires a virtual mapping
and so it needs to be allocated from RtServicesData memory.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
---
MdeModulePkg/Universal/EsrtDxe/EsrtDxe.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MdeModulePkg/Universal/EsrtDxe/EsrtDxe.c b/MdeModulePkg/Universal/EsrtDxe/EsrtDxe.c
index a386a9770583..1741cbe8f2b5 100644
--- a/MdeModulePkg/Universal/EsrtDxe/EsrtDxe.c
+++ b/MdeModulePkg/Universal/EsrtDxe/EsrtDxe.c
@@ -571,7 +571,8 @@ EsrtReadyToBootEventNotify (
goto EXIT;
}
- EsrtTable = AllocatePool(sizeof(EFI_SYSTEM_RESOURCE_TABLE) + NonFmpRepositorySize + FmpRepositorySize);
+ EsrtTable = AllocateRuntimePool (sizeof(EFI_SYSTEM_RESOURCE_TABLE) +
+ NonFmpRepositorySize + FmpRepositorySize);
if (EsrtTable == NULL) {
DEBUG ((EFI_D_ERROR, "Esrt table memory allocation failure\n"));
goto EXIT;
--
2.20.1
next reply other threads:[~2019-04-19 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 14:13 Ard Biesheuvel [this message]
2019-04-19 17:36 ` [edk2-devel] [PATCH resend] MdeModulePkg/EsrtDxe: allocate ESRT table from RtServicesData memory Michael D Kinney
2019-04-19 17:42 ` Ard Biesheuvel
2019-04-19 17:53 ` Ard Biesheuvel
2019-04-19 18:08 ` Michael D Kinney
2019-04-19 18:11 ` Ard Biesheuvel
2019-04-19 18:23 ` Michael D Kinney
2019-04-19 18:38 ` Ard Biesheuvel
2019-04-19 18:43 ` Ard Biesheuvel
2019-04-19 19:46 ` Michael D Kinney
2019-04-19 20:04 ` Michael D Kinney
2019-04-20 10:25 ` Ard Biesheuvel
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=20190419141319.11084-1-ard.biesheuvel@linaro.org \
--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