All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: kernelci@lists.linux.dev
Subject: Re: Enabling additional KUnit tests in KernelCI?
Date: Sat, 18 Apr 2026 17:50:19 -0700	[thread overview]
Message-ID: <20260419005019.GA18115@quark> (raw)
In-Reply-To: <4fd302e0-ffa7-4bbf-a94a-c8879fde32f4@sirena.org.uk>

On Fri, Mar 13, 2026 at 12:31:41PM +0000, Mark Brown wrote:
> On Fri, Mar 13, 2026 at 01:04:56AM +0000, Eric Biggers wrote:
> > On Thu, Mar 12, 2026 at 11:34:51PM +0000, Mark Brown wrote:
> 
> > > Whatever is enabled by the KUnit runner tools/testing/kunit/kunit.py
> > > (which makes x86_64 a bit of an unfortunate choice given how slim theilr
> > > defconfig is).  The theory is that the KUnit configs will do the right
> 
> > Yes, the tests run by kunit.py depend on the args passed to it.  It
> > looks like without any arguments it runs all tests available with
> > defconfig + tools/testing/kunit/configs/default.config.  With
> > --alltests, it runs all tests available with defconfig +
> > tools/testing/kunit/configs/all_tests.config.  Both set
> > "CONFIG_KUNIT_ALL_TESTS=y", so the difference is just what additional
> > options get enabled to fulfill the test dependencies.  all_tests.config
> > enables more dependencies than default.config.
> 
> Yes, exactly.
> 
> > So I think KernelCI should start passing --alltests to kunit.py, and I
> > should get the dependencies for all the crypto and CRC tests added to
> > tools/testing/kunit/configs/all_tests.config.  Then KernelCI would pick
> > them up automatically.
> 
> That sounds like a plan.
> 
> > > The KUnit runner uses qemu as standard which I guess is probably fine
> > > for an initial pass, we would need to do a bunch more plumbing to run on
> > > actual hardware and pull the results out.  We'd also be restricted by
> > > what's available to us, at the minute we've got arm, arm64, riscv and
> > > x86 systems with a bit of an embedded focus.
> 
> > It seems kunit.py uses UML by default, though it accepts an --arch
> > argument which enables QEMU.  So something to think about for KernelCI
> > would be to run all KUnit tests with different combinations of --arch.
> 
> Right, and UML only works with an x86 host which is fun.  qemu is the
> standard way of running for a specific architecture.

Just to follow up on this, in mainline 'kunit.py run --alltests' now
runs all the CRC and crypto library KUnit tests.

It looks like the kunit job on KernelCI is still running only on the 6.1
kernel.  Will it be enabled on newer kernels?

- Eric

  reply	other threads:[~2026-04-19  0:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07  7:55 Enabling additional KUnit tests in KernelCI? Eric Biggers
2026-03-12 20:21 ` Mark Brown
2026-03-12 21:51   ` Eric Biggers
2026-03-12 23:34     ` Mark Brown
2026-03-13  1:04       ` Eric Biggers
2026-03-13 12:31         ` Mark Brown
2026-04-19  0:50           ` Eric Biggers [this message]
2026-04-20 14:16             ` Mark Brown
2026-04-21 12:34               ` 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=20260419005019.GA18115@quark \
    --to=ebiggers@kernel.org \
    --cc=broonie@kernel.org \
    --cc=kernelci@lists.linux.dev \
    /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.