From: Zi Yan <ziy@nvidia.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: wang lian <lianux.mm@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 3/4] selftests/mm: reimplement is_backed_by_thp() with more precise check
Date: Wed, 13 Aug 2025 17:58:56 -0400 [thread overview]
Message-ID: <47433AB7-58A4-4791-9C40-431D8573E26D@nvidia.com> (raw)
In-Reply-To: <20250813214112.tarr5rbamtc6cmie@master>
On 13 Aug 2025, at 17:41, Wei Yang wrote:
> On Tue, Aug 12, 2025 at 11:55:11AM -0400, Zi Yan wrote:
>> and rename it to is_backed_by_folio().
>>
>> is_backed_by_folio() checks if the given vaddr is backed a folio with
>> a given order. It does so by:
>> 1. getting the pfn of the vaddr;
>> 2. checking kpageflags of the pfn;
>>
>> if order is greater than 0:
>> 3. checking kpageflags of the head pfn;
>> 4. checking kpageflags of all tail pfns.
>>
>> pmd_order is added to split_huge_page_test.c and replaces max_order.
>>
>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>> ---
>> .../selftests/mm/split_huge_page_test.c | 67 +++++++++++++------
>> tools/testing/selftests/mm/vm_util.c | 2 +-
>> tools/testing/selftests/mm/vm_util.h | 1 +
>> 3 files changed, 48 insertions(+), 22 deletions(-)
>>
>> diff --git a/tools/testing/selftests/mm/split_huge_page_test.c b/tools/testing/selftests/mm/split_huge_page_test.c
>> index 63ac82f0b9e0..3aaf783f339f 100644
>> --- a/tools/testing/selftests/mm/split_huge_page_test.c
>> +++ b/tools/testing/selftests/mm/split_huge_page_test.c
>> @@ -25,6 +25,7 @@
>> uint64_t pagesize;
>> unsigned int pageshift;
>> uint64_t pmd_pagesize;
>> +unsigned int pmd_order;
>>
>> #define SPLIT_DEBUGFS "/sys/kernel/debug/split_huge_pages"
>> #define SMAP_PATH "/proc/self/smaps"
>> @@ -36,23 +37,48 @@ uint64_t pmd_pagesize;
>>
>> #define GET_ORDER(nr_pages) (31 - __builtin_clz(nr_pages))
>>
>> -int is_backed_by_thp(char *vaddr, int pagemap_file, int kpageflags_file)
>> +int is_backed_by_folio(char *vaddr, int order, int pagemap_fd, int kpageflags_fd)
>> {
>> - uint64_t paddr;
>> - uint64_t page_flags;
>> + unsigned long pfn_head;
>> + uint64_t pfn_flags;
>> + unsigned long pfn;
>> + unsigned long i;
>>
>> - if (pagemap_file) {
>> - pread(pagemap_file, &paddr, sizeof(paddr),
>> - ((long)vaddr >> pageshift) * sizeof(paddr));
>> + if (!pagemap_fd || !kpageflags_fd)
>> + return 0;
>
> The same in patch 2.
Will fix it.
>
>>
>> - if (kpageflags_file) {
>> - pread(kpageflags_file, &page_flags, sizeof(page_flags),
>> - PAGEMAP_PFN(paddr) * sizeof(page_flags));
>> + pfn = pagemap_get_pfn(pagemap_fd, vaddr);
>>
>> - return !!(page_flags & KPF_THP);
>> - }
>> + if (pfn == -1UL)
>> + return 0;
>> +
>> + if (get_pfn_flags(pfn, kpageflags_fd, &pfn_flags))
>> + return 0;
>> +
>> + if (!order) {
>> + if (pfn_flags & (KPF_THP | KPF_COMPOUND_HEAD | KPF_COMPOUND_TAIL))
>> + return 0;
>> + return 1;
>> }
>> - return 0;
>> +
>> + if (!(pfn_flags & KPF_THP))
>> + return 0;
>> +
>> + pfn_head = pfn & ~((1 << order) - 1);
>> +
>> + if (get_pfn_flags(pfn_head, kpageflags_fd, &pfn_flags))
>> + return 0;
>> +
>> + if (!(pfn_flags & (KPF_THP | KPF_COMPOUND_HEAD)))
>> + return 0;
>> +
>> + for (i = 1; i < (1UL << order) - 1; i++) {
>
> Do we miss the last tail?
Yes, will fix it.
>
>> + if (get_pfn_flags(pfn_head + i, kpageflags_fd, &pfn_flags))
>> + return 0;
>> + if (!(pfn_flags & (KPF_THP | KPF_COMPOUND_TAIL)))
>> + return 0;
>> + }
>
> If this folio is larger than order, would it still return 1?
Yes, but it should be good enough for current use. Will add a comment about it.
Thanks for the review.
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-08-13 21:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 15:55 [PATCH v3 0/4] Better split_huge_page_test result check Zi Yan
2025-08-12 15:55 ` [PATCH v3 1/4] mm/huge_memory: add new_order and offset to split_huge_pages*() pr_debug Zi Yan
2025-08-12 15:55 ` [PATCH v3 2/4] selftests/mm: add check_folio_orders() helper Zi Yan
2025-08-13 3:38 ` wang lian
2025-08-14 17:50 ` Zi Yan
2025-08-13 21:12 ` Wei Yang
2025-08-13 21:56 ` Zi Yan
2025-08-12 15:55 ` [PATCH v3 3/4] selftests/mm: reimplement is_backed_by_thp() with more precise check Zi Yan
2025-08-13 21:41 ` Wei Yang
2025-08-13 21:58 ` Zi Yan [this message]
2025-08-12 15:55 ` [PATCH v3 4/4] selftests/mm: check after-split folio orders in split_huge_page_test Zi Yan
2025-08-14 9:16 ` Wei Yang
2025-08-14 13:35 ` 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=47433AB7-58A4-4791-9C40-431D8573E26D@nvidia.com \
--to=ziy@nvidia.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=lianux.mm@gmail.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 \
/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