From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] arm64 UEFI early FDT handling
Date: Mon, 21 Sep 2015 17:21:22 -0700 [thread overview]
Message-ID: <1442881288-13962-1-git-send-email-ard.biesheuvel@linaro.org> (raw)
This is a followup to the "arm64: update/clarify/relax Image and FDT placement
rules" series I sent a while ago:
(http://article.gmane.org/gmane.linux.ports.arm.kernel/407148)
This has now been split in two series: this first series deals with the
early FDT handling, primarily in the context of UEFI, but not exclusively.
A number of minor issues exist in the early UEFI/FDT handling path, such as:
- when booting via UEFI, memreserve entries are removed from the device tree but
the /reserved-memory node is not
- memory nodes are removed from the device tree in a way that is not officially
supported by the libfdt API (i.e., you cannot delete nodes while traversing
the tree)
- removal of memory nodes may discard annotations (such as NUMA topology) that
should ideally be retained, or may corrupt the tree by discarding nodes
referenced by phandles.
Patches #1 and #2 introduce an arm64 specific version of
early_init_dt_add_memory_arch() so that we can modify it later to ignore DT
memory nodes if booting via UEFI.
Patch #3 moves some UEFI+FDT init code around before making changes to it.
Patch #4 moves the UEFI initialization to before the early FDT scanning so we
know at that point whether we are booting via UEFI or not.
Patch #5 changes the UEFI init code so that memory nodes are simply ignored, so
that they don't have to be removed by the stub anymore.
Patch #6 does the same as #5, but for memreserves and the /reserved-memory
node.
Changes since v2:
- instead of copying the generic implementation, turn
early_init_dt_add_memory_arch() into a weak alias so that it is still
accessible to overrides
Changes since v1:
- dropped first two patches, they have been merged into v4.2-rc1
- dropped last patch regarding FDT placement by the stub, this is not entirely
relevant to the primary issue targeted by this series
- rebased onto for-next/core (arm64) as of today
Ard Biesheuvel (6):
of/fdt: make generic early_init_dt_add_memory_arch() a weak alias
arm64: override generic version of early_init_dt_add_memory_arch()
efi: move FDT handling to separate object file
arm64/efi: move EFI /chosen node parsing before early FDT processing
arm64/efi: ignore DT memory nodes instead of removing them
arm64/efi: ignore DT memreserve entries instead of removing them
arch/arm64/include/asm/efi.h | 2 +
arch/arm64/kernel/efi.c | 26 ++++--
arch/arm64/kernel/setup.c | 3 +
arch/arm64/mm/init.c | 12 ++-
drivers/firmware/efi/Makefile | 1 +
drivers/firmware/efi/efi-fdt.c | 73 +++++++++++++++++
drivers/firmware/efi/efi.c | 84 --------------------
drivers/firmware/efi/libstub/fdt.c | 33 +-------
drivers/of/fdt.c | 7 +-
include/linux/efi.h | 2 +-
include/linux/of_fdt.h | 1 +
11 files changed, 116 insertions(+), 128 deletions(-)
create mode 100644 drivers/firmware/efi/efi-fdt.c
--
1.9.1
next reply other threads:[~2015-09-22 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 0:21 Ard Biesheuvel [this message]
2015-09-22 0:21 ` [PATCH v3 1/6] of/fdt: make generic early_init_dt_add_memory_arch() a weak alias Ard Biesheuvel
2015-09-22 0:21 ` [PATCH v3 2/6] arm64: override generic version of early_init_dt_add_memory_arch() Ard Biesheuvel
2015-09-22 0:21 ` [PATCH v3 3/6] efi: move FDT handling to separate object file Ard Biesheuvel
2015-09-22 0:21 ` [PATCH v3 4/6] arm64/efi: move EFI /chosen node parsing before early FDT processing Ard Biesheuvel
2015-09-22 0:21 ` [PATCH v3 5/6] arm64/efi: ignore DT memory nodes instead of removing them Ard Biesheuvel
2015-09-22 0:21 ` [PATCH v3 6/6] arm64/efi: ignore DT memreserve entries " Ard Biesheuvel
2015-09-29 7:38 ` [PATCH v3 0/6] arm64 UEFI early FDT handling Ard Biesheuvel
2015-11-16 10:43 ` Will Deacon
2015-11-16 10:57 ` Ard Biesheuvel
2015-11-16 10:57 ` Catalin Marinas
2015-11-16 11:00 ` 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=1442881288-13962-1-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).