From: Dale B Stimson <dale.b.stimson@intel.com>
To: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: [igt-dev] [PATCH i-g-t 0/2] i915/gem_ctx_isolation: __for_each_physical_engine + engine mapping
Date: Wed, 22 Jan 2020 15:26:55 -0800 [thread overview]
Message-ID: <cover.1579731227.git.dale.b.stimson@intel.com> (raw)
i915/gem_ctx_isolation: __for_each_physical_engine and gem_engine_topology
Use __for_each_physical_engine with gem_engine_topology.
Iterates through the definitive list of all engines
present. All contexts have their engine mapping set via
gem_context_set_all_engines().
Patch 1 was originally posted by Ramalingam C <ramalingam.c@intel.com>.
Since then, slight modifications have been done to it due to
upstream changes. Patch 1 is being kept separate from patch 2 in
order to assure proper attribution to the author.
Dale B Stimson (1):
DBS: tests/i915/gem_ctx_isolation: use the gem_engine_topology
library, part 2
Ramalingam C (1):
tests/i915/gem_ctx_isolation: use the gem_engine_topology library,
part 1
tests/i915/gem_ctx_isolation.c | 66 ++++++++++++++++++++++------------
1 file changed, 43 insertions(+), 23 deletions(-)
--
2.25.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-01-22 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 23:26 Dale B Stimson [this message]
2020-01-22 23:26 ` [igt-dev] [PATCH i-g-t 1/2] tests/i915/gem_ctx_isolation: use the gem_engine_topology library, part 1 Dale B Stimson
2020-01-22 23:26 ` [igt-dev] [PATCH i-g-t 2/2] DBS: tests/i915/gem_ctx_isolation: use the gem_engine_topology library, part 2 Dale B Stimson
2020-01-23 9:09 ` Chris Wilson
2020-01-23 15:59 ` Tvrtko Ursulin
2020-01-23 19:21 ` Dale B Stimson
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=cover.1579731227.git.dale.b.stimson@intel.com \
--to=dale.b.stimson@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@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