From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Arvind Sankar <nivedita@alum.mit.edu>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxim Uvarov <maxim.uvarov@linaro.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: [PATCH 1/1] efi/libstub: DRAM base calculation
Date: Fri, 4 Sep 2020 17:50:25 +0200 [thread overview]
Message-ID: <20200904155025.55718-1-xypron.glpk@gmx.de> (raw)
In the memory map the regions with the lowest addresses may be of type
EFI_RESERVED_TYPE. The reserved areas may be discontinuous relative to the
rest of the memory. So for calculating the maximum loading address for the
device tree and the initial ramdisk image these reserved areas should not
be taken into account.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
---
drivers/firmware/efi/libstub/efi-stub.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware/efi/libstub/efi-stub.c b/drivers/firmware/efi/libstub/efi-stub.c
index c2484bf75c5d..13058ac75765 100644
--- a/drivers/firmware/efi/libstub/efi-stub.c
+++ b/drivers/firmware/efi/libstub/efi-stub.c
@@ -106,7 +106,8 @@ static unsigned long get_dram_base(void)
map.map_end = map.map + map_size;
for_each_efi_memory_desc_in_map(&map, md) {
- if (md->attribute & EFI_MEMORY_WB) {
+ if (md->attribute & EFI_MEMORY_WB &&
+ md->type != EFI_RESERVED_TYPE) {
if (membase > md->phys_addr)
membase = md->phys_addr;
}
--
2.28.0
next reply other threads:[~2020-09-04 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 15:50 Heinrich Schuchardt [this message]
2020-09-07 7:00 ` [PATCH 1/1] efi/libstub: DRAM base calculation Maxim Uvarov
2020-09-07 8:30 ` Heinrich Schuchardt
2020-09-07 10:21 ` Maxim Uvarov
2020-09-07 15:42 ` Maxim Uvarov
2020-09-09 8:17 ` Ard Biesheuvel
2020-09-09 10:43 ` Maxim Uvarov
2020-09-09 10:46 ` Ard Biesheuvel
2020-09-09 11:04 ` Maxim Uvarov
2020-09-09 20:36 ` Atish Patra
2020-09-10 10:03 ` 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-all 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=20200904155025.55718-1-xypron.glpk@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=ardb@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.uvarov@linaro.org \
--cc=mingo@kernel.org \
--cc=nivedita@alum.mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).