From: David Hildenbrand <david@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: Fix test result reporting in gup_longterm
Date: Thu, 22 May 2025 10:42:50 +0200 [thread overview]
Message-ID: <f6cf8a99-48b0-46f7-b11b-574d1544fa24@redhat.com> (raw)
In-Reply-To: <e7cb18c4-fed3-4fa5-bb51-228f2b018ce9@sirena.org.uk>
On 21.05.25 20:48, Mark Brown wrote:
> On Mon, May 19, 2025 at 03:28:47PM +0200, David Hildenbrand wrote:
>> On 16.05.25 20:07, Mark Brown wrote:
>>> On Fri, May 16, 2025 at 04:12:08PM +0200, David Hildenbrand wrote:
>
>>> [Converting to kselftet_harness]
>>>>> That'd certainly work, though doing that is more surgery on the test
>>>>> than I personally have the time/enthusiasm for right now.
>
>>>> Same over here.
>
>>>> But probably if we touch it, we should just clean it up right away. Well,
>>>> if we decide that that is the right cleanup. (you mention something like that
>>>> in your patch description :)
>
>>> OTOH there's something to be said for just making incremental
>>> improvements in the tests where we can, they tend not to get huge
>>> amounts of love in general which means perfect can very much be the
>
>> I would agree if it would be a handful of small changes.
>
>> But here we are already at
>
>> 1 file changed, 107 insertions(+), 56 deletions(-)
>
> So, I did have a brief poke at this which confirmed my instinct that
> blocking a fix for this (and the other similarly structured tests like
> cow) seems disproportionate.
Thanks for giving it a try.
>
> The biggest issue is the configuration of fixtures, the harness really
> wants the set of test variants to be fixed at compile time (see the
> FIXTURE_ macros) but we're covering the dynamically discovered list of
> huge page sizes.
Yes.
Probably, one might be able to revert the logic: instead of running each
test for each size, run each size for each test: then, the tests are
fixed and would be covering all available sizes in a single logical test.
I agree that that really is a bigger rework. Let me take a look at your
original patch later (fairly busy today, please poke me if I forget).
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-05-22 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 8:57 [PATCH] selftests/mm: Fix test result reporting in gup_longterm Mark Brown
2025-05-15 9:35 ` Dev Jain
2025-05-15 9:41 ` Mark Brown
2025-05-15 9:43 ` Dev Jain
2025-05-16 8:02 ` David Hildenbrand
2025-05-16 12:29 ` Mark Brown
2025-05-16 12:55 ` David Hildenbrand
2025-05-16 13:09 ` Mark Brown
2025-05-16 14:12 ` David Hildenbrand
2025-05-16 18:07 ` Mark Brown
2025-05-19 13:28 ` David Hildenbrand
2025-05-19 14:55 ` Mark Brown
2025-05-21 18:48 ` Mark Brown
2025-05-22 8:42 ` David Hildenbrand [this message]
2025-05-22 9:23 ` Mark Brown
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=f6cf8a99-48b0-46f7-b11b-574d1544fa24@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
/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).