diff options
author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2016-04-08 15:50:23 -0700 |
---|---|---|
committer | Will Deacon <will.deacon@arm.com> | 2016-04-15 18:06:07 +0100 |
commit | 500899c2cc3e3f06140373b587a69d30650f2d9d (patch) | |
tree | 511f461a59e5da71b273c95d941412987321d731 /Documentation | |
parent | ac1ad20f9ed73a22b0a72eb83206302f5fbff55c (diff) | |
download | linux-stable-500899c2cc3e3f06140373b587a69d30650f2d9d.tar.gz linux-stable-500899c2cc3e3f06140373b587a69d30650f2d9d.tar.bz2 linux-stable-500899c2cc3e3f06140373b587a69d30650f2d9d.zip |
efi: ARM/arm64: ignore DT memory nodes instead of removing them
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.
Reviewed-by: Matt Fleming <matt@codeblueprint.co.uk>
Acked-by: Steve Capper <steve.capper@arm.com>
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: David Daney <david.daney@cavium.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions