On October 15, 2019 2:46:59 AM GMT+02:00, Will Deacon [off-list ref] wrote:

On Sat, Sep 28, 2019 at 11:02:26AM +0300, Mike Rapoport wrote:

quoted

From: Mike Rapoport <redacted>

arm64 calls memblock_free() for the initrd area in its implementation

of

quoted

free_initrd_mem(), but this call has no actual effect that late in

the boot

quoted

process. By the time initrd is freed, all the reserved memory is

managed by

quoted

the page allocator and the memblock.reserved is unused, so the only

purpose

quoted

of the memblock_free() call is to keep track of initrd memory for

debugging

quoted

and accounting.

Without the memblock_free() call the only difference between arm64

and the

quoted

generic versions of free_initrd_mem() is the memory poisoning.

Move memblock_free() call to the generic code, enable it there
for the architectures that define ARCH_KEEP_MEMBLOCK and use the

generic

quoted

implementation of free_initrd_mem() on arm64.

Signed-off-by: Mike Rapoport <redacted>
---

v4:
* memblock_free() aligned area around the initrd

Looks straightforward to me:

Acked-by: Will Deacon <will@kernel.org>

 Can it go via arm64 tree?

Will

-- 
Sincerely yours,
Mike

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel