From: Wei Yang <richard.weiyang@gmail.com>
To: Donet Tom <donettom@linux.ibm.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org,
David Hildenbrand <david@redhat.com>, Zi Yan <ziy@nvidia.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [PATCH] selftests/mm: refactore split_huge_page_test with kselftest_harness
Date: Fri, 5 Sep 2025 13:39:44 +0000 [thread overview]
Message-ID: <20250905133944.dxwa6l5acd2w7mgj@master> (raw)
In-Reply-To: <720957f8-c50e-428e-952a-9616e9f610b8@linux.ibm.com>
On Fri, Sep 05, 2025 at 05:03:26PM +0530, Donet Tom wrote:
[...]
>> +FIXTURE(split_pmd_thp_to_order) {
>> +};
>> +
>> +FIXTURE_VARIANT(split_pmd_thp_to_order) {
>> + int order;
>> +};
>> +
>> +FIXTURE_SETUP(split_pmd_thp_to_order)
>> +{
>> + if (variant->order >= pmd_order)
>> + SKIP(return, "order %d is not supported", variant->order);
>
>
>On a 64 KB page size system, the page order is 5, so the remaining tests
>are getting skipped. On such systems, these tests are effectively invalid.
>Instead of skipping them, would it be better to simply not account those
>tests?
>
> # PASSED: 64 / 64 tests passed.
> # 30 skipped test(s) detected. Consider enabling relevant config options to
>improve coverage.
> # Totals: pass:34 fail:0 xfail:0 xpass:0 skip:30 error:0
>
>
>Here, the 30 skipped tests are invalid, and the total valid tests are 34.
>Would it make sense to exclude the 30 invalid tests entirely for 64KB page
>size systems?
>
Yes, this is a little annoying. But I don't find a way to achieve what you
mentioned with kselftest_harness. :-(
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2025-09-05 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 3:24 Wei Yang
2025-09-05 9:10 ` wang lian
2025-09-05 13:43 ` Wei Yang
2025-09-05 11:33 ` Donet Tom
2025-09-05 13:39 ` Wei Yang [this message]
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=20250905133944.dxwa6l5acd2w7mgj@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=donettom@linux.ibm.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--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