From: Muchun Song <songmuchun@bytedance.com>
To: will@kernel.org, akpm@linux-foundation.org, david@redhat.com,
bodeddub@amazon.com, osalvador@suse.de, mike.kravetz@oracle.com,
rientjes@google.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
duanxiongchun@bytedance.com,
Muchun Song <songmuchun@bytedance.com>
Subject: [PATCH 2/3] mm: hugetlb: introduce arch_free_vmemmap_page
Date: Wed, 10 Mar 2021 15:15:34 +0800 [thread overview]
Message-ID: <20210310071535.35245-3-songmuchun@bytedance.com> (raw)
In-Reply-To: <20210310071535.35245-1-songmuchun@bytedance.com>
We register bootmem info for vmemmap pages when boot on x86-64, so
the vmemmap pages must be freed by using free_bootmem_page(). But
on some other architectures, we do not need bootmem info. In this
case, free_reserved_page() is enough to free vmemmap pages.
Currently, only x86-64 need free_bootmem_page(), so introduce a
default arch_free_vmemmap_page() which use free_reserved_page()
to free vmemmap pages directly. On x86-64, we can implement
arch_free_vmemmap_page() to override the default behavior.
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
---
arch/x86/mm/init_64.c | 5 +++++
mm/sparse-vmemmap.c | 9 +++++++--
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 39f88c5faadc..732609dad0ec 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -1575,6 +1575,11 @@ int __meminit vmemmap_populate(unsigned long start, unsigned long end, int node,
}
#ifdef CONFIG_HAVE_BOOTMEM_INFO_NODE
+void arch_free_vmemmap_page(struct page *page)
+{
+ free_bootmem_page(page);
+}
+
void register_page_bootmem_memmap(unsigned long section_nr,
struct page *start_page, unsigned long nr_pages)
{
diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c
index 60fc6cd6cd23..76f7b52820e3 100644
--- a/mm/sparse-vmemmap.c
+++ b/mm/sparse-vmemmap.c
@@ -156,16 +156,21 @@ static void vmemmap_remap_range(unsigned long start, unsigned long end,
flush_tlb_kernel_range(start + PAGE_SIZE, end);
}
+void __weak arch_free_vmemmap_page(struct page *page)
+{
+ free_reserved_page(page);
+}
+
/*
* Free a vmemmap page. A vmemmap page can be allocated from the memblock
* allocator or buddy allocator. If the PG_reserved flag is set, it means
* that it allocated from the memblock allocator, just free it via the
- * free_bootmem_page(). Otherwise, use __free_page().
+ * arch_free_vmemmap_page(). Otherwise, use __free_page().
*/
static inline void free_vmemmap_page(struct page *page)
{
if (PageReserved(page))
- free_bootmem_page(page);
+ arch_free_vmemmap_page(page);
else
__free_page(page);
}
--
2.11.0
next prev parent reply other threads:[~2021-03-10 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 7:15 [PATCH 0/3] Add support for free vmemmap pages of HugeTLB for arm64 Muchun Song
2021-03-10 7:15 ` [PATCH 1/3] mm: bootmem_info: mark register_page_bootmem_info_section __init Muchun Song
2021-03-10 7:15 ` Muchun Song [this message]
2021-03-10 12:16 ` [PATCH 2/3] mm: hugetlb: introduce arch_free_vmemmap_page kernel test robot
2021-03-11 0:15 ` kernel test robot
2021-03-10 7:15 ` [PATCH 3/3] arm64: mm: hugetlb: add support for free vmemmap pages of HugeTLB Muchun Song
2021-03-11 0:47 ` kernel test robot
2021-03-11 4:12 ` [PATCH 0/3] Add support for free vmemmap pages of HugeTLB for arm64 Chen Huang
2021-03-11 5:00 ` Bodeddula, Balasubramaniam
2021-03-11 6:01 ` Chen Huang
2021-03-11 18:00 ` Bodeddula, Balasubramaniam
2021-03-12 2:52 ` Chen Huang
2021-03-12 17:38 ` Mike Kravetz
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=20210310071535.35245-3-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=bodeddub@amazon.com \
--cc=david@redhat.com \
--cc=duanxiongchun@bytedance.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).