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-mm@kvack.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Zhenhua Huang <quic_zhenhuah@quicinc.com>
Subject: [PATCH v2 1/2] arm64: mm: vmemmap populate to page level if not section aligned
Date: Mon, 9 Dec 2024 17:42:26 +0800 [thread overview]
Message-ID: <20241209094227.1529977-2-quic_zhenhuah@quicinc.com> (raw)
In-Reply-To: <20241209094227.1529977-1-quic_zhenhuah@quicinc.com>
Commit c1cc1552616d ("arm64: MMU initialisation")
optimizes the vmemmap to populate at the PMD section level. However, if
start or end is not aligned to a section boundary, such as when a
subsection is hot added, populating the entire section is wasteful. For
instance, if only one subsection hot-added, the entire section's struct
page metadata will still be populated.In such cases, it is more effective
to populate at page granularity.
This change also addresses mismatch issues during vmemmap_free(): When
pmd_sect() is true, the entire PMD section is cleared, even if there is
other effective subsection. For example, pagemap1 and pagemap2 are part
of a single PMD entry and they are hot-added sequentially. Then pagemap1
is removed, vmemmap_free() will clear the entire PMD entry, freeing the
struct page metadata for the whole section, even though pagemap2 is still
active.
Fixes: c1cc1552616d ("arm64: MMU initialisation")
Signed-off-by: Zhenhua Huang <quic_zhenhuah@quicinc.com>
---
arch/arm64/mm/mmu.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c
index e2739b69e11b..fd59ee44960e 100644
--- a/arch/arm64/mm/mmu.c
+++ b/arch/arm64/mm/mmu.c
@@ -1177,7 +1177,9 @@ int __meminit vmemmap_populate(unsigned long start, unsigned long end, int node,
{
WARN_ON((start < VMEMMAP_START) || (end > VMEMMAP_END));
- if (!IS_ENABLED(CONFIG_ARM64_4K_PAGES))
+ if (!IS_ENABLED(CONFIG_ARM64_4K_PAGES) ||
+ !IS_ALIGNED(page_to_pfn((struct page *)start), PAGES_PER_SECTION) ||
+ !IS_ALIGNED(page_to_pfn((struct page *)end), PAGES_PER_SECTION))
return vmemmap_populate_basepages(start, end, node, altmap);
else
return vmemmap_populate_hugepages(start, end, node, altmap);
--
2.25.1
next prev parent reply other threads:[~2024-12-09 9:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 9:42 [PATCH v2 0/2] Fix subsection vmemmap_populate logic Zhenhua Huang
2024-12-09 9:42 ` Zhenhua Huang [this message]
2024-12-20 18:30 ` [PATCH v2 1/2] arm64: mm: vmemmap populate to page level if not section aligned Catalin Marinas
2024-12-24 9:32 ` Zhenhua Huang
2024-12-24 14:09 ` Catalin Marinas
2024-12-25 9:59 ` Zhenhua Huang
2024-12-27 7:49 ` Anshuman Khandual
2024-12-30 7:48 ` Zhenhua Huang
2024-12-31 5:52 ` Zhenhua Huang
2025-01-02 3:16 ` Anshuman Khandual
2025-01-02 9:07 ` Zhenhua Huang
2025-01-02 3:51 ` Anshuman Khandual
2025-01-02 9:13 ` Zhenhua Huang
2025-01-02 18:58 ` Catalin Marinas
2025-01-03 2:01 ` Zhenhua Huang
2024-12-09 9:42 ` [PATCH v2 2/2] arm64: mm: implement vmemmap_check_pmd for arm64 Zhenhua Huang
2024-12-20 18:35 ` Catalin Marinas
2024-12-27 2:57 ` Anshuman Khandual
2024-12-30 7:48 ` Zhenhua Huang
2024-12-31 6:59 ` Anshuman Khandual
2024-12-31 7:18 ` Zhenhua Huang
2025-01-02 18:12 ` Catalin Marinas
2025-01-03 2:43 ` Zhenhua Huang
2025-01-03 17:58 ` Catalin Marinas
2024-12-17 1:47 ` [PATCH v2 0/2] Fix subsection vmemmap_populate logic 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=20241209094227.1529977-2-quic_zhenhuah@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=linux-mm@kvack.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