From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Andi Shyti <andi.shyti@intel.com>,
IGT dev <igt-dev@lists.freedesktop.org>
Cc: Andi Shyti <andi@etezian.org>
Subject: Re: [igt-dev] [PATCH v21 5/6] lib: igt_dummyload: use for_each_context_engine()
Date: Wed, 17 Apr 2019 17:14:45 +0100 [thread overview]
Message-ID: <a0de5a71-e513-0e8c-a1ed-3a7571bd1275@linux.intel.com> (raw)
In-Reply-To: <030e2dba-1dd8-da25-2dd7-e2a7cdd6ad87@intel.com>
On 17/04/2019 16:42, Daniele Ceraolo Spurio wrote:
> <snip>
>
>> @@ -94,17 +95,17 @@ emit_recursive_batch(igt_spin_t *spin,
>> nengine = 0;
>> if (opts->engine == ALL_ENGINES) {
>> - unsigned int engine;
>> + struct intel_execution_engine2 *engine;
>> - for_each_physical_engine(fd, engine) {
>> + for_each_context_engine(fd, opts->ctx, engine) {
>
> On a kernel that has the new I915_CONTEXT_PARAM_ENGINES, wouldn't this
> implicitly update opts->ctx to use it (via the ctx_map_engines in
> intel_init_engine_list)? What if the caller then tries to submit with
> that ctx using an execbuf flag?only an issue until all the callers are
> updated I guess.
I think you are right. And I think it is not only until all tests are
updated that we need dual paths but maybe even longer.
Something like:
if (ctx_has_map(ctx)) {
for_each_context_engine()
...
} else {
for_each_physical_engine
...
}
Problem though is the end game of replacing for_each_physical_engine
with the new implementation. It is okay to have for_each_physical_engine
configure the context when called directly in a test, but a bit less
okay if done deep down in some function like this one.
So what to do to preserve compatibility with eb.flags and not mess up
the context in here.. use the static iterator for contexts wo/ maps and
legacy eb? But what does ALL_ENGINES mean then? Phase out ALL_ENGINES
support in spin batch? Needs an audit of how many call sites we have and
how do they look.
Regards,
Tvrtko
>
> Thanks,
> Daniele
>
>> if (opts->flags & IGT_SPIN_POLL_RUN &&
>> - !gem_can_store_dword(fd, engine))
>> + !gem_class_can_store_dword(fd, engine->class))
>> continue;
>> - engines[nengine++] = engine;
>> + flags[nengine++] = engine->flags;
>> }
>> } else {
>> - engines[nengine++] = opts->engine;
>> + flags[nengine++] = opts->engine;
>> }
>> igt_require(nengine);
>> @@ -234,7 +235,7 @@ emit_recursive_batch(igt_spin_t *spin,
>> for (i = 0; i < nengine; i++) {
>> execbuf->flags &= ~ENGINE_MASK;
>> - execbuf->flags |= engines[i];
>> + execbuf->flags |= flags[i];
>> gem_execbuf_wr(fd, execbuf);
>> @@ -309,9 +310,19 @@ igt_spin_batch_factory(int fd, const struct
>> igt_spin_factory *opts)
>> igt_require_gem(fd);
>> if (opts->engine != ALL_ENGINES) {
>> - gem_require_ring(fd, opts->engine);
>> + struct intel_execution_engine2 e;
>> + int class;
>> +
>> + if (!gem_context_lookup_engine(fd, opts->engine,
>> + opts->ctx, &e)) {
>> + class = e.class;
>> + } else {
>> + gem_require_ring(fd, opts->engine);
>> + class = gem_execbuf_flags_to_engine_class(opts->engine);
>> + }
>> +
>> if (opts->flags & IGT_SPIN_POLL_RUN)
>> - igt_require(gem_can_store_dword(fd, opts->engine));
>> + igt_require(gem_class_can_store_dword(fd, class));
>> }
>> spin = spin_batch_create(fd, opts);
>
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-17 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 15:11 [igt-dev] [PATCH v21 0/6] new engine discovery interface Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 1/6] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 2/6] lib/i915: add gem_engine_topology library and for_each loop definition Andi Shyti
2019-04-16 15:21 ` Chris Wilson
2019-04-16 15:28 ` Andi Shyti
2019-04-16 17:09 ` Tvrtko Ursulin
2019-04-16 15:11 ` [igt-dev] [PATCH v21 3/6] lib: igt_gt: add execution buffer flags to class helper Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 4/6] lib: igt_gt: make gem_engine_can_store_dword() check engine class Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 5/6] lib: igt_dummyload: use for_each_context_engine() Andi Shyti
2019-04-17 15:42 ` Daniele Ceraolo Spurio
2019-04-17 15:48 ` Chris Wilson
2019-04-17 16:14 ` Tvrtko Ursulin [this message]
2019-04-17 16:21 ` Chris Wilson
2019-04-18 8:46 ` Tvrtko Ursulin
2019-04-16 15:11 ` [igt-dev] [PATCH v21 6/6] test: perf_pmu: use the gem_engine_topology library Andi Shyti
2019-04-16 17:06 ` Tvrtko Ursulin
2019-04-16 23:05 ` Andi Shyti
2019-04-17 13:42 ` Tvrtko Ursulin
2019-04-16 16:36 ` [igt-dev] ✓ Fi.CI.BAT: success for new engine discovery interface Patchwork
2019-04-17 0:46 ` [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=a0de5a71-e513-0e8c-a1ed-3a7571bd1275@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=andi.shyti@intel.com \
--cc=andi@etezian.org \
--cc=daniele.ceraolospurio@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