[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MWHPR2201MB12770C946CB59879CEF63C5FC1300@MWHPR2201MB1277.namprd22.prod.outlook.com>
Date: Mon, 6 May 2019 19:12:04 +0000
From: Paul Burton <paul.burton@...s.com>
To: Serge Semin <fancer.lancer@...il.com>
CC: Ralf Baechle <ralf@...ux-mips.org>,
Paul Burton <pburton@...ecomp.com>,
James Hogan <jhogan@...nel.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Bogendoerfer <tbogendoerfer@...e.de>,
Huacai Chen <chenhc@...ote.com>,
Stefan Agner <stefan@...er.ch>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Juergen Gross <jgross@...e.com>,
Serge Semin <Sergey.Semin@...latforms.ru>,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Subject: Re: [PATCH v2 5/5] mips: Manually call fdt_init_reserved_mem() method
Hello,
Serge Semin wrote:
> Since memblock-patchset was introduced the reserved-memory nodes are
> supported being declared in dt-files. So these nodes are actually parsed
> during the arch setup procedure when the early_init_fdt_scan_reserved_mem()
> method is called. But due to the arch-specific boot mem_map container
> utilization we need to manually call the fdt_init_reserved_mem() method
> after all the available and reserved memory has been moved to memblock.
> The first function call performed before bootmem_init() by the
> early_init_fdt_scan_reserved_mem() routine fails due to the lack of any
> memblock memory regions to allocate from at that stage.
>
> Signed-off-by: Serge Semin <fancer.lancer@...il.com>
Applied to mips-next.
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paul.burton@...s.com to report it. ]
Powered by blists - more mailing lists