From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] tests/i915/gem_exec_store: remove hard coded engine limit
Date: Fri, 14 Feb 2020 13:26:18 +0000 [thread overview]
Message-ID: <92a70cc5-b757-f9b5-0ac1-da8a3686266f@linux.intel.com> (raw)
In-Reply-To: <20200214130826.31004-1-matthew.auld@intel.com>
On 14/02/2020 13:08, Matthew Auld wrote:
> Prep for having an arbitrary context engine[], since that can be
> whatever we like.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Antonio Argenziano <antonio.argenziano@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> tests/i915/gem_exec_store.c | 33 +++++++++++++++++++++++++--------
> 1 file changed, 25 insertions(+), 8 deletions(-)
>
> diff --git a/tests/i915/gem_exec_store.c b/tests/i915/gem_exec_store.c
> index b74c3d84..eb511696 100644
> --- a/tests/i915/gem_exec_store.c
> +++ b/tests/i915/gem_exec_store.c
> @@ -180,25 +180,40 @@ static void store_all(int fd)
> const int gen = intel_gen(intel_get_drm_devid(fd));
> struct drm_i915_gem_exec_object2 obj[2];
> struct intel_execution_engine2 *engine;
> - struct drm_i915_gem_relocation_entry reloc[32];
> + struct drm_i915_gem_relocation_entry *reloc;
> struct drm_i915_gem_execbuffer2 execbuf;
> - unsigned engines[16], permuted[16];
> + unsigned *engines, *permuted;
> uint32_t batch[16];
> uint64_t offset;
> unsigned nengine;
> int value;
> int i, j;
>
> + nengine = 0;
> + __for_each_physical_engine(fd, engine) {
> + if (!gem_class_can_store_dword(fd, engine->class))
> + continue;
> + nengine++;
> + }
> +
> + reloc = calloc(2*nengine, sizeof(*reloc));
> + igt_assert(reloc);
> +
> + engines = calloc(nengine, sizeof(*engines));
> + igt_assert(engines);
> +
> + permuted = calloc(nengine, sizeof(*permuted));
> + igt_assert(permuted);
> +
> memset(&execbuf, 0, sizeof(execbuf));
> execbuf.buffers_ptr = to_user_pointer(obj);
> execbuf.buffer_count = 2;
> if (gen < 6)
> execbuf.flags |= I915_EXEC_SECURE;
>
> - memset(reloc, 0, sizeof(reloc));
> memset(obj, 0, sizeof(obj));
> - obj[0].handle = gem_create(fd, 4096);
> - obj[1].handle = gem_create(fd, 4096);
> + obj[0].handle = gem_create(fd, nengine*sizeof(uint32_t));
> + obj[1].handle = gem_create(fd, 2*nengine*sizeof(batch));
> obj[1].relocation_count = 1;
>
> offset = sizeof(uint32_t);
> @@ -224,8 +239,6 @@ static void store_all(int fd)
> if (!gem_class_can_store_dword(fd, engine->class))
> continue;
>
> - igt_assert(2*(nengine+1)*sizeof(batch) <= 4096);
> -
> execbuf.flags &= ~ENGINE_MASK;
> execbuf.flags |= engine->flags;
>
> @@ -281,12 +294,16 @@ static void store_all(int fd)
> }
> gem_close(fd, obj[1].handle);
>
> - gem_read(fd, obj[0].handle, 0, engines, sizeof(engines));
> + gem_read(fd, obj[0].handle, 0, engines, nengine*sizeof(engines[0]));
> gem_close(fd, obj[0].handle);
>
> for (i = 0; i < nengine; i++)
> igt_assert_eq_u32(engines[i], i);
> igt_assert_eq(intel_detect_and_clear_missed_interrupts(fd), 0);
> +
> + free(permuted);
> + free(engines);
> + free(reloc);
> }
>
> static int print_welcome(int fd)
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-14 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 13:08 [Intel-gfx] [PATCH] tests/i915/gem_exec_store: remove hard coded engine limit Matthew Auld
2020-02-14 13:26 ` Tvrtko Ursulin [this message]
2020-02-14 13:34 ` Chris Wilson
2020-02-14 18:35 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " 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=92a70cc5-b757-f9b5-0ac1-da8a3686266f@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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;
as well as URLs for NNTP newsgroup(s).