Re: [PATCH v2 13/13] arch, mm: make releasing of memory to page allocator more explicit
Geert Uytterhoeven <[email protected]>
| Newsgroups | org.kernel.vger.linux-hexagon,dev.linux.lists.loongarch,org.infradead.lists.linux-riscv,org.infradead.lists.linux-snps-arc,org.infradead.lists.linux-um,org.kernel.vger.linux-alpha,org.kernel.vger.linux-arch,org.kernel.vger.linux-csky,org.kernel.vger.linux-kernel,org.kernel.vger.linux-m68k,org.kernel.vger.linux-mips,org.kernel.vger.linux-openrisc,org.kernel.vger.linux-parisc,org.kernel.vger.linux-s390,org.kernel.vger.linux-sh,org.kernel.vger.sparclinux,org.kvack.linux-mm,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <CAMuHMdWCBL_cg1NgbHCA3e9GTob_P9mTuN_Tepvigci6rxDmbg@mail.gmail.com> |
On Thu, 13 Mar 2025 at 14:53, Mike Rapoport <[email protected]> wrote: > From: "Mike Rapoport (Microsoft)" <[email protected]> > > 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 <[email protected]> # x86 > Signed-off-by: Mike Rapoport (Microsoft) <[email protected]> > arch/m68k/mm/init.c | 2 -- Acked-by: Geert Uytterhoeven <[email protected]> # m68k Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds