From: Wei Yang <richard.weiyang@gmail.com>
To: Zi Yan <ziy@nvidia.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
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 v2 2/3] selftests/mm: add check_folio_orders() helper.
Date: Mon, 11 Aug 2025 21:28:02 +0000 [thread overview]
Message-ID: <20250811212802.gsvbeqmo62v4tqly@master> (raw)
In-Reply-To: <B13F65A9-B001-4494-A060-23D95055553F@nvidia.com>
On Mon, Aug 11, 2025 at 02:39:08PM -0400, Zi Yan wrote:
[...]
>>> +static int gather_folio_orders(char *vaddr_start, size_t len,
>>> + int pagemap_file, int kpageflags_file,
>>> + int orders[], int nr_orders)
>>> +{
>>> + uint64_t page_flags = 0;
>>> + int cur_order = -1;
>>> + char *vaddr;
>>> +
>>> + if (!pagemap_file || !kpageflags_file)
>>> + return -1;
>>> + if (nr_orders <= 0)
>>> + return -1;
>>> +
>>> + for (vaddr = vaddr_start; vaddr < vaddr_start + len; ) {
>>> + char *next_folio_vaddr;
>>> + int status;
>>> +
>>> + if (get_page_flags(vaddr, pagemap_file, kpageflags_file, &page_flags))
>>> + return -1;
>>> +
>>> + /* all order-0 pages with possible false postive (non folio) */
>>> + if (!(page_flags & (KPF_COMPOUND_HEAD | KPF_COMPOUND_TAIL))) {
>>> + orders[0]++;
>>> + vaddr += psize();
>>> + continue;
>>> + }
>>> +
>>> + /* skip non thp compound pages */
>>> + if (!(page_flags & KPF_THP)) {
>>> + vaddr += psize();
>>> + continue;
>>> + }
>>> +
>>> + /* vpn points to part of a THP at this point */
>>> + if (page_flags & KPF_COMPOUND_HEAD)
>>> + cur_order = 1;
>>> + else {
>>> + /* not a head nor a tail in a THP? */
>>> + if (!(page_flags & KPF_COMPOUND_TAIL))
>>> + return -1;
>>> + continue;
>>> + }
>>> +
>>> + next_folio_vaddr = vaddr + (1UL << (cur_order + pshift()));
>>> +
>>> + if (next_folio_vaddr >= vaddr_start + len)
>>> + break;
>>
>> Would we skip order 1 folio at the last position?
>>
>> For example, vaddr_start is 0x2000, len is 0x2000 and the folio at vaddr_start
>> is an order 1 folio, whose size is exactly 0x2000.
>>
>> Then we will get next_folio_vaddr == vaddr_start + len.
>>
>> Could that happen?
>
>No. After the loop, there is code checking cur_order and updating orders[].
>
Oh, I missed this.
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-08-11 21:28 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
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 [this message]
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=20250811212802.gsvbeqmo62v4tqly@master \
--to=richard.weiyang@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=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.