From: Zhenhua Huang <quic_zhenhuah@quicinc.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>, <ardb@kernel.org>,
<ryan.roberts@arm.com>, <mark.rutland@arm.com>,
<joey.gouly@arm.com>, <dave.hansen@linux.intel.com>,
<akpm@linux-foundation.org>, <chenfeiyang@loongson.cn>,
<chenhuacai@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Fix subsection vmemmap_populate logic
Date: Thu, 28 Nov 2024 15:26:43 +0800 [thread overview]
Message-ID: <eb4d6674-494a-4a84-bade-481b0c89eb93@quicinc.com> (raw)
In-Reply-To: <20241121071256.487220-1-quic_zhenhuah@quicinc.com>
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(-)
>
next prev parent reply other threads:[~2024-11-28 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 7:12 Zhenhua Huang
2024-11-21 7:12 ` [PATCH 1/2] arm64: mm: vmemmap populate to page level if not section aligned Zhenhua Huang
2024-12-06 17:13 ` Catalin Marinas
2024-12-09 6:04 ` Zhenhua Huang
2024-11-21 7:12 ` [PATCH 2/2] arm64: mm: implement vmemmap_check_pmd for arm64 Zhenhua Huang
2024-11-28 7:26 ` Zhenhua Huang [this message]
2024-12-06 9:13 ` [PATCH 0/2] Fix subsection vmemmap_populate logic Zhenhua Huang
2024-12-07 6:14 ` Andrew Morton
2024-12-09 6:04 ` Zhenhua Huang
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=eb4d6674-494a-4a84-bade-481b0c89eb93@quicinc.com \
--to=quic_zhenhuah@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®