[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <163293186685.928897.8618689831730989496.b4-ty@kernel.org>
Date: Wed, 29 Sep 2021 18:48:27 +0100
From: Will Deacon <will@...nel.org>
To: Chris Goldsworthy <quic_cgoldswo@...cinc.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: catalin.marinas@....com, kernel-team@...roid.com,
Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mm@...ck.org,
Georgi Djakov <quic_c_gdjako@...cinc.com>,
Sudarshan Rajagopalan <quic_sudaraja@...cinc.com>,
David Hildenbrand <david@...hat.com>
Subject: Re: arm64: mm: update max_pfn after memory hotplug
On Tue, 28 Sep 2021 11:51:48 -0700, Chris Goldsworthy wrote:
> Follow up of RFC patch:
>
> https://lore.kernel.org/linux-mm/a3bf84c4-8f35-f273-145c-55928a06f332@quicinc.com/T/#m219937b1acdd40318bbe90ab39f187804775eb74
>
> On arm64 we set max_pfn at boot in arch/arm64/mm/init.c. If you
> hotplug in memory after booting up, max_pfn is not updated. This
> breaks diagnostic functions executed from user space like
> read_page_owner():
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64: mm: update max_pfn after memory hotplug
https://git.kernel.org/arm64/c/8fac67ca236b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists