From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v15 1/6] efi: ARM/arm64: ignore DT memory nodes instead of removing them
Date: Fri, 18 Mar 2016 12:26:09 +0000 [thread overview]
Message-ID: <20160318122609.GS2619@codeblueprint.co.uk> (raw)
In-Reply-To: <1457481587-8976-2-git-send-email-ddaney.cavm@gmail.com>
On Tue, 08 Mar, at 03:59:42PM, David Daney wrote:
> From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> There are two problems with the UEFI stub DT memory node removal
> routine:
> - it deletes nodes as it traverses the tree, which happens to work
> but is not supported, as deletion invalidates the node iterator;
> - deleting memory nodes entirely may discard annotations in the form
> of additional properties on the nodes.
>
> Since the discovery of DT memory nodes occurs strictly before the
> UEFI init sequence, we can simply clear the memblock memory table
> before parsing the UEFI memory map. This way, it is no longer
> necessary to remove the nodes, so we can remove that logic from the
> stub as well.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Signed-off-by: David Daney <david.daney@cavium.com>
> ---
> drivers/firmware/efi/arm-init.c | 8 ++++++++
> drivers/firmware/efi/libstub/fdt.c | 24 +-----------------------
> 2 files changed, 9 insertions(+), 23 deletions(-)
I've not delved into the rest of the series too deeply, but this looks
like a straight forward change.
Reviewed-by: Matt Fleming <matt@codeblueprint.co.uk>
> diff --git a/drivers/firmware/efi/arm-init.c b/drivers/firmware/efi/arm-init.c
> index 9e15d57..40c9d85 100644
> --- a/drivers/firmware/efi/arm-init.c
> +++ b/drivers/firmware/efi/arm-init.c
> @@ -143,6 +143,14 @@ static __init void reserve_regions(void)
> if (efi_enabled(EFI_DBG))
> pr_info("Processing EFI memory map:\n");
>
> + /*
> + * Discard memblocks discovered so far: if there are any at this
> + * point, they originate from memory nodes in the DT, and UEFI
> + * uses its own memory map instead.
> + */
> + memblock_dump_all();
> + memblock_remove(0, ULLONG_MAX);
> +
> for_each_efi_memory_desc(&memmap, md) {
> paddr = md->phys_addr;
> npages = md->num_pages;
Out of curiosity, could some kind person explain (or point me at a
previous explanation for) why we may have both DT memory nodes and a
UEFI memory map and why they're not compatible enough to co-exist?
next prev parent reply other threads:[~2016-03-18 12:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 23:59 [PATCH v15 0/6] arm64, numa: Add numa support for arm64 platforms David Daney
2016-03-08 23:59 ` [PATCH v15 1/6] efi: ARM/arm64: ignore DT memory nodes instead of removing them David Daney
2016-03-18 12:26 ` Matt Fleming [this message]
2016-03-18 12:31 ` Ard Biesheuvel
2016-03-18 12:56 ` Matt Fleming
2016-03-18 13:11 ` Ard Biesheuvel
2016-03-08 23:59 ` [PATCH v15 2/6] Documentation, dt, numa: dt bindings for NUMA David Daney
2016-03-08 23:59 ` [PATCH v15 3/6] of, numa: Add NUMA of binding implementation David Daney
2016-03-08 23:59 ` [PATCH v15 4/6] arm64: Move unflatten_device_tree() call earlier David Daney
2016-03-08 23:59 ` [PATCH v15 5/6] arm64, numa: Add NUMA support for arm64 platforms David Daney
2016-04-13 14:09 ` Steve Capper
2016-04-13 14:30 ` Steve Capper
2016-03-08 23:59 ` [PATCH v15 6/6] arm64, mm, numa: Add NUMA balancing support for arm64 David Daney
2016-03-22 18:48 ` [PATCH v15 0/6] arm64, numa: Add numa support for arm64 platforms Jon Masters
2016-03-22 21:45 ` David Daney
2016-04-05 13:08 ` Graeme Gregory
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=20160318122609.GS2619@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--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).