From: Dominik Karol Piatkowski <dominik.karol.piatkowski@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH v4 i-g-t 0/6] Introduce KUnit
Date: Fri, 2 Jun 2023 10:27:15 +0200 [thread overview]
Message-ID: <20230602082721.7818-1-dominik.karol.piatkowski@intel.com> (raw)
This series is a continuation of Isabella's work on introducing
KUnit to IGT.
Sample drm_buddy output:
[thread:13223] TAP version 1
[thread:13223] Executing 6 tests in: drm_buddy
Starting subtest: drm_buddy__drm_test_buddy_alloc_limit
Subtest drm_buddy__drm_test_buddy_alloc_limit: SUCCESS (0.000s)
Starting subtest: drm_buddy__drm_test_buddy_alloc_range
Subtest drm_buddy__drm_test_buddy_alloc_range: SUCCESS (0.000s)
Starting subtest: drm_buddy__drm_test_buddy_alloc_optimistic
Subtest drm_buddy__drm_test_buddy_alloc_optimistic: SUCCESS (0.000s)
Starting subtest: drm_buddy__drm_test_buddy_alloc_pessimistic
Subtest drm_buddy__drm_test_buddy_alloc_pessimistic: SUCCESS (0.000s)
Starting subtest: drm_buddy__drm_test_buddy_alloc_smoke
Subtest drm_buddy__drm_test_buddy_alloc_smoke: SUCCESS (0.000s)
Starting subtest: drm_buddy__drm_test_buddy_alloc_pathological
Subtest drm_buddy__drm_test_buddy_alloc_pathological: SUCCESS (0.000s)
Starting subtest: drm_buddy
Subtest drm_buddy: SUCCESS (0.000s)
The issue of possibility of too many sublevels occurrence is solved
by name concatenation.
Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Dominik Karol Piatkowski (2):
Change logic of ktap parser to run on a thread
Fix drm_mm build error
Isabella Basso (4):
lib/igt_kmod: rename kselftest functions to ktest
lib/igt_kmod.c: check if module is builtin before attempting to unload
it
lib/igt_kmod: add compatibility for KUnit
tests: DRM selftests: switch to KUnit
lib/igt_kmod.c | 133 ++++++-
lib/igt_kmod.h | 14 +-
lib/igt_ktap.c | 615 +++++++++++++++++++++++++++++++
lib/igt_ktap.h | 50 +++
lib/meson.build | 1 +
tests/drm_buddy.c | 4 +-
tests/drm_mm.c | 4 +-
tests/i915/i915_test_config.json | 2 +-
tests/kms_selftest.c | 8 +
9 files changed, 811 insertions(+), 20 deletions(-)
create mode 100644 lib/igt_ktap.c
create mode 100644 lib/igt_ktap.h
--
2.34.1
next reply other threads:[~2023-06-02 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 8:27 Dominik Karol Piatkowski [this message]
2023-06-02 8:27 ` [igt-dev] [PATCH i-g-t 1/6] lib/igt_kmod: rename kselftest functions to ktest Dominik Karol Piatkowski
2023-06-02 8:27 ` [igt-dev] [PATCH i-g-t 2/6] lib/igt_kmod.c: check if module is builtin before attempting to unload it Dominik Karol Piatkowski
2023-06-02 8:27 ` [igt-dev] [PATCH i-g-t 3/6] lib/igt_kmod: add compatibility for KUnit Dominik Karol Piatkowski
2023-06-02 8:27 ` [igt-dev] [PATCH i-g-t 4/6] tests: DRM selftests: switch to KUnit Dominik Karol Piatkowski
2023-06-02 8:27 ` [igt-dev] [PATCH i-g-t 5/6] Change logic of ktap parser to run on a thread Dominik Karol Piatkowski
2023-06-02 8:27 ` [igt-dev] [PATCH i-g-t 6/6] Fix drm_mm build error Dominik Karol Piatkowski
2023-06-05 10:46 ` Mauro Carvalho Chehab
2023-06-02 9:16 ` [igt-dev] ✗ GitLab.Pipeline: warning for Introduce KUnit (rev4) Patchwork
2023-06-02 9:42 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-04 8:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20230602082721.7818-1-dominik.karol.piatkowski@intel.com \
--to=dominik.karol.piatkowski@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox