Hi Serge,

On 02/02/18 03:54, Serge Semin wrote:
Low memory can be tested at this point, since all the
reservations have just been finished without much of
additional allocations.


Perhaps something along the lines of:
"Allow an early memtest to be performed by calling early_memtest. Testing at this point in the boot sequence should be safe since all critical areas are now reserved and a minimum of allocations have been done."

Otherwise, looks good to me.

Reviewed-by: Matt Redfearn <matt.redfe...@mips.com>

Thanks,
Matt


Signed-off-by: Serge Semin <fancer.lan...@gmail.com>
---
  arch/mips/kernel/setup.c | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
index 531a1471a2a4..a0eac8160750 100644
--- a/arch/mips/kernel/setup.c
+++ b/arch/mips/kernel/setup.c
@@ -850,6 +850,8 @@ static void __init arch_mem_init(char **cmdline_p)
        memblock_allow_resize();
memblock_dump_all();
+
+       early_memtest(PFN_PHYS(min_low_pfn), PFN_PHYS(max_low_pfn));
  }
static void __init resource_init(void)

Reply via email to