[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be0b6614-708d-a32a-029d-7e606a673e5b@imgtec.com>
Date: Mon, 22 May 2017 11:48:36 +0200
From: Marcin Nowakowski <marcin.nowakowski@...tec.com>
To: Serge Semin <fancer.lancer@...il.com>, <ralf@...ux-mips.org>,
<paul.burton@...tec.com>, <rabinv@...s.com>,
<matt.redfearn@...tec.com>, <james.hogan@...tec.com>,
<alexander.sverdlin@...ia.com>, <robh+dt@...nel.org>,
<frowand.list@...il.com>
CC: <Sergey.Semin@...latforms.ru>, <linux-mips@...ux-mips.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/21] MIPS memblock: Remove bootmem code and switch to
NO_BOOTMEM
Hi Serge,
On 19.12.2016 03:07, Serge Semin wrote:
> Most of the modern platforms supported by linux kernel have already
> been cleaned up of old bootmem allocator by moving to nobootmem
> interface wrapping up the memblock. This patchset is the first
> attempt to do the similar improvement for MIPS for UMA systems
> only.
>
> Even though the porting was performed as much careful as possible
> there still might be problem with support of some platforms,
> especially Loonson3 or SGI IP27, which perform early memory manager
> initialization by their self.
>
> The patchset is split so individual patch being consistent in
> functional and buildable ways. But the MIPS early memory manager
> will work correctly only either with or without the whole set being
> applied. For the same reason a reviewer should not pay much attention
> to methods bootmem_init(), arch_mem_init(), paging_init() and
> mem_init() until they are fully refactored.
>
> The patchset is applied on top of kernel v4.9.
Have you progressed any further with these patches?
They would definitely be useful to include for MIPS arch, so can you let
us know if you are planning to send any updated version?
thanks,
Marcin
Powered by blists - more mailing lists