diff options
author | Matt Fleming <matt@codeblueprint.co.uk> | 2016-04-25 20:06:38 (GMT) |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2016-04-28 09:33:50 (GMT) |
commit | 78ce248faa3c46e24e9bd42db3ab3650659f16dd (patch) | |
tree | e40ffbc803346ab0a8d2e0994ab7b20462b20a98 /arch/microblaze | |
parent | 30d7bf034c034995f34dae265d96247f7f12044e (diff) | |
download | linux-78ce248faa3c46e24e9bd42db3ab3650659f16dd.tar.xz |
efi: Iterate over efi.memmap in for_each_efi_memory_desc()
Most of the users of for_each_efi_memory_desc() are equally happy
iterating over the EFI memory map in efi.memmap instead of 'memmap',
since the former is usually a pointer to the latter.
For those users that want to specify an EFI memory map other than
efi.memmap, that can be done using for_each_efi_memory_desc_in_map().
One such example is in the libstub code where the firmware is queried
directly for the memory map, it gets iterated over, and then freed.
This change goes part of the way toward deleting the global 'memmap'
variable, which is not universally available on all architectures
(notably IA64) and is rather poorly named.
Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Mark Salter <msalter@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-efi@vger.kernel.org
Link: http://lkml.kernel.org/r/1461614832-17633-7-git-send-email-matt@codeblueprint.co.uk
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'arch/microblaze')
0 files changed, 0 insertions, 0 deletions