[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aaa9cdf2-8fd9-4073-8c5e-f4ae3762a1bb@sirena.org.uk>
Date: Tue, 20 Jan 2026 17:47:42 +0000
From: Mark Brown <broonie@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: David Hildenbrand <david@...nel.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
"Liam R. Howlett" <Liam.Howlett@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, Mike Rapoport <rppt@...nel.org>,
Suren Baghdasaryan <surenb@...gle.com>,
Michal Hocko <mhocko@...e.com>, Shuah Khan <shuah@...nel.org>,
Jason Gunthorpe <jgg@...pe.ca>, Leon Romanovsky <leon@...nel.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH] selftests/mm: Have the harness run each test category
separately
On Tue, Jan 20, 2026 at 09:22:52AM -0800, Andrew Morton wrote:
> On Tue, 20 Jan 2026 13:25:32 +0000 Mark Brown <broonie@...nel.org> wrote:
> > has separately. Since kselftest really wants to run test programs this
> > is done by providing a trivial wrapper script for each categorty that
> > invokes run_vmtest.sh, this is not a thing of great elegence but it is
> > clear and simple. Since run_vmtests.sh is doing runtime support
> > detection, scenario enumeration and setup for many of the tests we can't
> > consistently tell the framework about the individual test programs.
> Thanks, let's see what people think.
> What happens with tests which are newly added but which don't integrate
> into this new framework? eg,
> https://lkml.kernel.org/r/20260120123239.909882-2-linmiaohe@huawei.com
Anything adding a new category will just not get run by the kselftest
harness until someone adds a wrapper script for them, they'll still get
run if someone invokes run_vmtest.sh with no arguments directly. As the
changelog says it's not particularly nice, but hopefully people don't
add new categories all that often.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists