From: Andi Shyti via igt-dev <igt-dev@lists.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: IGT dev <igt-dev@lists.freedesktop.org>,
Andi Shyti <andi@etezian.org>,
Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [RFC PATCH v8 5/5] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test
Date: Wed, 13 Feb 2019 03:02:36 +0200 [thread overview]
Message-ID: <20190213010236.GB4740@intel.intel> (raw)
In-Reply-To: <155001739294.13414.4413937487335739365@skylake-alporthouse-com>
Hi Chris,
> > + igt_subtest("exec-ctx") {
> > + uint32_t ctx_id;
> > + struct intel_execution_engine2 *e2;
> > + int index_map = 0;
> > +
> > + igt_require_gem_engine_list(fd);
> > + ctx_id = gem_context_create(fd);
> > +
> > + for_each_engine2(fd, ctx_id, e2)
> > + igt_assert(gem_has_ring_by_idx(fd, ++index_map,
> > + ctx_id));
>
> Since the iterator here is e2, it looks quite abusive not to use the
> iterator... I don't think this serves as a good example of
> for_each_engine2().
I thought about hiding e2 inside for_each_engine2, but I also
thought the user might want to use it, e.g.:
for_each_engine2(fd, ctx_id, e2)
printf("%s\n", e2->name);
if I keep it hidden then, although it's there, it's not visible.
But, yes, I can hide it inside the for_each_engine2 and perhaps
have another iterator where e2 is meant to be used.
Thanks,
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-13 1:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 23:54 [igt-dev] [RFC PATCH v8 0/5] new engine discovery interface Andi Shyti via igt-dev
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 1/5] include/drm-uapi: import i915_drm.h header file Andi Shyti via igt-dev
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 2/5] lib/i915: add gem_query library Andi Shyti via igt-dev
2019-02-13 0:13 ` Chris Wilson
2019-02-13 0:55 ` Andi Shyti via igt-dev
2019-02-13 9:19 ` Chris Wilson
2019-02-13 9:55 ` Andi Shyti via igt-dev
2019-02-13 10:00 ` Chris Wilson
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 3/5] lib/igt_gt: use for_each_engine2 to loop through engines Andi Shyti via igt-dev
2019-02-13 0:16 ` Chris Wilson
2019-02-13 1:19 ` Andi Shyti via igt-dev
2019-02-13 9:20 ` Chris Wilson
2019-02-13 11:07 ` Andi Shyti via igt-dev
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 4/5] lib: ioctl_wrappers: reach engines by index as well Andi Shyti via igt-dev
2019-02-13 0:19 ` Chris Wilson
2019-02-13 1:11 ` Andi Shyti via igt-dev
2019-02-13 9:22 ` Chris Wilson
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 5/5] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti via igt-dev
2019-02-13 0:23 ` Chris Wilson
2019-02-13 1:02 ` Andi Shyti via igt-dev [this message]
2019-02-13 0:28 ` [igt-dev] ✓ Fi.CI.BAT: success for new engine discovery interface Patchwork
2019-02-13 2:44 ` [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=20190213010236.GB4740@intel.intel \
--to=igt-dev@lists.freedesktop.org \
--cc=andi.shyti@intel.com \
--cc=andi@etezian.org \
--cc=chris@chris-wilson.co.uk \
--cc=petri.latvala@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