From: Catalin Marinas <catalin.marinas@arm.com>
To: anshuman.khandual@arm.com, david@redhat.com, will@kernel.org,
ryan.roberts@arm.com, mark.rutland@arm.com, ardb@kernel.org,
yangyicong@hisilicon.com, joey.gouly@arm.com,
quic_cgoldswo@quicinc.com, quic_sudaraja@quicinc.com,
akpm@linux-foundation.org,
Zhenhua Huang <quic_zhenhuah@quicinc.com>
Cc: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, quic_tingweiz@quicinc.com
Subject: Re: [PATCH] arm64: mm: Correct the update of max_pfn
Date: Fri, 28 Mar 2025 20:08:21 +0000 [thread overview]
Message-ID: <174319246799.4193737.10993641019327469518.b4-ty@arm.com> (raw)
In-Reply-To: <20250321070019.1271859-1-quic_zhenhuah@quicinc.com>
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@genericarmv8:~# 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
prev parent reply other threads:[~2025-03-28 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 7:00 Zhenhua Huang
2025-03-21 16:40 ` Catalin Marinas
2025-03-22 5:18 ` David Hildenbrand
2025-03-24 4:19 ` Anshuman Khandual
2025-03-25 19:22 ` David Hildenbrand
2025-03-28 20:08 ` Catalin Marinas [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=174319246799.4193737.10993641019327469518.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=david@redhat.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=quic_cgoldswo@quicinc.com \
--cc=quic_sudaraja@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=ryan.roberts@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
/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