public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: IGT dev <igt-dev@lists.freedesktop.org>, Andi Shyti <andi@etezian.org>
Subject: Re: [igt-dev] [RFC PATCH v6 2/4] lib: implement new engine discovery interface
Date: Fri, 8 Feb 2019 14:55:42 +0200	[thread overview]
Message-ID: <20190208125542.GA4420@intel.intel> (raw)
In-Reply-To: <154944546968.31771.14331690484230080470@skylake-alporthouse-com>

Hi Chris,

Thanks for the review!

I think fixed everything, just a few questions on the following

> > @@ -1459,6 +1460,8 @@ void igt_require_gem(int fd)
> >         err = 0;
> >         if (ioctl(fd, DRM_IOCTL_I915_GEM_THROTTLE))
> >                 err = -errno;
> > +       else
> > +               gem_init_engine_list(fd);
> 
> igt_require_gem() maybe called multiple times per subtest.

I'm actually checking that with:

        if (intel_execution_engines2)
                return;

inside the gem_init_engine_list(). Shouldn't that be enough to
prevent multiple calls?

> Just gem_require_engine_list() ? Gives a good indicator which tests are
> converted and which not, and a reminder that we still need to test
> legacy ABIs in conjunction with the new era.

Can do that, but I thought that in the new era, when your and
Tvrtko's patch will get in, we will convert everything to the new
ABI's and this would remain an extra step (which BTW, wouldn't
prevent multiple calls either, as above).

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

  reply	other threads:[~2019-02-08 12:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  9:18 [igt-dev] [RFC PATCH v6 0/4] new engine discovery interface Andi Shyti
2019-02-06  9:18 ` [igt-dev] [RFC PATCH v6 1/4] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-02-06  9:18 ` [igt-dev] [RFC PATCH v6 2/4] lib: implement new engine discovery interface Andi Shyti
2019-02-06  9:31   ` Chris Wilson
2019-02-08 12:55     ` Andi Shyti [this message]
2019-02-08 13:03       ` Chris Wilson
2019-02-06 18:11   ` Antonio Argenziano
2019-02-08 11:03     ` Andi Shyti
2019-02-08 11:06       ` Chris Wilson
2019-02-06  9:18 ` [igt-dev] [RFC PATCH v6 3/4] lib: ioctl_wrappers: reach engines by index as well Andi Shyti
2019-02-06  9:33   ` Chris Wilson
2019-02-06  9:18 ` [igt-dev] [RFC PATCH v6 4/4] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti
2019-02-06  9:25 ` [igt-dev] ✗ Fi.CI.BAT: failure for new engine discovery interface (rev7) Patchwork
2019-02-07  8:58   ` Petri Latvala
2019-02-08 10:56     ` Andi Shyti
2019-02-12  8:43     ` Tvrtko Ursulin via igt-dev
2019-02-12 11:39       ` Arkadiusz Hiler via igt-dev
2019-02-12 11:56         ` Tvrtko Ursulin via igt-dev
2019-02-15  9:50       ` Petri Latvala via igt-dev
2019-02-25 13:22         ` Tvrtko Ursulin
2019-02-26  9:32           ` Petri Latvala

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=20190208125542.GA4420@intel.intel \
    --to=andi.shyti@intel.com \
    --cc=andi@etezian.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    /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