From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org,
Tomi Sarvela <tomi.p.sarvela@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: [igt-dev] [PATCH i-g-t] i915/i915_selftests: Expose 'perf' selftests
Date: Fri, 1 Nov 2019 14:21:23 +0000 [thread overview]
Message-ID: <20191101142123.18136-1-chris@chris-wilson.co.uk> (raw)
Find all the perf* selftests and expose them in our igt. In CI we expect
these not to be run in BAT (since they are just performance tests rather
than conformance), but expect the results to be available from the
shards.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
---
tests/i915/i915_selftest.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/tests/i915/i915_selftest.c b/tests/i915/i915_selftest.c
index 6d597e682..abc8c9c79 100644
--- a/tests/i915/i915_selftest.c
+++ b/tests/i915/i915_selftest.c
@@ -40,4 +40,9 @@ igt_main
"live_selftests=-1 disable_display=1 st_filter=%s",
env) < sizeof(opts));
igt_kselftests("i915", opts, "live_selftests", "live");
+
+ igt_assert(snprintf(opts, sizeof(opts),
+ "perf_selftests=-1 disable_display=1 st_filter=%s",
+ env) < sizeof(opts));
+ igt_kselftests("i915", opts, "perf_selftests", "perf");
}
--
2.24.0.rc2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-11-01 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 14:21 Chris Wilson [this message]
2019-11-01 15:49 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/i915_selftests: Expose 'perf' selftests Patchwork
2019-11-01 17:26 ` [igt-dev] [Intel-gfx] [PATCH i-g-t] " Lionel Landwerlin
2019-11-01 17:43 ` Chris Wilson
2019-11-03 0:17 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=20191101142123.18136-1-chris@chris-wilson.co.uk \
--to=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=tomi.p.sarvela@intel.com \
/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