[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174319246799.4193737.10993641019327469518.b4-ty@arm.com>
Date: Fri, 28 Mar 2025 20:08:21 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: anshuman.khandual@....com,
david@...hat.com,
will@...nel.org,
ryan.roberts@....com,
mark.rutland@....com,
ardb@...nel.org,
yangyicong@...ilicon.com,
joey.gouly@....com,
quic_cgoldswo@...cinc.com,
quic_sudaraja@...cinc.com,
akpm@...ux-foundation.org,
Zhenhua Huang <quic_zhenhuah@...cinc.com>
Cc: linux-mm@...ck.org,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
quic_tingweiz@...cinc.com
Subject: Re: [PATCH] arm64: mm: Correct the update of max_pfn
On Fri, 21 Mar 2025 15:00:19 +0800, Zhenhua Huang wrote:
> Hotplugged memory can be smaller than the original memory. For example,
> on my target:
>
> root@...ericarmv8:~# cat /sys/kernel/debug/memblock/memory
> 0: 0x0000000064005000..0x0000000064023fff 0 NOMAP
> 1: 0x0000000064400000..0x00000000647fffff 0 NOMAP
> 2: 0x0000000068000000..0x000000006fffffff 0 DRV_MNG
> 3: 0x0000000088800000..0x0000000094ffefff 0 NONE
> 4: 0x0000000094fff000..0x0000000094ffffff 0 NOMAP
> max_pfn will affect read_page_owner. Therefore, it should first compare and
> then select the larger value for max_pfn.
>
> [...]
Applied to arm64 (for-next/core), thanks!
[1/1] arm64: mm: Correct the update of max_pfn
https://git.kernel.org/arm64/c/89f43e1ce6f6
--
Catalin
Powered by blists - more mailing lists