From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/8] arm64/efi: ignore DT memreserve entries instead of removing them
Date: Mon, 11 May 2015 08:41:59 +0200 [thread overview]
Message-ID: <1431326520-17331-8-git-send-email-ard.biesheuvel@linaro.org> (raw)
In-Reply-To: <1431326520-17331-1-git-send-email-ard.biesheuvel@linaro.org>
Now that the reservation of the FDT image itself is split off, we
can make the DT scanning of memreserves conditional on whether we
booted via UEFI and have its memory map available. This allows us
to drop deletion of these memreserves in the stub. It also fixes
the issue where the /reserved-memory/ node (which offers another
way of reserving memory ranges) was not being ignored under UEFI.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
---
arch/arm64/mm/init.c | 3 ++-
drivers/firmware/efi/libstub/fdt.c | 11 +----------
2 files changed, 3 insertions(+), 11 deletions(-)
diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
index 95c239f43384..a3469a436a73 100644
--- a/arch/arm64/mm/init.c
+++ b/arch/arm64/mm/init.c
@@ -179,7 +179,8 @@ void __init arm64_memblock_init(void)
memblock_reserve(__virt_to_phys(initrd_start), initrd_end - initrd_start);
#endif
- early_init_fdt_scan_reserved_mem();
+ if (!efi_enabled(EFI_MEMMAP))
+ early_init_fdt_scan_reserved_mem();
/* 4GB maximum for 32-bit only capable devices */
if (IS_ENABLED(CONFIG_ZONE_DMA))
diff --git a/drivers/firmware/efi/libstub/fdt.c b/drivers/firmware/efi/libstub/fdt.c
index 343e7992bd8f..a7e87cd582f2 100644
--- a/drivers/firmware/efi/libstub/fdt.c
+++ b/drivers/firmware/efi/libstub/fdt.c
@@ -24,8 +24,7 @@ efi_status_t update_fdt(efi_system_table_t *sys_table, void *orig_fdt,
unsigned long map_size, unsigned long desc_size,
u32 desc_ver)
{
- int node, num_rsv;
- int status;
+ int node, status;
u32 fdt_val32;
u64 fdt_val64;
@@ -53,14 +52,6 @@ efi_status_t update_fdt(efi_system_table_t *sys_table, void *orig_fdt,
if (status != 0)
goto fdt_set_fail;
- /*
- * Delete all memory reserve map entries. When booting via UEFI,
- * kernel will use the UEFI memory map to find reserved regions.
- */
- num_rsv = fdt_num_mem_rsv(fdt);
- while (num_rsv-- > 0)
- fdt_del_mem_rsv(fdt, num_rsv);
-
node = fdt_subnode_offset(fdt, 0, "chosen");
if (node < 0) {
node = fdt_add_subnode(fdt, 0, "chosen");
--
1.9.1
next prev parent reply other threads:[~2015-05-11 6:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 6:41 [PATCH 0/8] arm64 UEFI early FDT handling Ard Biesheuvel
2015-05-11 6:41 ` [PATCH 1/8] of/fdt: split off FDT self reservation from memreserve processing Ard Biesheuvel
2015-05-22 10:35 ` Catalin Marinas
2015-06-01 7:56 ` Ard Biesheuvel
2015-06-01 9:56 ` Mark Rutland
2015-06-01 10:46 ` Ard Biesheuvel
2015-06-01 11:02 ` Mark Rutland
2015-06-01 11:14 ` Ard Biesheuvel
2015-06-01 11:18 ` Mark Rutland
2015-05-11 6:41 ` [PATCH 2/8] arm64: use fixmap region for permanent FDT mapping Ard Biesheuvel
2015-06-01 9:53 ` Mark Rutland
2015-06-01 9:55 ` Ard Biesheuvel
2015-05-11 6:41 ` [PATCH 3/8] arm64: override early_init_dt_add_memory_arch() Ard Biesheuvel
2015-05-11 6:41 ` [PATCH 4/8] efi: move FDT handling to separate object file Ard Biesheuvel
2015-05-26 18:15 ` Matt Fleming
2015-05-11 6:41 ` [PATCH 5/8] arm64/efi: move EFI init before early FDT processing Ard Biesheuvel
2015-05-11 6:41 ` [PATCH 6/8] arm64/efi: ignore DT memory nodes instead of removing them Ard Biesheuvel
2015-05-11 16:28 ` Ganapatrao Kulkarni
2015-05-12 14:31 ` Leif Lindholm
2015-05-12 15:01 ` Ard Biesheuvel
2015-05-11 6:41 ` Ard Biesheuvel [this message]
2015-05-11 6:42 ` [PATCH 8/8] arm64/efi: adapt to relaxed FDT placement requirements 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=1431326520-17331-8-git-send-email-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).