[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yyl3UXvLd3Jyr9uP@platvala-desk.ger.corp.intel.com>
Date: Tue, 20 Sep 2022 11:18:25 +0300
From: Petri Latvala <petri.latvala@...el.com>
To: Isabella Basso <isabbasso@...eup.net>
Cc: igt-dev@...ts.freedesktop.org, linux-kselftest@...r.kernel.org,
daniel@...ll.ch, kunit-dev@...glegroups.com,
magalilemes00@...il.com, maira.canal@....br, dlatypov@...gle.com,
n@...aprado.net, linux-kernel@...r.kernel.org,
leandro.ribeiro@...labora.com, dri-devel@...ts.freedesktop.org,
davidgow@...gle.com, tales.aparecida@...il.com,
skhan@...uxfoundation.org, andrealmeid@...eup.net,
brendanhiggins@...gle.com, twoerner@...il.com
Subject: Re: [igt-dev] [PATCH i-g-t v2 4/4] tests: DRM selftests: switch to
KUnit
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@usp.br/
>
> Signed-off-by: Isabella Basso <isabbasso@...eup.net>
> ---
> 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()?
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'.
--
Petri Latvala
> diff --git a/tests/drm_mm.c b/tests/drm_mm.c
> index 2052b115..75fc6682 100644
> --- a/tests/drm_mm.c
> +++ b/tests/drm_mm.c
> @@ -24,9 +24,10 @@
> #include "igt.h"
> #include "igt_kmod.h"
>
> -IGT_TEST_DESCRIPTION("Basic sanity check of DRM's range manager (struct drm_mm)");
> +IGT_TEST_DESCRIPTION("Basic sanity check of DRM's range manager (struct drm_mm)\
> + using KUnit");
>
> -igt_main
> +igt_simple_main
> {
> - igt_kselftests("test-drm_mm", NULL, NULL, NULL);
> + igt_kunit("drm_mm_test", NULL);
> }
> diff --git a/tests/kms_selftest.c b/tests/kms_selftest.c
> index abc4bfe9..bbf24c2b 100644
> --- a/tests/kms_selftest.c
> +++ b/tests/kms_selftest.c
> @@ -24,9 +24,15 @@
> #include "igt.h"
> #include "igt_kmod.h"
>
> -IGT_TEST_DESCRIPTION("Basic sanity check of KMS selftests.");
> +IGT_TEST_DESCRIPTION("Basic sanity check of KMS selftests using KUnit");
>
> -igt_main
> +igt_simple_main
> {
> - igt_kselftests("test-drm_modeset", NULL, NULL, NULL);
> + igt_kunit("drm_cmdline_parser_test", NULL);
> + igt_kunit("drm_damage_helper_test", NULL);
> + igt_kunit("drm_dp_mst_helper_test", NULL);
> + igt_kunit("drm_format_helper_test", NULL);
> + igt_kunit("drm_format_test", NULL);
> + igt_kunit("drm_framebuffer_test", NULL);
> + igt_kunit("drm_plane_helper_test", NULL);
> }
> --
> 2.37.2
>
Powered by blists - more mailing lists