FAILED: patch "[PATCH] mm/page_alloc: Separate THP PCP into movable and non-movable" failed to apply to 6.1-stable tree
Subsystems (5)
[email protected]
maintainerThe patch below does not apply to the 6.1-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.1.y
git checkout FETCH_HEAD
git cherry-pick -x bf14ed81f571f8dba31cd72ab2e50fbcc877cc31
# <resolve conflicts, build, test, etc.>
git commit -s
git send-email --to '<[email protected]>' --in-reply-to '2024070129-movable-commend-1b2a@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..
Possible dependencies:
bf14ed81f571 ("mm/page_alloc: Separate THP PCP into movable and non-movable categories") 6303d1c553c8 ("mm: page_alloc: use the correct THP order for THP PCP") c1dc69e6ce65 ("mm/page_alloc: remove unneeded variable base")
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From bf14ed81f571f8dba31cd72ab2e50fbcc877cc31 Mon Sep 17 00:00:00 2001
From: yangge <[email protected]>
Date: Thu, 20 Jun 2024 08:59:50 +0800
Subject: [PATCH] mm/page_alloc: Separate THP PCP into movable and non-movable
categories
Since commit 5d0a661d808f ("mm/page_alloc: use only one PCP list for THP-sized allocations") no longer differentiates the migration type of pages in THP-sized PCP list, it's possible that non-movable allocation requests may get a CMA page from the list, in some cases, it's not acceptable.
If a large number of CMA memory are configured in system (for example, the CMA memory accounts for 50% of the system memory), starting a virtual machine with device passthrough will get stuck. During starting the virtual machine, it will call pin_user_pages_remote(..., FOLL_LONGTERM, ...) to pin memory. Normally if a page is present and in CMA area, pin_user_pages_remote() will migrate the page from CMA area to non-CMA area because of FOLL_LONGTERM flag. But if non-movable allocation requests return CMA memory, migrate_longterm_unpinnable_pages() will migrate a CMA page to another CMA page, which will fail to pass the check in check_and_migrate_movable_pages() and cause migration endless.
Call trace:
pin_user_pages_remote
--__gup_longterm_locked // endless loops in this function ----_get_user_pages_locked ----check_and_migrate_movable_pages ------migrate_longterm_unpinnable_pages --------alloc_migration_target
This problem will also have a negative impact on CMA itself. For example, when CMA is borrowed by THP, and we need to reclaim it through cma_alloc() or dma_alloc_coherent(), we must move those pages out to ensure CMA's users can retrieve that contigous memory. Currently, CMA's memory is occupied by non-movable pages, meaning we can't relocate them. As a result, cma_alloc() is more likely to fail.
To fix the problem above, we add one PCP list for THP, which will not introduce a new cacheline for struct per_cpu_pages. THP will have 2 PCP lists, one PCP list is used by MOVABLE allocation, and the other PCP list is used by UNMOVABLE allocation. MOVABLE allocation contains GPF_MOVABLE, and UNMOVABLE allocation contains GFP_UNMOVABLE and GFP_RECLAIMABLE.
include/linux/mmzone.h +4 -5
@@ -654,13 +654,12 @@ enum zone_watermarks { };/* -* One per migratetype for each PAGE_ALLOC_COSTLY_ORDER. One additional list -* for THP which will usually be GFP_MOVABLE. Even if it is another type, -* it should not contribute to serious fragmentation causing THP allocation -* failures. +* One per migratetype for each PAGE_ALLOC_COSTLY_ORDER. Two additional lists +* are added for THP. One PCP list is used by GPF_MOVABLE, and the other PCP list +* is used by GFP_UNMOVABLE and GFP_RECLAIMABLE. */ #ifdef CONFIG_TRANSPARENT_HUGEPAGE -#define NR_PCP_THP 1 +#define NR_PCP_THP 2#else #define NR_PCP_THP 0#endif
mm/page_alloc.c +7 -2
@@ -504,10 +504,15 @@ static void bad_page(struct page *page, const char *reason)static inline unsigned int order_to_pindex (int migratetype,int order) { +bool __maybe_unused movable; +#ifdef CONFIG_TRANSPARENT_HUGEPAGE if (order >PAGE_ALLOC_COSTLY_ORDER ) {VM_BUG_ON (order !=HPAGE_PMD_ORDER ); -return NR_LOWORDER_PCP_LISTS ; + + movable = migratetype ==MIGRATE_MOVABLE ; + +return NR_LOWORDER_PCP_LISTS + movable; }#else VM_BUG_ON (order >PAGE_ALLOC_COSTLY_ORDER );
@@ -521,7 +526,7 @@ static inline int pindex_to_order(unsigned int pindex)int order = pindex /MIGRATE_PCPTYPES ;#ifdef CONFIG_TRANSPARENT_HUGEPAGE -if (pindex ==NR_LOWORDER_PCP_LISTS ) +if (pindex >=NR_LOWORDER_PCP_LISTS ) order =HPAGE_PMD_ORDER ;#else VM_BUG_ON (order >PAGE_ALLOC_COSTLY_ORDER );
PATCH 1/1 mm/page_alloc: Separate THP PCP into movable and non-movable categories
From: yangge <[email protected]>
Since commit 5d0a661d808f ("mm/page_alloc: use only one PCP list for THP-sized allocations") no longer differentiates the migration type of pages in THP-sized PCP list, it's possible that non-movable allocation requests may get a CMA page from the list, in some cases, it's not acceptable.
If a large number of CMA memory are configured in system (for example, the CMA memory accounts for 50% of the system memory), starting a virtual machine with device passthrough will get stuck. During starting the virtual machine, it will call pin_user_pages_remote(..., FOLL_LONGTERM, ...) to pin memory. Normally if a page is present and in CMA area, pin_user_pages_remote() will migrate the page from CMA area to non-CMA area because of FOLL_LONGTERM flag. But if non-movable allocation requests return CMA memory, migrate_longterm_unpinnable_pages() will migrate a CMA page to another CMA page, which will fail to pass the check in check_and_migrate_movable_pages() and cause migration endless.
Call trace:
pin_user_pages_remote
--__gup_longterm_locked // endless loops in this function ----_get_user_pages_locked ----check_and_migrate_movable_pages ------migrate_longterm_unpinnable_pages --------alloc_migration_target
This problem will also have a negative impact on CMA itself. For example, when CMA is borrowed by THP, and we need to reclaim it through cma_alloc() or dma_alloc_coherent(), we must move those pages out to ensure CMA's users can retrieve that contigous memory. Currently, CMA's memory is occupied by non-movable pages, meaning we can't relocate them. As a result, cma_alloc() is more likely to fail.
To fix the problem above, we add one PCP list for THP, which will not introduce a new cacheline for struct per_cpu_pages. THP will have 2 PCP lists, one PCP list is used by MOVABLE allocation, and the other PCP list is used by UNMOVABLE allocation. MOVABLE allocation contains GPF_MOVABLE, and UNMOVABLE allocation contains GFP_UNMOVABLE and GFP_RECLAIMABLE.
--- include/linux/mmzone.h | 9 ++++----- mm/page_alloc.c | 8 ++++++-- 2 files changed, 10 insertions(+), 7 deletions(-)
include/linux/mmzone.h +4 -5
@@ -552,13 +552,12 @@ enum zone_watermarks { };/* -* One per migratetype for each PAGE_ALLOC_COSTLY_ORDER. One additional list -* for THP which will usually be GFP_MOVABLE. Even if it is another type, -* it should not contribute to serious fragmentation causing THP allocation -* failures. +* One per migratetype for each PAGE_ALLOC_COSTLY_ORDER. Two additional lists +* are added for THP. One PCP list is used by GPF_MOVABLE, and the other PCP list +* is used by GFP_UNMOVABLE and GFP_RECLAIMABLE. */ #ifdef CONFIG_TRANSPARENT_HUGEPAGE -#define NR_PCP_THP 1 +#define NR_PCP_THP 2#else #define NR_PCP_THP 0#endif
mm/page_alloc.c +6 -2
@@ -705,12 +705,16 @@ static void bad_page(struct page *page, const char *reason)static inline unsigned int order_to_pindex (int migratetype,int order) { +bool __maybe_unused movable;int base = order;#ifdef CONFIG_TRANSPARENT_HUGEPAGE if (order >PAGE_ALLOC_COSTLY_ORDER ) {VM_BUG_ON (order != pageblock_order); -return NR_LOWORDER_PCP_LISTS ; + + movable = migratetype ==MIGRATE_MOVABLE ; + +return NR_LOWORDER_PCP_LISTS + movable; }#else VM_BUG_ON (order >PAGE_ALLOC_COSTLY_ORDER );
@@ -724,7 +728,7 @@ static inline int pindex_to_order(unsigned int pindex)int order = pindex /MIGRATE_PCPTYPES ;#ifdef CONFIG_TRANSPARENT_HUGEPAGE -if (pindex ==NR_LOWORDER_PCP_LISTS ) +if (pindex >=NR_LOWORDER_PCP_LISTS ) order = pageblock_order;#else VM_BUG_ON (order >PAGE_ALLOC_COSTLY_ORDER );
Signature · 1 line
2.7.4
Re: [PATCH 6.1.y] mm/page_alloc: Separate THP PCP into movable and non-movable categories
Quoted 50 lines · On Tue, Jul 02, 2024 at 12:00:19PM +0800, [email protected] wrote:
From: yangge <[email protected]>
Since commit
5d0a661d808f("mm/page_alloc: use only one PCP list for THP-sized allocations") no longer differentiates the migration type of pages in THP-sized PCP list, it's possible that non-movable allocation requests may get a CMA page from the list, in some cases, it's not acceptable.If a large number of CMA memory are configured in system (for example, the CMA memory accounts for 50% of the system memory), starting a virtual machine with device passthrough will get stuck. During starting the virtual machine, it will call
pin_user_pages_remote(..., FOLL_LONGTERM, ...)to pin memory. Normally if a page is present and in CMA area,pin_user_pages_remote()will migrate the page from CMA area to non-CMA area because ofFOLL_LONGTERMflag. But if non-movable allocation requests return CMA memory,migrate_longterm_unpinnable_pages()will migrate a CMA page to another CMA page, which will fail to pass the check incheck_and_migrate_movable_pages()and cause migration endless.Call trace:
pin_user_pages_remote
--__gup_longterm_locked // endless loops in this function ----_get_user_pages_locked ----check_and_migrate_movable_pages ------migrate_longterm_unpinnable_pages --------alloc_migration_targetThis problem will also have a negative impact on CMA itself. For example, when CMA is borrowed by THP, and we need to reclaim it through
cma_alloc()ordma_alloc_coherent(), we must move those pages out to ensure CMA's users can retrieve that contigous memory. Currently, CMA's memory is occupied by non-movable pages, meaning we can't relocate them. As a result,cma_alloc()is more likely to fail.To fix the problem above, we add one PCP list for THP, which will not introduce a new cacheline for struct
per_cpu_pages. THP will have 2 PCP lists, one PCP list is used by MOVABLE allocation, and the other PCP list is used by UNMOVABLE allocation. MOVABLE allocation containsGPF_MOVABLE, and UNMOVABLE allocation containsGFP_UNMOVABLEandGFP_RECLAIMABLE.Fixes 5d0a661d808f ("mm/page_alloc: use only one PCP list for THP-sized allocations")Signed-off-by yangge <[email protected]>Cc Baolin Wang <[email protected]>Cc Barry Song <[email protected]>Cc Mel Gorman <[email protected]>Cc <[email protected]>Signed-off-by Andrew Morton <[email protected]>(cherry picked from commit bf14ed81f571f8dba31cd72ab2e50fbcc877cc31)Signed-off-by yangge <[email protected]>
Quoted 5 lines
--- include/linux/mmzone.h | 9 ++++----- mm/page_alloc.c | 8 ++++++-- 2 files changed, 10 insertions(+), 7 deletions(-)
All now queued up, thanks.
greg k-h