[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f4f6e93-ddc2-c9bb-ef47-4a40f2c3d0d7@quicinc.com>
Date: Mon, 27 Sep 2021 20:22:46 +0300
From: Georgi Djakov <quic_c_gdjako@...cinc.com>
To: Chris Goldsworthy <quic_cgoldswo@...cinc.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
CC: David Hildenbrand <david@...hat.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
Sudarshan Rajagopalan <quic_sudaraja@...cinc.com>
Subject: Re: [RFC] arm64: mm: update max_pfn after memory hotplug
On 9/24/2021 1:54 AM, Chris Goldsworthy wrote:
> From: Sudarshan Rajagopalan <quic_sudaraja@...cinc.com>
>
> After new memory blocks have been hotplugged, max_pfn and max_low_pfn
> needs updating to reflect on new PFNs being hot added to system.
>
> Signed-off-by: Sudarshan Rajagopalan <quic_sudaraja@...cinc.com>
> Signed-off-by: Chris Goldsworthy <quic_cgoldswo@...cinc.com>
Thanks for the patch, Chris!
With this patch, the data in /proc/kpageflags appears to be correct and
memory tools like procrank work again on arm64 platforms.
Tested-by: Georgi Djakov <quic_c_gdjako@...cinc.com>
Maybe we should add fixes tag, as it has been broken since the following
commit:
Fixes: abec749facff ("fs/proc/page.c: allow inspection of last section
and fix end detection")
Thanks,
Georgi
> ---
> arch/arm64/mm/mmu.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c
> index cfd9deb..fd85b51 100644
> --- a/arch/arm64/mm/mmu.c
> +++ b/arch/arm64/mm/mmu.c
> @@ -1499,6 +1499,11 @@ int arch_add_memory(int nid, u64 start, u64 size,
> if (ret)
> __remove_pgd_mapping(swapper_pg_dir,
> __phys_to_virt(start), size);
> + else {
> + max_pfn = PFN_UP(start + size);
> + max_low_pfn = max_pfn;
> + }
> +
> return ret;
> }
>
>
Powered by blists - more mailing lists