From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Zi Yan <ziy@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Muchun Song <muchun.song@linux.dev>, <linux-mm@kvack.org>,
<sidhartha.kumar@oracle.com>, <jane.chu@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@kernel.org>
Subject: Re: [PATCH v4 2/6] mm: page_alloc: add __split_page()
Date: Wed, 17 Dec 2025 15:01:33 +0800 [thread overview]
Message-ID: <2b19e44a-2562-4ea5-b52c-a216f565d734@huawei.com> (raw)
In-Reply-To: <130003EA-0DFF-4C32-ADF3-DDB800494264@nvidia.com>
On 2025/12/17 0:21, Zi Yan wrote:
> On 16 Dec 2025, at 6:48, Kefeng Wang wrote:
>
>> Factor out the splitting of non-compound page from make_alloc_exact()
>> and split_page() into a new helper function __split_page().
>>
>> While at it, convert the VM_BUG_ON_PAGE() into a VM_WARN_ON_PAGE().
>>
>> Acked-by: David Hildenbrand <david@redhat.com>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> include/linux/mmdebug.h | 10 ++++++++++
>> mm/page_alloc.c | 19 ++++++++++++-------
>> 2 files changed, 22 insertions(+), 7 deletions(-)
>>
>> diff --git a/include/linux/mmdebug.h b/include/linux/mmdebug.h
>> index 14a45979cccc..ab60ffba08f5 100644
>> --- a/include/linux/mmdebug.h
>> +++ b/include/linux/mmdebug.h
>> @@ -47,6 +47,15 @@ void vma_iter_dump_tree(const struct vma_iterator *vmi);
>> BUG(); \
>> } \
>> } while (0)
>> +#define VM_WARN_ON_PAGE(cond, page) ({ \
>> + int __ret_warn = !!(cond); \
>> + \
>> + if (unlikely(__ret_warn)) { \
>> + dump_page(page, "VM_WARN_ON_PAGE(" __stringify(cond)")");\
>> + WARN_ON(1); \
>> + } \
>> + unlikely(__ret_warn); \
>> +})
>> #define VM_WARN_ON_ONCE_PAGE(cond, page) ({ \
>> static bool __section(".data..once") __warned; \
>> int __ret_warn_once = !!(cond); \
>> @@ -122,6 +131,7 @@ void vma_iter_dump_tree(const struct vma_iterator *vmi);
>> #define VM_BUG_ON_MM(cond, mm) VM_BUG_ON(cond)
>> #define VM_WARN_ON(cond) BUILD_BUG_ON_INVALID(cond)
>> #define VM_WARN_ON_ONCE(cond) BUILD_BUG_ON_INVALID(cond)
>> +#define VM_WARN_ON_PAGE(cond, page) BUILD_BUG_ON_INVALID(cond)
>> #define VM_WARN_ON_ONCE_PAGE(cond, page) BUILD_BUG_ON_INVALID(cond)
>> #define VM_WARN_ON_FOLIO(cond, folio) BUILD_BUG_ON_INVALID(cond)
>> #define VM_WARN_ON_ONCE_FOLIO(cond, folio) BUILD_BUG_ON_INVALID(cond)
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index da32397b4313..aa30d4436296 100644
>> --- a/mm/page_alloc.c
>> +++ b/mm/page_alloc.c
>> @@ -3077,6 +3077,15 @@ void free_unref_folios(struct folio_batch *folios)
>> folio_batch_reinit(folios);
>> }
>>
>> +static void __split_page(struct page *page, unsigned int order)
>> +{
>> + VM_WARN_ON_PAGE(PageCompound(page), page);
>> +
>> + split_page_owner(page, order, 0);
>> + pgalloc_tag_split(page_folio(page), order, 0);
>> + split_page_memcg(page, order);
>> +}
>> +
>> /*
>> * split_page takes a non-compound higher-order page, and splits it into
>> * n (1<<order) sub-pages: page[0..n]
>> @@ -3089,14 +3098,12 @@ void split_page(struct page *page, unsigned int order)
>> {
>> int i;
>>
>> - VM_BUG_ON_PAGE(PageCompound(page), page);
>> VM_BUG_ON_PAGE(!page_count(page), page);
>
> Could this be converted to VM_WARN_ON_PAGE() as well?
Yep, will change it too.
Thanks.
>
> Otherwise, LGTM. Reviewed-by: Zi Yan <ziy@nvidia.com>
>
> Best Regards,
> Yan, Zi
>
next prev parent reply other threads:[~2025-12-17 7:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 11:48 [PATCH v4 RESEND 0/6] mm: hugetlb: allocate frozen gigantic folio Kefeng Wang
2025-12-16 11:48 ` [PATCH v4 1/6] mm: debug_vm_pgtable: add debug_vm_pgtable_free_huge_page() Kefeng Wang
2025-12-16 16:08 ` Zi Yan
2025-12-17 2:40 ` Muchun Song
2025-12-16 11:48 ` [PATCH v4 2/6] mm: page_alloc: add __split_page() Kefeng Wang
2025-12-16 16:21 ` Zi Yan
2025-12-17 7:01 ` Kefeng Wang [this message]
2025-12-17 2:45 ` Muchun Song
2025-12-16 11:48 ` [PATCH v4 3/6] mm: cma: add __cma_release() Kefeng Wang
2025-12-16 16:39 ` Zi Yan
2025-12-17 2:46 ` Muchun Song
2025-12-16 11:48 ` [PATCH v4 4/6] mm: page_alloc: add alloc_contig_frozen_{range,pages}() Kefeng Wang
2025-12-16 17:20 ` Zi Yan
2025-12-17 7:17 ` Kefeng Wang
2025-12-17 19:20 ` Zi Yan
2025-12-18 12:00 ` Kefeng Wang
2025-12-16 11:48 ` [PATCH v4 5/6] mm: cma: add cma_alloc_frozen{_compound}() Kefeng Wang
2025-12-16 18:40 ` Zi Yan
2025-12-17 8:02 ` Kefeng Wang
2025-12-17 19:38 ` Zi Yan
2025-12-18 12:54 ` Kefeng Wang
2025-12-18 15:52 ` Zi Yan
2025-12-19 4:09 ` Kefeng Wang
2025-12-22 2:30 ` Zi Yan
2025-12-22 13:03 ` Kefeng Wang
2025-12-20 14:34 ` kernel test robot
2025-12-22 1:46 ` Kefeng Wang
2025-12-16 11:48 ` [PATCH v4 6/6] mm: hugetlb: allocate frozen pages in alloc_gigantic_folio() Kefeng Wang
2025-12-16 18:44 ` Zi Yan
2025-12-17 8:09 ` Kefeng Wang
2025-12-17 19:40 ` Zi Yan
2025-12-18 12:56 ` Kefeng Wang
-- strict thread matches above, loose matches on Subject: below --
2025-10-23 11:59 [PATCH v4 0/6] mm: hugetlb: allocate frozen gigantic folio Kefeng Wang
2025-10-23 11:59 ` [PATCH v4 2/6] mm: page_alloc: add __split_page() Kefeng Wang
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=2b19e44a-2562-4ea5-b52c-a216f565d734@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=jane.chu@oracle.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=sidhartha.kumar@oracle.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ziy@nvidia.com \
/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