From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t 1/2] i915/query: Cross-check engine list against execbuf interface
Date: Tue, 8 Dec 2020 13:56:33 +0200 [thread overview]
Message-ID: <X89p8cxixzgFd8tn@intel.intel> (raw)
In-Reply-To: <20201207161150.1841453-1-chris@chris-wilson.co.uk>
Hi Chris,
> - /* Check results match the legacy GET_PARAM (where we can). */
> + /* Confirm the individual engines exist with EXECBUFFER2 */
> for (i = 0; i < engines->num_engines; i++) {
> struct drm_i915_engine_info *engine =
> (struct drm_i915_engine_info *)&engines->engines[i];
> + I915_DEFINE_CONTEXT_PARAM_ENGINES(p_engines, 1) = {
> + .engines = { engine->engine }
> + };
> + struct drm_i915_gem_context_param param = {
> + .param = I915_CONTEXT_PARAM_ENGINES,
> + .value = to_user_pointer(&p_engines),
> + .size = sizeof(p_engines),
> + };
> +
> + struct drm_i915_gem_exec_object2 obj = {};
> + struct drm_i915_gem_execbuffer2 execbuf = {
> + .buffers_ptr = to_user_pointer(&obj),
> + .buffer_count = 1,
> + };
>
> igt_debug("%u: class=%u instance=%u flags=%llx capabilities=%llx\n",
> i,
> @@ -689,6 +713,15 @@ static void engines(int fd)
> engine->engine.engine_instance,
> engine->flags,
> engine->capabilities);
> + gem_context_set_param(fd, ¶m);
> + igt_assert_eq(__gem_execbuf(fd, &execbuf), -ENOENT);
> + }
> + gem_context_reset_engines(fd, 0);
> +
> + /* Check results match the legacy GET_PARAM (where we can). */
> + for (i = 0; i < engines->num_engines; i++) {
> + struct drm_i915_engine_info *engine =
> + (struct drm_i915_engine_info *)&engines->engines[i];
I would have liked it with one single for loop, perhaps resetting
engines individually.
But this works, as well and I'm not strong with this:
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-12-08 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 16:11 [igt-dev] [PATCH i-g-t 1/2] i915/query: Cross-check engine list against execbuf interface Chris Wilson
2020-12-07 16:11 ` [igt-dev] [PATCH i-g-t 2/2] i915/query: Directly check query results against GETPARAM Chris Wilson
2020-12-08 11:04 ` Petri Latvala
2020-12-08 11:18 ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2020-12-08 11:31 ` Chris Wilson
2020-12-07 17:40 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] i915/query: Cross-check engine list against execbuf interface Patchwork
2020-12-07 19:47 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-12-08 11:01 ` Petri Latvala
2020-12-08 11:56 ` Andi Shyti [this message]
2020-12-09 5:51 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=X89p8cxixzgFd8tn@intel.intel \
--to=andi.shyti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@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