On Tue, Jun 03, 2025 at 02:26:03PM +0200, Peter Zijlstra wrote: > On Mon, Jun 02, 2025 at 01:13:29PM +0200, Maxime Ripard wrote: > > > > I can't operate kunit > > > > Why not? > > Too complicated. People have even wrecked tools/testing/selftests/ to > the point that it is now nearly impossible to run the simple selftests > :-( > > And while I don't mind tests -- they're quite useful. Kunit just looks > to make it all more complicated that it needs to be. Not to mention > there seems to be snakes involved -- and I never can remember how that > works. > > Basically, if the stuff takes more effort to make run, than the time it > runs for, its a loss. And in that respect much of the kernel testing > stuff is a fail. Just too damn hard to make work. > > I want to: make; ./run.sh or something similarly trivial. But clearly > that is too much to task these days :-(
Are you sure you're not confusing kunit with kselftests? You can run all tests in the kernel using: ./tools/testing/kunit/kunit.py run Restrict it to a single subsystem with (for DRM for example): ./tools/testing/kunit/kunit.py run --kunitconfig=drivers/gpu/drm/tests Both would compile a UML kernel and run the tests on your workstation, but you can also run them in qemu with: ./tools/testing/kunit/kunit.py run --arch x86_64 So it looks close to what you expect? Maxime
signature.asc
Description: PGP signature
