From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
Intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t] tests/i915/gem_ctx_persistence: Convert engine subtests to dynamic
Date: Thu, 30 Jan 2020 21:17:10 +0000 [thread overview]
Message-ID: <158041903003.20421.14685928348321853302@skylake-alporthouse-com> (raw)
In-Reply-To: <f12e30f0-a287-f821-4bc4-c7545e9821b6@linux.intel.com>
Quoting Tvrtko Ursulin (2020-01-30 20:56:23)
>
> On 30/01/2020 20:47, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2020-01-30 20:41:24)
> > Then I had a plan to add the pathological engines[] here.
>
> Will see later what you exactly mean.
for_each_gem_engine(ce, __context_engines_static(ctx), it) {
struct intel_engine_cs *engine;
if (intel_context_set_banned(ce))
continue;
engine = active_engine(ce);
That's the bit I want to try and confuse.
So 1..64xrcs0, 1...64xVirtual and make sure it kills the right active
context.
I hope I had such nastiness in mind while writing, so hopefully there's
no hole here.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
Intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] tests/i915/gem_ctx_persistence: Convert engine subtests to dynamic
Date: Thu, 30 Jan 2020 21:17:10 +0000 [thread overview]
Message-ID: <158041903003.20421.14685928348321853302@skylake-alporthouse-com> (raw)
In-Reply-To: <f12e30f0-a287-f821-4bc4-c7545e9821b6@linux.intel.com>
Quoting Tvrtko Ursulin (2020-01-30 20:56:23)
>
> On 30/01/2020 20:47, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2020-01-30 20:41:24)
> > Then I had a plan to add the pathological engines[] here.
>
> Will see later what you exactly mean.
for_each_gem_engine(ce, __context_engines_static(ctx), it) {
struct intel_engine_cs *engine;
if (intel_context_set_banned(ce))
continue;
engine = active_engine(ce);
That's the bit I want to try and confuse.
So 1..64xrcs0, 1...64xVirtual and make sure it kills the right active
context.
I hope I had such nastiness in mind while writing, so hopefully there's
no hole here.
-Chris
_______________________________________________
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 21:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 20:41 [Intel-gfx] [PATCH i-g-t] tests/i915/gem_ctx_persistence: Convert engine subtests to dynamic Tvrtko Ursulin
2020-01-30 20:41 ` [igt-dev] " Tvrtko Ursulin
2020-01-30 20:44 ` [Intel-gfx] " Tvrtko Ursulin
2020-01-30 20:44 ` Tvrtko Ursulin
2020-01-30 20:50 ` [Intel-gfx] " Chris Wilson
2020-01-30 20:50 ` [igt-dev] [Intel-gfx] " Chris Wilson
2020-01-30 20:47 ` Chris Wilson
2020-01-30 20:47 ` [igt-dev] " Chris Wilson
2020-01-30 20:56 ` Tvrtko Ursulin
2020-01-30 20:56 ` [igt-dev] " Tvrtko Ursulin
2020-01-30 21:17 ` Chris Wilson [this message]
2020-01-30 21:17 ` Chris Wilson
2020-01-30 20:52 ` [Intel-gfx] [PATCH i-g-t v2] " Tvrtko Ursulin
2020-01-30 20:56 ` Chris Wilson
2020-01-30 20:56 ` [igt-dev] " Chris Wilson
2020-01-30 20:59 ` Tvrtko Ursulin
2020-01-30 20:59 ` [igt-dev] " Tvrtko Ursulin
2020-01-30 20:56 ` [igt-dev] ✗ GitLab.Pipeline: failure for " Patchwork
2020-01-30 21:01 ` [Intel-gfx] [PATCH i-g-t v3] " Tvrtko Ursulin
2020-01-30 21:01 ` [igt-dev] " Tvrtko Ursulin
2020-01-30 21:07 ` [Intel-gfx] " Chris Wilson
2020-01-30 21:07 ` Chris Wilson
2020-01-30 21:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-01-30 21:26 ` [igt-dev] ✗ GitLab.Pipeline: failure for tests/i915/gem_ctx_persistence: Convert engine subtests to dynamic (rev3) Patchwork
2020-01-30 21:33 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-02-02 12:49 ` [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=158041903003.20421.14685928348321853302@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=krishnaiah.bommu@intel.com \
--cc=tvrtko.ursulin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.