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

From: "Mike Rapoport (Microsoft)" 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()

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

On Tue, Mar 11, 2025 at 05:51:06PM +, Mark Brown wrote: > On Thu, Mar 06, 2025 at 08:51:20PM +0200, Mike Rapoport wrote: > > From: "Mike Rapoport (Microsoft)" > > > > high_memory defines upper bound on the directly mapped memory. > > This bound is defined by the beginning of ZONE_HIGHMEM when

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

On Tue, Mar 11, 2025 at 09:33:29PM +, Mark Brown wrote: > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Linux version 6.14.0-rc6-next-20250311 (tuxmake@tuxmake) > (arm-linux-gnueabihf-gcc (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils for > Debian) 2.

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

On Tue, Mar 11, 2025 at 09:59:32PM +, Russell King (Oracle) wrote: > On Tue, Mar 11, 2025 at 05:51:06PM +, Mark Brown wrote: > > On Thu, Mar 06, 2025 at 08:51:20PM +0200, Mike Rapoport wrote: > > > From: "Mike Rapoport (Microsoft)" > > > > > > high_memory defines upper bound on the direct

[PATCH 02/13] csky: move setup_initrd() to setup.c

From: "Mike Rapoport (Microsoft)" Memory used by initrd should be reserved as soon as possible before there any memblock allocations that might overwrite that memory. This will also help with pulling out memblock_free_all() to the generic code and reducing code duplication in arch::mem_init().

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

roduced with qemu? > > https://lava.sirena.org.uk/scheduler/job/1184953 > > Turns out it's actually producing output on qemu: > > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Linux version 6.14.0-rc6-next-20250311 (tuxmake@tuxmake) > (arm-linux-gn

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

Hi Mark, On Tue, Mar 11, 2025 at 05:51:06PM +, Mark Brown wrote: > On Thu, Mar 06, 2025 at 08:51:20PM +0200, Mike Rapoport wrote: > > From: "Mike Rapoport (Microsoft)" > > > > high_memory defines upper bound on the directly mapped memory. > > This bound is defined by the beginning of ZONE_HI

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

producing output on qemu: [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 6.14.0-rc6-next-20250311 (tuxmake@tuxmake) (arm-linux-gnueabihf-gcc (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP @1741691801 [0.00] CPU: ARMv7 Processor [4

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

s can be reproduced with qemu? > > https://lava.sirena.org.uk/scheduler/job/1184953 > > Turns out it's actually producing output on qemu: > > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Linux version 6.14.0-rc6-next-20250311 (tuxmake@tuxmake) > (arm-l

Re: [PATCH 10/13] arch, mm: set high_memory in free_area_init()

255893718268e1ab852fb52f70c613d109b99] Add linux-next specific files for 20250311 # good: [97654dc13f139ea726042711a4943f424c5d5b83] Merge branch 'for-linux-next-fixes' of https://gitlab.freedesktop.org/drm/misc/kernel.git # good: [5cd09a324588b4554c9ed89cef34fa502a097d16]