[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <eb4d6674-494a-4a84-bade-481b0c89eb93@quicinc.com>
Date: Thu, 28 Nov 2024 15:26:43 +0800
From: Zhenhua Huang <quic_zhenhuah@...cinc.com>
To: <catalin.marinas@....com>, <will@...nel.org>, <ardb@...nel.org>,
<ryan.roberts@....com>, <mark.rutland@....com>, <joey.gouly@....com>,
<dave.hansen@...ux.intel.com>, <akpm@...ux-foundation.org>,
<chenfeiyang@...ngson.cn>, <chenhuacai@...nel.org>
CC: <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] Fix subsection vmemmap_populate logic
On 2024/11/21 15:12, Zhenhua Huang wrote:
> To perform memory hotplug operations, the memmap (aka struct page) will be
> updated. For arm64 with 4K page size, the typical granularity is 128M,
> which corresponds to a 2M memmap buffer.
> Commit 2045a3b8911b ("mm/sparse-vmemmap: generalise vmemmap_populate_hugepages()")
> optimizes this 2M buffer to be mapped with PMD huge pages. However,
> commit ba72b4c8cf60 ("mm/sparsemem: support sub-section hotplug")
> which supports 2M subsection hotplug granularity, causes other issues
> (refer to the change log of patch #1). The logic is adjusted to populate
> with huge pages only if the hotplug address/size is section-aligned.
Could any expert please help review ?
>
> Zhenhua Huang (2):
> arm64: mm: vmemmap populate to page level if not section aligned
> arm64: mm: implement vmemmap_check_pmd for arm64
>
> arch/arm64/mm/mmu.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
Powered by blists - more mailing lists