* [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result
@ 2020-02-13 19:26 Dale B Stimson
2020-02-13 20:44 ` Chris Wilson
2020-02-14 18:43 ` Antonio Argenziano
0 siblings, 2 replies; 6+ messages in thread
From: Dale B Stimson @ 2020-02-13 19:26 UTC (permalink / raw)
To: igt-dev, intel-gfx
Function intel_get_current_engine() should return NULL (instead of
engine 0) if there are no engines.
Function intel_init_engine_list() should not store potential engine
data in the output structure unless the engine is present.
Function intel_init_engine_list() should arguably not filter the static
engine list with gem_has_ring if fd == -1, so that subtests can still
be individually invoked to show subtest FAIL instead of test notrun.
Symptom: A device open failure in gem_ctx_isolation resulted in
an endless __for_each_physical_engine "per-engine" loop with the
purported last potential engine being processed every time.
Diagnosis: device open (or debugfs open) failed, leaving fd == -1.
Control skipped the rest of the initial igt_fixture block, after
which an attempt was made to iterate through engines using macro
__for_each_physical_engine.
Macro __for_each_physical_engine called intel_init_engine_list()
to initialize the loop control data. Because fd == -1,
intel_init_engine_list() fell back to using __for_each_static_engine().
All of the engines in the static engine list are rejected due to
gem_has_ring returning false (because of fd == -1), leaving 0 engines.
That resulted in loop control data with engine_data.nengines == 0
and the data for the last engine considered stored at index 0.
Still in macro __for_each_physical_engine, intel_get_current_engine()
was called to get the engine to process. It should have returned NULL,
but instead returned the engine entry at index 0, which
had received information describing the last potential engine.
This happened without end.
Signed-off-by: Dale B Stimson <dale.b.stimson@intel.com>
---
lib/i915/gem_engine_topology.c | 29 ++++++++++++++++-------------
1 file changed, 16 insertions(+), 13 deletions(-)
diff --git a/lib/i915/gem_engine_topology.c b/lib/i915/gem_engine_topology.c
index 9daa03df4..b8ed49bc9 100644
--- a/lib/i915/gem_engine_topology.c
+++ b/lib/i915/gem_engine_topology.c
@@ -156,10 +156,10 @@ static void query_engine_list(int fd, struct intel_engine_data *ed)
struct intel_execution_engine2 *
intel_get_current_engine(struct intel_engine_data *ed)
{
- if (!ed->n)
- ed->current_engine = &ed->engines[0];
- else if (ed->n >= ed->nengines)
+ if (ed->n >= ed->nengines)
ed->current_engine = NULL;
+ else if (!ed->n)
+ ed->current_engine = &ed->engines[0];
return ed->current_engine;
}
@@ -222,18 +222,21 @@ struct intel_engine_data intel_init_engine_list(int fd, uint32_t ctx_id)
igt_debug("using pre-allocated engine list\n");
__for_each_static_engine(e2) {
- struct intel_execution_engine2 *__e2 =
- &engine_data.engines[engine_data.nengines];
-
- strcpy(__e2->name, e2->name);
- __e2->instance = e2->instance;
- __e2->class = e2->class;
- __e2->flags = e2->flags;
- __e2->is_virtual = false;
-
if (igt_only_list_subtests() ||
- gem_has_ring(fd, e2->flags))
+ (fd < 0) ||
+ gem_has_ring(fd, e2->flags)) {
+ struct intel_execution_engine2 *__e2 =
+ &engine_data.engines[
+ engine_data.nengines];
+
+ strcpy(__e2->name, e2->name);
+ __e2->instance = e2->instance;
+ __e2->class = e2->class;
+ __e2->flags = e2->flags;
+ __e2->is_virtual = false;
+
engine_data.nengines++;
+ }
}
return engine_data;
}
--
2.25.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 6+ messages in thread* Re: [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result
2020-02-13 19:26 [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result Dale B Stimson
@ 2020-02-13 20:44 ` Chris Wilson
2020-02-14 18:43 ` Antonio Argenziano
1 sibling, 0 replies; 6+ messages in thread
From: Chris Wilson @ 2020-02-13 20:44 UTC (permalink / raw)
To: Dale B Stimson, igt-dev, intel-gfx
Quoting Dale B Stimson (2020-02-13 19:26:06)
> Function intel_get_current_engine() should return NULL (instead of
> engine 0) if there are no engines.
There should be some igt to put basic use of for_each_engine() though
its paces. Nothing fancy, just complete a loop....
Andi, am I imagining this? I swear saw patches from you to do the
basics.
Anyway, there should be some, and this is worth adding to them,
for_each_context_engine() on an empty engines[] and assert we do not
enter the loop.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result
2020-02-13 19:26 [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result Dale B Stimson
2020-02-13 20:44 ` Chris Wilson
@ 2020-02-14 18:43 ` Antonio Argenziano
2020-02-14 18:44 ` Chris Wilson
1 sibling, 1 reply; 6+ messages in thread
From: Antonio Argenziano @ 2020-02-14 18:43 UTC (permalink / raw)
To: Dale B Stimson, igt-dev, intel-gfx
On 13/02/20 11:26, Dale B Stimson wrote:
> Function intel_get_current_engine() should return NULL (instead of
> engine 0) if there are no engines.
>
> Function intel_init_engine_list() should not store potential engine
> data in the output structure unless the engine is present.
>
> Function intel_init_engine_list() should arguably not filter the static
> engine list with gem_has_ring if fd == -1, so that subtests can still
> be individually invoked to show subtest FAIL instead of test notrun.
>
> Symptom: A device open failure in gem_ctx_isolation resulted in
> an endless __for_each_physical_engine "per-engine" loop with the
> purported last potential engine being processed every time.
>
> Diagnosis: device open (or debugfs open) failed, leaving fd == -1.
> Control skipped the rest of the initial igt_fixture block, after
> which an attempt was made to iterate through engines using macro
> __for_each_physical_engine.
>
> Macro __for_each_physical_engine called intel_init_engine_list()
> to initialize the loop control data. Because fd == -1,
> intel_init_engine_list() fell back to using __for_each_static_engine().
> All of the engines in the static engine list are rejected due to
> gem_has_ring returning false (because of fd == -1), leaving 0 engines.
> That resulted in loop control data with engine_data.nengines == 0
> and the data for the last engine considered stored at index 0.
>
> Still in macro __for_each_physical_engine, intel_get_current_engine()
> was called to get the engine to process. It should have returned NULL,
> but instead returned the engine entry at index 0, which
> had received information describing the last potential engine.
> This happened without end.
>
> Signed-off-by: Dale B Stimson <dale.b.stimson@intel.com>
> ---
> lib/i915/gem_engine_topology.c | 29 ++++++++++++++++-------------
> 1 file changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/lib/i915/gem_engine_topology.c b/lib/i915/gem_engine_topology.c
> index 9daa03df4..b8ed49bc9 100644
> --- a/lib/i915/gem_engine_topology.c
> +++ b/lib/i915/gem_engine_topology.c
> @@ -156,10 +156,10 @@ static void query_engine_list(int fd, struct intel_engine_data *ed)
> struct intel_execution_engine2 *
> intel_get_current_engine(struct intel_engine_data *ed)
> {
> - if (!ed->n)
> - ed->current_engine = &ed->engines[0];
> - else if (ed->n >= ed->nengines)
> + if (ed->n >= ed->nengines)
> ed->current_engine = NULL;
> + else if (!ed->n)
> + ed->current_engine = &ed->engines[0];
>
> return ed->current_engine;
> }
> @@ -222,18 +222,21 @@ struct intel_engine_data intel_init_engine_list(int fd, uint32_t ctx_id)
> igt_debug("using pre-allocated engine list\n");
>
> __for_each_static_engine(e2) {
> - struct intel_execution_engine2 *__e2 =
> - &engine_data.engines[engine_data.nengines];
> -
> - strcpy(__e2->name, e2->name);
> - __e2->instance = e2->instance;
> - __e2->class = e2->class;
> - __e2->flags = e2->flags;
> - __e2->is_virtual = false;
> -
> if (igt_only_list_subtests() ||
> - gem_has_ring(fd, e2->flags))
> + (fd < 0) ||
Patch LGTM, Chris do you have any issues merging this before someone
implements some tests for the infrastructure?
Acked-by: Antonio Argenziano <antonio.argenziano@intel.com>
> + gem_has_ring(fd, e2->flags)) {
> + struct intel_execution_engine2 *__e2 =
> + &engine_data.engines[
> + engine_data.nengines];
> +
> + strcpy(__e2->name, e2->name);
> + __e2->instance = e2->instance;
> + __e2->class = e2->class;
> + __e2->flags = e2->flags;
> + __e2->is_virtual = false;
> +
> engine_data.nengines++;
> + }
> }
> return engine_data;
> }
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result
2020-02-14 18:43 ` Antonio Argenziano
@ 2020-02-14 18:44 ` Chris Wilson
2020-02-14 18:54 ` Chris Wilson
0 siblings, 1 reply; 6+ messages in thread
From: Chris Wilson @ 2020-02-14 18:44 UTC (permalink / raw)
To: Antonio Argenziano, Dale B Stimson, igt-dev, intel-gfx
Quoting Antonio Argenziano (2020-02-14 18:43:01)
>
>
> On 13/02/20 11:26, Dale B Stimson wrote:
> > Function intel_get_current_engine() should return NULL (instead of
> > engine 0) if there are no engines.
> >
> > Function intel_init_engine_list() should not store potential engine
> > data in the output structure unless the engine is present.
> >
> > Function intel_init_engine_list() should arguably not filter the static
> > engine list with gem_has_ring if fd == -1, so that subtests can still
> > be individually invoked to show subtest FAIL instead of test notrun.
> >
> > Symptom: A device open failure in gem_ctx_isolation resulted in
> > an endless __for_each_physical_engine "per-engine" loop with the
> > purported last potential engine being processed every time.
> >
> > Diagnosis: device open (or debugfs open) failed, leaving fd == -1.
> > Control skipped the rest of the initial igt_fixture block, after
> > which an attempt was made to iterate through engines using macro
> > __for_each_physical_engine.
> >
> > Macro __for_each_physical_engine called intel_init_engine_list()
> > to initialize the loop control data. Because fd == -1,
> > intel_init_engine_list() fell back to using __for_each_static_engine().
> > All of the engines in the static engine list are rejected due to
> > gem_has_ring returning false (because of fd == -1), leaving 0 engines.
> > That resulted in loop control data with engine_data.nengines == 0
> > and the data for the last engine considered stored at index 0.
> >
> > Still in macro __for_each_physical_engine, intel_get_current_engine()
> > was called to get the engine to process. It should have returned NULL,
> > but instead returned the engine entry at index 0, which
> > had received information describing the last potential engine.
> > This happened without end.
> >
> > Signed-off-by: Dale B Stimson <dale.b.stimson@intel.com>
> > ---
> > lib/i915/gem_engine_topology.c | 29 ++++++++++++++++-------------
> > 1 file changed, 16 insertions(+), 13 deletions(-)
> >
> > diff --git a/lib/i915/gem_engine_topology.c b/lib/i915/gem_engine_topology.c
> > index 9daa03df4..b8ed49bc9 100644
> > --- a/lib/i915/gem_engine_topology.c
> > +++ b/lib/i915/gem_engine_topology.c
> > @@ -156,10 +156,10 @@ static void query_engine_list(int fd, struct intel_engine_data *ed)
> > struct intel_execution_engine2 *
> > intel_get_current_engine(struct intel_engine_data *ed)
> > {
> > - if (!ed->n)
> > - ed->current_engine = &ed->engines[0];
> > - else if (ed->n >= ed->nengines)
> > + if (ed->n >= ed->nengines)
> > ed->current_engine = NULL;
> > + else if (!ed->n)
> > + ed->current_engine = &ed->engines[0];
> >
> > return ed->current_engine;
> > }
> > @@ -222,18 +222,21 @@ struct intel_engine_data intel_init_engine_list(int fd, uint32_t ctx_id)
> > igt_debug("using pre-allocated engine list\n");
> >
> > __for_each_static_engine(e2) {
> > - struct intel_execution_engine2 *__e2 =
> > - &engine_data.engines[engine_data.nengines];
> > -
> > - strcpy(__e2->name, e2->name);
> > - __e2->instance = e2->instance;
> > - __e2->class = e2->class;
> > - __e2->flags = e2->flags;
> > - __e2->is_virtual = false;
> > -
> > if (igt_only_list_subtests() ||
> > - gem_has_ring(fd, e2->flags))
> > + (fd < 0) ||
>
> Patch LGTM, Chris do you have any issues merging this before someone
> implements some tests for the infrastructure?
It seems like a really trivial one to write a test for. 3 minutes
tops... Just do it.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result
2020-02-14 18:44 ` Chris Wilson
@ 2020-02-14 18:54 ` Chris Wilson
2020-02-14 19:14 ` Chris Wilson
0 siblings, 1 reply; 6+ messages in thread
From: Chris Wilson @ 2020-02-14 18:54 UTC (permalink / raw)
To: Antonio Argenziano, Dale B Stimson, igt-dev, intel-gfx
+static void libapi(int i915)
+{
+ I915_DEFINE_CONTEXT_PARAM_ENGINES(engines, 0);
+ struct drm_i915_gem_context_param p = {
+ .ctx_id = gem_context_create(i915),
+ .param = I915_CONTEXT_PARAM_ENGINES,
+ .value = to_user_pointer(&engines),
+ .size = sizeof(engines),
+ };
+ const struct intel_execution_engine2 *e;
+ unsigned int count = 0;
+
+ gem_context_set_param(i915, &p);
+
+ for_each_context_engine(i915, p.ctx_id, e)
+ count++;
+ igt_assert_eq(count, 0);
+
+ ____for_each_physical_engine(i915, p.ctx_id, e)
+ count++;
+ igt_assert_eq(count, 0);
+
+ gem_context_destroy(i915, p.ctx_id);
+}
I leave find a home and correcting the whitespace to the reader.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result
2020-02-14 18:54 ` Chris Wilson
@ 2020-02-14 19:14 ` Chris Wilson
0 siblings, 0 replies; 6+ messages in thread
From: Chris Wilson @ 2020-02-14 19:14 UTC (permalink / raw)
To: Antonio Argenziano, Dale B Stimson, igt-dev, intel-gfx
Quoting Chris Wilson (2020-02-14 18:54:43)
> +static void libapi(int i915)
> +{
> + I915_DEFINE_CONTEXT_PARAM_ENGINES(engines, 0);
I915_DEFINE_CONTEXT_PARAM_ENGINES(engines, 0) = {};
or
struct i915_gem_context_param_engines engines = {};
> + struct drm_i915_gem_context_param p = {
> + .ctx_id = gem_context_create(i915),
> + .param = I915_CONTEXT_PARAM_ENGINES,
> + .value = to_user_pointer(&engines),
> + .size = sizeof(engines),
> + };
> + const struct intel_execution_engine2 *e;
> + unsigned int count = 0;
> +
> + gem_context_set_param(i915, &p);
> +
> + for_each_context_engine(i915, p.ctx_id, e)
> + count++;
> + igt_assert_eq(count, 0);
Of course this says that this for_each_context_engine() loop doesn't
work anyway.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-02-14 19:15 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-13 19:26 [Intel-gfx] [PATCH i-g-t] lib/i915/gem_engine_topology.c - intel_get_current_engine invalid result Dale B Stimson
2020-02-13 20:44 ` Chris Wilson
2020-02-14 18:43 ` Antonio Argenziano
2020-02-14 18:44 ` Chris Wilson
2020-02-14 18:54 ` Chris Wilson
2020-02-14 19:14 ` Chris Wilson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).