From: wang lian <lianux.mm@gmail.com>
To: ziy@nvidia.com
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
baohua@kernel.org, baolin.wang@linux.alibaba.com,
david@redhat.com, dev.jain@arm.com, lianux.mm@gmail.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com, mhocko@suse.com,
npache@redhat.com, richard.weiyang@gmail.com, rppt@kernel.org,
ryan.roberts@arm.com, shuah@kernel.org, surenb@google.com,
vbabka@suse.cz
Subject: Re: [PATCH v2 1/3] mm/huge_memory: add new_order and offset to split_huge_pages*() pr_debug.
Date: Mon, 11 Aug 2025 09:32:13 +0800 [thread overview]
Message-ID: <20250811013213.54499-1-lianux.mm@gmail.com> (raw)
In-Reply-To: <20250808190144.797076-2-ziy@nvidia.com>
> They are useful information for debugging split huge page tests.
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> ---
Yes. LGTM.
Reviewed-by: wang lian <lianux.mm@gmail.com>
Best regards,
wang lian
next prev parent reply other threads:[~2025-08-11 1:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 19:01 [PATCH v2 0/3] Better split_huge_page_test result check Zi Yan
2025-08-08 19:01 ` [PATCH v2 1/3] mm/huge_memory: add new_order and offset to split_huge_pages*() pr_debug Zi Yan
2025-08-09 18:45 ` Wei Yang
2025-08-10 16:55 ` Donet Tom
2025-08-11 1:32 ` wang lian [this message]
2025-08-11 6:45 ` Baolin Wang
2025-08-11 6:58 ` Barry Song
2025-08-11 7:55 ` David Hildenbrand
2025-08-08 19:01 ` [PATCH v2 2/3] selftests/mm: add check_folio_orders() helper Zi Yan
2025-08-09 20:18 ` Wei Yang
2025-08-11 18:39 ` Zi Yan
2025-08-11 21:28 ` Wei Yang
2025-08-10 16:49 ` Donet Tom
2025-08-11 18:40 ` Zi Yan
2025-08-11 7:52 ` Baolin Wang
2025-08-11 18:41 ` Zi Yan
2025-08-08 19:01 ` [PATCH v2 3/3] selftests/mm: check after-split folio orders in split_huge_page_test Zi Yan
2025-08-10 16:53 ` Donet Tom
2025-08-11 18:20 ` Zi Yan
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=20250811013213.54499-1-lianux.mm@gmail.com \
--to=lianux.mm@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).