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

On Tue, Mar 11, 2025 at 10:41:28PM +0100, Geert Uytterhoeven wrote: > On Tue, 11 Mar 2025 at 22:33, Mark Brown wrote: > > [0.00] efi: UEFI not found. > > [0.00] cma: Reserved 64 MiB at 0x > > - I'd only been sampling the logs for the physical platforms, none of > > which

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

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.43.1) #1 SMP @17416918

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

Hi Mark, On Tue, 11 Mar 2025 at 22:33, Mark Brown wrote: > On Tue, Mar 11, 2025 at 11:06:56PM +0200, Mike Rapoport wrote: > > On Tue, Mar 11, 2025 at 05:51:06PM +, Mark Brown wrote: > > > This patch appears to be causing breakage on a number of 32 bit arm > > > platforms, including qemu's vir

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: > On Tue, Mar 11, 2025 at 11:06:56PM +0200, Mike Rapoport wrote: > > On Tue, Mar 11, 2025 at 05:51:06PM +, Mark Brown wrote: > > > > This patch appears to be causing breakage on a number of 32 bit arm > > > platforms, including qemu's

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

On Tue, Mar 11, 2025 at 11:06:56PM +0200, Mike Rapoport wrote: > On Tue, Mar 11, 2025 at 05:51:06PM +, Mark Brown wrote: > > This patch appears to be causing breakage on a number of 32 bit arm > > platforms, including qemu's virt-2.11,gic-version=3. Affected platforms > > die on boot with no

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()

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 a system has > high memory and by the end of memory otherwise. > > A

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

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 a system has high memory and by the end of memory otherwise. All this is known to generic memory management initialization code that can se