mm-memory_hotplug-move-debug_pagealloc_map_pages-into-online_pages_range.patch removed from -mm tree
The quilt patch titled
Subject: mm/memory_hotplug: move debug_pagealloc_map_pages() into online_pages_range()
has been removed from the -mm tree. Its filename was
mm-memory_hotplug-move-debug_pagealloc_map_pages-into-online_pages_range.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: David Hildenbrand <[email protected]>
Subject: mm/memory_hotplug: move debug_pagealloc_map_pages() into online_pages_range()
Date: Tue, 3 Dec 2024 11:20:50 +0100
In the near future, we want to have a single way to handover PageOffline pages to the buddy, whereby they could have:
(a) Never been exposed to the buddy before: kept PageOffline when onlining the memory block.
(b) Been allocated from the buddy, for example using alloc_contig_range() to then be set PageOffline,
Let's start by making generic_online_page()->__free_pages_core() less special compared to ordinary page freeing (e.g., free_contig_range()), and perform the debug_pagealloc_map_pages() call unconditionally, even when the online callback might decide to keep the pages offline.
All pages are already initialized with PageOffline, so nobody touches them either way.
---
mm/memory_hotplug.c | 10 +++++++++- mm/page_alloc.c | 6 ------ 2 files changed, 9 insertions(+), 7 deletions(-)
mm/memory_hotplug.c renamed from mm/memory_hotplug.c~mm-memory_hotplug-move-debug_pagealloc_map_pages-into-online_pages_range +9 -1
@@ -650,6 +650,7 @@ static void online_pages_range(unsigned* this and the first chunk to online will be pageblock_nr_pages. */ for (pfn = start_pfn; pfn < end_pfn;) { +struct page *page =pfn_to_page (pfn);int order;/*
@@ -664,7 +665,14 @@ static void online_pages_range(unsignedelse order =MAX_PAGE_ORDER ; - (*online_page_callback)(pfn_to_page (pfn), order); +/* +* Exposing the page to the buddy by freeing can cause +* issues with debug_pagealloc enabled: some archs don't +* like double-unmappings. So treat them like any pages that +* were allocated from the buddy. +*/ +debug_pagealloc_map_pages (page,1 << order); + (*online_page_callback)(page, order); pfn += (1UL << order); }
mm/page_alloc.c renamed from mm/page_alloc.c~mm-memory_hotplug-move-debug_pagealloc_map_pages-into-online_pages_range +0 -6
@@ -1295,12 +1295,6 @@ void __meminit __free_pages_core(structset_page_count (p,0 ); } -/* -* Freeing the page with debug_pagealloc enabled will try to -* unmap it; some archs don't like double-unmappings, so -* map it first. -*/ -debug_pagealloc_map_pages (page, nr_pages);adjust_managed_page_count (page, nr_pages); }else {for (loop =0 ; loop < nr_pages; loop++, p++) {
_
Patches currently in -mm which might be from [email protected] are
mm-huge_memory-convert-has_hwpoisoned-into-a-pure-folio-flag.patch mm-hugetlb-rename-isolate_hugetlb-to-folio_isolate_hugetlb.patch mm-migrate-dont-call-folio_putback_active_hugetlb-on-dst-hugetlb-folio.patch mm-hugetlb-rename-folio_putback_active_hugetlb-to-folio_putback_hugetlb.patch mm-hugetlb-cgroup-convert-hugetlb_cgroup_css_offline-to-work-on-folios.patch mm-hugetlb-use-folio-lru-int-demote_free_hugetlb_folios.patch