From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
igt-dev@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v6 1/1] tests/i915/gem_ctx_persistence: Set context with supported engines
Date: Thu, 30 Jan 2020 10:31:31 +0000 [thread overview]
Message-ID: <8454bc4b-d07a-07bd-a8e8-bd15795de282@linux.intel.com> (raw)
In-Reply-To: <158033216228.13511.16715726772665260638@skylake-alporthouse-com>
On 29/01/2020 21:09, Chris Wilson wrote:
> Quoting Bommu Krishnaiah (2020-01-29 18:10:02)
>> Update the context with supported engines on the platform with set_property
>> I915_CONTEXT_PARAM_ENGINES to make sure the work load is submitted to
>> the available engines only.
>>
>> v2: addressed the review comments.
>> v3: addressed v2 review comments.
>> V4: Re-introduced the gem_context_set_all_engines() API,test_process_mixed()
>> test creating new forked process, to set engine map to new forked process
>> I added gem_context_set_all_engines() API.
>> v5: addressed v4 review comments.
>> v6: addressed chris comments.
>
> This is totally useless as a recording of the history. Explain why you
> had to make the changes, for posterity.
>
>> - __for_each_static_engine(e) {
>> + for_each_engine(e, i915) {
>
> Incorrect change that leads to compiler warnings and prevents the legacy
> tests being listed by CI.
>
> I've given up and fixed it.
Partially my bad, I suggested to use for_each_engine while forgetting subtest
enumeration needs to be static and for_each_engine has an runtime element. :(
This diff on top fixes it:
diff --git a/tests/i915/gem_ctx_persistence.c b/tests/i915/gem_ctx_persistence.c
index de6f59251200..c56189c57cdd 100644
--- a/tests/i915/gem_ctx_persistence.c
+++ b/tests/i915/gem_ctx_persistence.c
@@ -758,7 +758,8 @@ static void smoketest(int i915)
igt_main
{
- const struct intel_execution_engine2 *e;
+ const struct intel_execution_engine *e;
+ const struct intel_execution_engine2 *e2;
int i915;
igt_fixture {
@@ -791,10 +792,10 @@ igt_main
igt_subtest("hang")
test_nohangcheck_hang(i915);
- for_each_engine(e, i915) {
+ for (e = intel_execution_engines; e->name; e++) {
igt_subtest_group {
igt_fixture {
- gem_require_ring(i915, e->flags);
+ gem_require_ring(i915, eb_ring(e));
gem_require_contexts(i915);
}
@@ -822,37 +823,37 @@ igt_main
}
}
- __for_each_physical_engine(i915, e) {
+ __for_each_physical_engine(i915, e2) {
igt_subtest_group {
igt_fixture {
- gem_require_ring(i915, e->flags);
+ gem_require_ring(i915, e2->flags);
gem_require_contexts(i915);
}
- igt_subtest_f("%s-persistence", e->name)
- test_persistence(i915, e->flags);
+ igt_subtest_f("%s-persistence", e2->name)
+ test_persistence(i915, e2->flags);
- igt_subtest_f("%s-cleanup", e->name)
- test_nonpersistent_cleanup(i915, e->flags);
+ igt_subtest_f("%s-cleanup", e2->name)
+ test_nonpersistent_cleanup(i915, e2->flags);
- igt_subtest_f("%s-queued", e->name)
- test_nonpersistent_queued(i915, e->flags);
+ igt_subtest_f("%s-queued", e2->name)
+ test_nonpersistent_queued(i915, e2->flags);
- igt_subtest_f("%s-mixed", e->name)
- test_nonpersistent_mixed(i915, e->flags);
+ igt_subtest_f("%s-mixed", e2->name)
+ test_nonpersistent_mixed(i915, e2->flags);
- igt_subtest_f("%s-mixed-process", e->name)
- test_process_mixed(i915, e->flags);
+ igt_subtest_f("%s-mixed-process", e2->name)
+ test_process_mixed(i915, e2->flags);
- igt_subtest_f("%s-hostile", e->name)
- test_nonpersistent_hostile(i915, e->flags);
+ igt_subtest_f("%s-hostile", e2->name)
+ test_nonpersistent_hostile(i915, e2->flags);
- igt_subtest_f("%s-hostile-preempt", e->name)
+ igt_subtest_f("%s-hostile-preempt", e2->name)
test_nonpersistent_hostile_preempt(i915,
- e->flags);
+ e2->flags);
- igt_subtest_f("%s-hang", e->name)
- test_nonpersistent_hang(i915, e->flags);
+ igt_subtest_f("%s-hang", e2->name)
+ test_nonpersistent_hang(i915, e2->flags);
}
}
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-01-30 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 18:10 [igt-dev] [PATCH i-g-t v6 0/1] tests/i915/gem_ctx_persistence: Set context with supported engines Bommu Krishnaiah
2020-01-29 18:10 ` [igt-dev] [PATCH i-g-t v6 1/1] " Bommu Krishnaiah
2020-01-29 21:09 ` Chris Wilson
2020-01-30 10:31 ` Tvrtko Ursulin [this message]
2020-01-30 10:52 ` Tvrtko Ursulin
2020-01-30 10:55 ` Chris Wilson
2020-01-30 11:08 ` Tvrtko Ursulin
2020-01-30 11:13 ` Chris Wilson
2020-01-30 11:37 ` Tvrtko Ursulin
2020-01-30 11:40 ` Chris Wilson
2020-01-29 20:27 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/gem_ctx_persistence: Set context with supported engines (rev7) Patchwork
2020-02-01 3:18 ` [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=8454bc4b-d07a-07bd-a8e8-bd15795de282@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=krishnaiah.bommu@intel.com \
--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