Re: [PATCH v2 13/13] arch, mm: make releasing of memory to page allocator more explicit

[Mike Rapoport <rppt@kernel.org>]

(reduced 'cc to m68k list)

Hi Geert,

On Thu, Mar 13, 2025 at 04:19:10PM +0100, Geert Uytterhoeven wrote:
> On Thu, 13 Mar 2025 at 14:53, Mike Rapoport <rppt@kernel.org> wrote:
> > From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
> >
> > The point where the memory is released from memblock to the buddy allocator
> > is hidden inside arch-specific mem_init()s and the call to
> > memblock_free_all() is needlessly duplicated in every artiste cure and
> > after introduction of arch_mm_preinit() hook, mem_init() implementation on
> > many architecture only contains the call to memblock_free_all().
> >
> > Pull memblock_free_all() call into mm_core_init() and drop mem_init() on
> > relevant architectures to make it more explicit where the free memory is
> > released from memblock to the buddy allocator and to reduce code
> > duplication in architecture specific code.
> >
> > Acked-by: Dave Hansen <dave.hansen@linux.intel.com>     # x86
> > Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> 
> >  arch/m68k/mm/init.c          |  2 --
> 
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> # m68k

Thanks :)

While working on this I was wondering if init_pointer_tables() can be moved
from mem_init() to motorola::paging_init(). It seems to me that it can, but
I wasn't sure enough so I left it there for now.
 
> Gr{oetje,eeting}s,
> 
>                         Geert

-- 
Sincerely yours,
Mike.