Hi Alexandre,
On Mon, May 19, 2025 at 05:54:23PM +0200, Alexandre Ghiti wrote:
> Hi Mike,
>
> I encountered the same error as Pratyush and the above diff fixes it: do you
> plan on sending this fix for 6.15?
>
> If so, you can add:
>
> Tested-by: Alexandre Ghiti
Thanks!
Here's the patch:
http
Hi Mike,
On 5/16/25 19:01, Mike Rapoport wrote:
Hi Pratyush,
On Fri, May 16, 2025 at 05:28:17PM +0200, Pratyush Yadav wrote:
Hi Mike, Andrew,
On Thu, Mar 13 2025, Mike Rapoport wrote:
From: "Mike Rapoport (Microsoft)"
high_memory defines upper bound on the directly mapped memory.
This bou
Hi Pratyush,
On Fri, May 16, 2025 at 05:28:17PM +0200, Pratyush Yadav wrote:
> Hi Mike, Andrew,
>
> On Thu, Mar 13 2025, Mike Rapoport wrote:
>
> > From: "Mike Rapoport (Microsoft)"
> >
> > high_memory defines upper bound on the directly mapped memory.
> > This bound is defined by the beginning
Hi Mike, Andrew,
On Thu, Mar 13 2025, 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.
>
> All t
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
