From: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: skhan@linuxfoundation.org, linux-kselftest@vger.kernel.org,
Daniel Latypov <dlatypov@google.com>,
linux-kernel@vger.kernel.org, igt-dev@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Isabella Basso <isabbasso@riseup.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
David Airlie <airlied@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH RFC v2 6/8] drm/i915: add perf selftests to KUnit
Date: Thu, 3 Nov 2022 14:51:36 +0000 [thread overview]
Message-ID: <048d54e7e5718ba6c7606be61482cedd7cb92dfd.1667486144.git.mchehab@kernel.org> (raw)
In-Reply-To: <cover.1667486144.git.mchehab@kernel.org>
Now that i915 KUnit has PCI support, add perf tests as well.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH RFC v2 0/8] at: https://lore.kernel.org/all/cover.1667486144.git.mchehab@kernel.org/
drivers/gpu/drm/i915/selftests/i915_kunit.c | 34 ++++++++++++++++++++-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/selftests/i915_kunit.c b/drivers/gpu/drm/i915/selftests/i915_kunit.c
index f5281c866d75..6de5d3fa8920 100644
--- a/drivers/gpu/drm/i915/selftests/i915_kunit.c
+++ b/drivers/gpu/drm/i915/selftests/i915_kunit.c
@@ -202,6 +202,30 @@ static struct kunit_case i915_live_tests[] = {
};
#undef selftest
+/*
+ * Suite 3: live selftests
+ */
+
+#define selftest(x, __y) int __y(struct drm_i915_private *i915);
+#include "i915_perf_selftests.h"
+#undef selftest
+
+/* Create selftest functions */
+#define selftest(__x, __y) \
+ static void perf_##__x(struct kunit *test) { \
+ run_pci_test(test, __y); \
+ }
+#include "i915_perf_selftests.h"
+#undef selftest
+
+/* Fill tests array */
+#define selftest(__x, __y) KUNIT_CASE(perf_##__x),
+static struct kunit_case i915_perf_tests[] = {
+#include "i915_perf_selftests.h"
+ {}
+};
+#undef selftest
+
/*
* Declare test suites
*/
@@ -219,10 +243,18 @@ static struct kunit_suite i915_test_suites[] = {
.suite_init = i915_pci_init_suite,
.suite_exit = i915_pci_exit_suite,
},
+ {
+ .name = "i915 perf selftests",
+ .test_cases = i915_perf_tests,
+ .init = initialize_i915_selftests,
+ .suite_init = i915_pci_init_suite,
+ .suite_exit = i915_pci_exit_suite,
+ },
};
kunit_test_suites(&i915_test_suites[0],
- &i915_test_suites[1]);
+ &i915_test_suites[1],
+ &i915_test_suites[2]);
MODULE_LICENSE("GPL v2");
MODULE_IMPORT_NS(I915_SELFTEST);
--
2.38.1
next prev parent reply other threads:[~2022-11-03 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 14:51 [Intel-gfx] [PATCH RFC v2 0/8] Add KUnit support for i915 driver Mauro Carvalho Chehab
2022-11-03 14:51 ` [Intel-gfx] [PATCH RFC v2 1/8] drm/i915: export all selftest functions Mauro Carvalho Chehab
2022-11-03 14:51 ` [Intel-gfx] [PATCH RFC v2 2/8] drm/i915: place selftest preparation on a separate function Mauro Carvalho Chehab
2022-11-03 14:51 ` [Intel-gfx] [PATCH RFC v2 3/8] drm/i915: allow running mock selftests via Kunit Mauro Carvalho Chehab
2022-11-03 14:51 ` [Intel-gfx] [PATCH RFC v2 4/8] drm/i915: add support to run KUnit tests on bare metal Mauro Carvalho Chehab
2022-11-03 14:51 ` [Intel-gfx] [PATCH RFC v2 5/8] drm/i915: add live selftests to KUnit Mauro Carvalho Chehab
2022-11-03 14:51 ` Mauro Carvalho Chehab [this message]
2022-11-03 14:51 ` [Intel-gfx] [PATCH RFC v2 7/8] drm/i915: now that all functions are used, remove __maybe_unused Mauro Carvalho Chehab
2022-11-03 14:51 ` [Intel-gfx] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL Mauro Carvalho Chehab
2022-11-03 19:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add KUnit support for i915 driver Patchwork
2022-11-03 19:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-11-03 19:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-04 16:12 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=048d54e7e5718ba6c7606be61482cedd7cb92dfd.1667486144.git.mchehab@kernel.org \
--to=mchehab@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dlatypov@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=isabbasso@riseup.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=skhan@linuxfoundation.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