On Tue, 20 Sep 2022 11:18:25 +0300 Petri Latvala <petri.latvala@xxxxxxxxx> wrote: > On Sun, Aug 28, 2022 at 09:09:20PM -0300, Isabella Basso wrote: > > As the DRM selftests are now using KUnit [1], update IGT tests as well. > > > > [1] - https://lore.kernel.org/all/20220708203052.236290-1-maira.canal@xxxxxx/ > > > > Signed-off-by: Isabella Basso <isabbasso@xxxxxxxxxx> > > --- > > tests/drm_buddy.c | 7 ++++--- > > tests/drm_mm.c | 7 ++++--- > > tests/kms_selftest.c | 12 +++++++++--- > > 3 files changed, 17 insertions(+), 9 deletions(-) > > > > diff --git a/tests/drm_buddy.c b/tests/drm_buddy.c > > index 06876e0c..74c06dce 100644 > > --- a/tests/drm_buddy.c > > +++ b/tests/drm_buddy.c > > @@ -6,9 +6,10 @@ > > #include "igt.h" > > #include "igt_kmod.h" > > > > -IGT_TEST_DESCRIPTION("Basic sanity check of DRM's buddy allocator (struct drm_buddy)"); > > +IGT_TEST_DESCRIPTION("Basic sanity check of DRM's buddy allocator (struct \ > > + drm_buddy) using KUnit"); > > > > -igt_main > > +igt_simple_main > > { > > - igt_kselftests("test-drm_buddy", NULL, NULL, NULL); > > + igt_kunit("drm_buddy_test", NULL); > > } > > With kselftests we had the ability to only run a specified set of > tests, and with or without selection, we had sub-results for each > through dynamic subtests. Does kunit have that possibility? I mean I > know kunit itself does but what about igt_kunit()? I don't think so. I created a KUnit with the mock selftests: $ modinfo test-i915-mock filename: /lib/modules/6.1.0-rc2-drm-b1cab854a639+/kernel/drivers/gpu/drm/i915/test-i915-mock.ko import_ns: I915_SELFTEST license: GPL v2 depends: i915 retpoline: Y intree: Y name: test_i915_mock vermagic: 6.1.0-rc2-drm-b1cab854a639+ SMP preempt mod_unload There's no module parameters. Just loading it makes all tests there to run. OK, with the current implementation, we could have one module per subtest, but that sounds overkill. Another possibility would be to implement it like: test-i915-mock-fences test-i915-mock-hugepages ... which would allow a finer control. Another possibility would be to change kunit_suite and kunit_test_suites() to optionally create a modprobe parameter to allow specifying what tests from the test suites would run. On the other hand, not sure if are there any gains implementing it, at least for the hardware-independent tests. I mean, if one of such tests fail after a patch, the change is broken and should be reverted, as this is a regression. > Orthogonal to that question, drm_mm and test-drm_modeset are _now_ > using kunit but in LTS kernels they're not, and we'd like to be able > to keep testing those. That means having both launchers here and just > letting the "incorrect" one produce a 'skip'. Agreed. Patch 4/4 should be checking if the test module is there. If not, fall back to selftest. Regards, Mauro
