[PATCH] arm: Adjust memory boundaries after reservations

Hi Laura,


On 14 December 2016 at 03:11, Laura Abbott [off-list ref] wrote:

The poorly named sanity_check_meminfo is responsible for setting up the
boundary for lowmem/highmem. This needs to be set up before memblock
reservations can occur. At the time memblock reservations can occur,
memory can also be removed from the system. This can throw off the
calculation of the lowmem/highmem boundary. On some systems this may be
harmless, on others this may result in incorrect ranges being passed to
the main memory allocator. Correct this by recalcuating the
lowmem/highmem boundary after all reservations have been made.
As part of this, rename sanity_check_meminfo to actually refect what the
function is doing.

Reported-by: Magnus Lilja <redacted>
Signed-off-by: Laura Abbott <redacted>
---

Thanks! I've applied the patch on a v4.9 kernel tree and tried it on
the i.MX31 board and the patch resolves the issue.

Tested-by: Magnus Lilja <redacted>

Regards, Magnus