public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "Latvala, Petri" <petri.latvala@intel.com>,
	"tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915: Use engine query interface for gem_ctx_isolation/persistence
Date: Wed, 4 Dec 2019 19:05:12 +0000	[thread overview]
Message-ID: <51b5ad4f3363fcc0948d123407371349b5342524.camel@intel.com> (raw)
In-Reply-To: <20191204145323.GA25209@platvala-desk.ger.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2932 bytes --]

On Wed, 2019-12-04 at 16:53 +0200, Petri Latvala wrote:
> On Wed, Dec 04, 2019 at 09:36:11AM +0000, Tvrtko Ursulin wrote:
> > 
> > On 03/12/2019 05:11, Stuart Summers wrote:
> > > Align with gem_exec_basic and other tests using the newer
> > > engine query interface into i915 to enumerate active engines.
> > > 
> > > Signed-off-by: Stuart Summers <stuart.summers@intel.com>
> > > ---
> > >   tests/i915/gem_ctx_isolation.c   | 4 ++--
> > >   tests/i915/gem_ctx_persistence.c | 2 +-
> > >   2 files changed, 3 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/tests/i915/gem_ctx_isolation.c
> > > b/tests/i915/gem_ctx_isolation.c
> > > index 6aa27133..9435209e 100644
> > > --- a/tests/i915/gem_ctx_isolation.c
> > > +++ b/tests/i915/gem_ctx_isolation.c
> > > @@ -856,6 +856,7 @@ static unsigned int
> > > __has_context_isolation(int fd)
> > >   igt_main
> > >   {
> > > +	struct intel_execution_engine2 *e;
> > >   	unsigned int has_context_isolation = 0;
> > >   	int fd = -1;
> > > @@ -876,8 +877,7 @@ igt_main
> > >   		igt_skip_on(gen > LAST_KNOWN_GEN);
> > >   	}
> > > -	for (const struct intel_execution_engine2 *e =
> > > intel_execution_engines2;
> > > -	     e->name; e++) {
> > > +	__for_each_physical_engine(fd, e) {
> > >   		igt_subtest_group {
> > >   			igt_fixture {
> > >   				igt_require(has_context_isolati
> > > on & (1 << e->class));
> > > diff --git a/tests/i915/gem_ctx_persistence.c
> > > b/tests/i915/gem_ctx_persistence.c
> > > index d68431ae..30772159 100644
> > > --- a/tests/i915/gem_ctx_persistence.c
> > > +++ b/tests/i915/gem_ctx_persistence.c
> > > @@ -727,7 +727,7 @@ igt_main
> > >   	igt_subtest("hangcheck")
> > >   		test_nohangcheck_hostile(i915);
> > > -	__for_each_static_engine(e) {
> > > +	__for_each_physical_engine(i915, e) {
> > >   		igt_subtest_group {
> > >   			igt_fixture {
> > >   				gem_require_ring(i915, e-
> > > >flags);
> > > 
> > 
> > __for_each_static_engine is correct, at least if you don't want CI
> > folks go
> > look for their pitchforks. :) Same for the first hunk, everything
> > that
> > enumerates subtests needs to be static.
> > 
> > Option 2, the preferred one - convert the tests to
> > igt_subtest_with_dynamic
> > and then you can use __for_each_physical_engine.
> 
> Doesn't __for_each_physical_engine anyway have a hack for being
> called in that context?
> 
> Btw, option 2 is 
> https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/44
> 
> Currently blocking that effort is getting
> https://patchwork.freedesktop.org/series/70286/ into shape.

Wait I'm a little confused, sorry for the naivete here. Does this mean
these kinds of changes are blocked on the above series? Or are you
saying I should go ahead and convert this to the dynamic subtests? Or
that we can move forward with the current approach and convert at a
later time?

Thanks,
Stuart

> 
> 

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3270 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-12-04 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  5:11 [igt-dev] [PATCH i-g-t] tests/i915: Use engine query interface for gem_ctx_isolation/persistence Stuart Summers
2019-12-03  6:03 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2019-12-03 18:31   ` Summers, Stuart
2019-12-04  9:36 ` [igt-dev] [PATCH i-g-t] " Tvrtko Ursulin
2019-12-04 14:53   ` Petri Latvala
2019-12-04 19:05     ` Summers, Stuart [this message]
2019-12-05  9:01       ` Petri Latvala
2019-12-05  9:22         ` Tvrtko Ursulin
2019-12-05  9:47           ` Andi Shyti
2019-12-05  9:54             ` Tvrtko Ursulin
2019-12-05 10:09               ` Petri Latvala
2019-12-05 10:23                 ` Tvrtko Ursulin
2019-12-05 22:07                   ` Summers, Stuart
2019-12-05 10:12               ` Andi Shyti

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=51b5ad4f3363fcc0948d123407371349b5342524.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox