From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: [igt-dev] [PATCH i-g-t] i915/gem_ctx_isolation: Use static iterator
Date: Thu, 23 Jan 2020 12:01:34 +0000 [thread overview]
Message-ID: <20200123120134.2682-1-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Quick fixup to the test so correct way of iterating the static engine list
is used. More comprehensive fixes to the test are in progress.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
tests/i915/gem_ctx_isolation.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/i915/gem_ctx_isolation.c b/tests/i915/gem_ctx_isolation.c
index 6aa27133cbb7..8b72a16ad86f 100644
--- a/tests/i915/gem_ctx_isolation.c
+++ b/tests/i915/gem_ctx_isolation.c
@@ -857,6 +857,7 @@ static unsigned int __has_context_isolation(int fd)
igt_main
{
unsigned int has_context_isolation = 0;
+ const struct intel_execution_engine2 *e;
int fd = -1;
igt_fixture {
@@ -876,8 +877,7 @@ igt_main
igt_skip_on(gen > LAST_KNOWN_GEN);
}
- for (const struct intel_execution_engine2 *e = intel_execution_engines2;
- e->name; e++) {
+ __for_each_static_engine(e) {
igt_subtest_group {
igt_fixture {
igt_require(has_context_isolation & (1 << e->class));
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-01-23 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 12:01 Tvrtko Ursulin [this message]
2020-01-23 12:21 ` [igt-dev] [Intel-gfx] [PATCH i-g-t] i915/gem_ctx_isolation: Use static iterator Petri Latvala
2020-01-23 13:14 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-24 6:45 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2020-01-24 16:06 ` [igt-dev] ✗ 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=20200123120134.2682-1-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=tvrtko.ursulin@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