Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Kyle Hendry <kylehendrydev@gmail.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: mm: Add check for highmem before removing memory block
Date: Mon, 29 Jun 2026 19:13:46 +0200	[thread overview]
Message-ID: <akKnyiuiWVZRZjZU@alpha.franken.de> (raw)
In-Reply-To: <20260621184702.17302-1-kylehendrydev@gmail.com>

On Sun, Jun 21, 2026 at 11:47:02AM -0700, Kyle Hendry wrote:
> If a device has less physical memory than the highmem threshold
> bootmem_init() doesn't set highstart_pfn. This results in highmem_init()
> wrongly disabling the entire memory range if the cpu doesn't support
> highmem. Add a check that highstart_pfn is non zero before removing the
> highmem block.
> 
> Signed-off-by: Kyle Hendry <kylehendrydev@gmail.com>
> ---
>  arch/mips/mm/init.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/mips/mm/init.c b/arch/mips/mm/init.c
> index 1c07ca84ee21..352718e43f69 100644
> --- a/arch/mips/mm/init.c
> +++ b/arch/mips/mm/init.c
> @@ -426,10 +426,11 @@ static inline void __init highmem_init(void)
>  	unsigned long tmp;
>  
>  	/*
> -	 * If CPU cannot support HIGHMEM discard the memory above highstart_pfn
> +	 * If CPU cannot support HIGHMEM discard any memory above highstart_pfn
>  	 */
>  	if (cpu_has_dc_aliases) {
> -		memblock_remove(PFN_PHYS(highstart_pfn), -1);
> +		if (highstart_pfn)
> +			memblock_remove(PFN_PHYS(highstart_pfn), -1);
>  		return;
>  	}
>  
> -- 
> 2.43.0

Applied to mips-fixes with

Fixes: f171b55f1441 ("mips: fix HIGHMEM initialization")

added.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2026-06-29 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-21 18:47 [PATCH] MIPS: mm: Add check for highmem before removing memory block Kyle Hendry
2026-06-29 17:13 ` Thomas Bogendoerfer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=akKnyiuiWVZRZjZU@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=kylehendrydev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox