public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi@etezian.org>, IGT dev <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH v23 10/14] test/i915: gem_exec_basic: use the gem_engine_topology library
Date: Mon, 13 May 2019 11:53:57 +0100	[thread overview]
Message-ID: <28e6bfda-fb52-9bb2-eb54-bdfee1e8c4cc@linux.intel.com> (raw)
In-Reply-To: <770d9a7f-ad59-b2f9-124d-12cc70e2a0ba@linux.intel.com>


On 13/05/2019 11:50, Tvrtko Ursulin wrote:
> 
> On 13/05/2019 01:45, Andi Shyti wrote:
>> From: Andi Shyti <andi.shyti@intel.com>
>>
>> Replace the legacy for_each_engine* defines with the ones
>> implemented in the gem_engine_topology library.
>>
>> Signed-off-by: Andi Shyti <andi.shyti@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> ---
>>   tests/i915/gem_exec_basic.c | 28 ++++++++++++++--------------
>>   1 file changed, 14 insertions(+), 14 deletions(-)
>>
>> diff --git a/tests/i915/gem_exec_basic.c b/tests/i915/gem_exec_basic.c
>> index dcb83864b1c1..140cbdbc66a5 100644
>> --- a/tests/i915/gem_exec_basic.c
>> +++ b/tests/i915/gem_exec_basic.c
>> @@ -42,12 +42,12 @@ static void batch_fini(int fd, uint32_t handle)
>>       gem_close(fd, handle);
>>   }
>> -static void noop(int fd, unsigned ring)
>> +static void noop(int fd, uint64_t flags)
>>   {
>>       struct drm_i915_gem_execbuffer2 execbuf;
>>       struct drm_i915_gem_exec_object2 exec;
>> -    gem_require_ring(fd, ring);
>> +    gem_require_ring(fd, flags);
> 
> gem_require_ring cannot support new engines, no?

It can. :)

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

Tvrtko

> 
> Regards,
> 
> Tvrtko
> 
>>       memset(&exec, 0, sizeof(exec));
>> @@ -56,18 +56,18 @@ static void noop(int fd, unsigned ring)
>>       memset(&execbuf, 0, sizeof(execbuf));
>>       execbuf.buffers_ptr = to_user_pointer(&exec);
>>       execbuf.buffer_count = 1;
>> -    execbuf.flags = ring;
>> +    execbuf.flags = flags;
>>       gem_execbuf(fd, &execbuf);
>>       batch_fini(fd, exec.handle);
>>   }
>> -static void readonly(int fd, unsigned ring)
>> +static void readonly(int fd, uint64_t flags)
>>   {
>>       struct drm_i915_gem_execbuffer2 *execbuf;
>>       struct drm_i915_gem_exec_object2 exec;
>> -    gem_require_ring(fd, ring);
>> +    gem_require_ring(fd, flags);
>>       memset(&exec, 0, sizeof(exec));
>>       exec.handle = batch_create(fd);
>> @@ -77,7 +77,7 @@ static void readonly(int fd, unsigned ring)
>>       execbuf->buffers_ptr = to_user_pointer(&exec);
>>       execbuf->buffer_count = 1;
>> -    execbuf->flags = ring;
>> +    execbuf->flags = flags;
>>       igt_assert(mprotect(execbuf, 4096, PROT_READ) == 0);
>>       gem_execbuf(fd, execbuf);
>> @@ -87,13 +87,13 @@ static void readonly(int fd, unsigned ring)
>>       batch_fini(fd, exec.handle);
>>   }
>> -static void gtt(int fd, unsigned ring)
>> +static void gtt(int fd, uint64_t flags)
>>   {
>>       struct drm_i915_gem_execbuffer2 *execbuf;
>>       struct drm_i915_gem_exec_object2 *exec;
>>       uint32_t handle;
>> -    gem_require_ring(fd, ring);
>> +    gem_require_ring(fd, flags);
>>       handle = gem_create(fd, 4096);
>> @@ -106,7 +106,7 @@ static void gtt(int fd, unsigned ring)
>>       execbuf->buffers_ptr = to_user_pointer(exec);
>>       execbuf->buffer_count = 1;
>> -    execbuf->flags = ring;
>> +    execbuf->flags = flags;
>>       gem_execbuf(fd, execbuf);
>> @@ -116,7 +116,7 @@ static void gtt(int fd, unsigned ring)
>>   igt_main
>>   {
>> -    const struct intel_execution_engine *e;
>> +    const struct intel_execution_engine2 *e;
>>       int fd = -1;
>>       igt_fixture {
>> @@ -126,13 +126,13 @@ igt_main
>>           igt_fork_hang_detector(fd);
>>       }
>> -    for (e = intel_execution_engines; e->name; e++) {
>> +    __for_each_physical_engine(fd, e) {
>>           igt_subtest_f("basic-%s", e->name)
>> -            noop(fd, e->exec_id | e->flags);
>> +            noop(fd, e->flags);
>>           igt_subtest_f("readonly-%s", e->name)
>> -            readonly(fd, e->exec_id | e->flags);
>> +            readonly(fd, e->flags);
>>           igt_subtest_f("gtt-%s", e->name)
>> -            gtt(fd, e->exec_id | e->flags);
>> +            gtt(fd, e->flags);
>>       }
>>       igt_fixture {
>>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-05-13 10:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13  0:44 [igt-dev] [PATCH v23 00/14] new engine discovery interface Andi Shyti
2019-05-13  0:44 ` [igt-dev] [PATCH v23 01/14] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-05-13  0:44 ` [igt-dev] [PATCH v23 02/14] lib/i915: add gem_engine_topology library and for_each loop definition Andi Shyti
2019-05-13  0:44 ` [igt-dev] [PATCH v23 03/14] lib: igt_gt: add execution buffer flags to class helper Andi Shyti
2019-05-13  0:44 ` [igt-dev] [PATCH v23 04/14] lib: igt_gt: make gem_engine_can_store_dword() check engine class Andi Shyti
2019-05-13  0:44 ` [igt-dev] [PATCH v23 05/14] lib: igt_dummyload: use for_each_context_engine() Andi Shyti
2019-05-13  0:45 ` [igt-dev] [PATCH v23 06/14] test: perf_pmu: use the gem_engine_topology library Andi Shyti
2019-05-13  9:03   ` Tvrtko Ursulin
2019-05-13 11:57   ` Chris Wilson
2019-05-13 14:15     ` Andi Shyti
2019-05-13 14:17       ` Chris Wilson
2019-05-13  0:45 ` [igt-dev] [PATCH v23 07/14] test/i915: gem_busy: " Andi Shyti
2019-05-13 10:42   ` Tvrtko Ursulin
2019-05-13 10:58     ` Chris Wilson
2019-05-13  0:45 ` [igt-dev] [PATCH v23 08/14] test/i915: gem_cs_tlb: " Andi Shyti
2019-05-13 10:43   ` Tvrtko Ursulin
2019-05-13  0:45 ` [igt-dev] [PATCH v23 09/14] test/i915: gem_ctx_exec: " Andi Shyti
2019-05-13 10:46   ` Tvrtko Ursulin
2019-05-13  0:45 ` [igt-dev] [PATCH v23 10/14] test/i915: gem_exec_basic: " Andi Shyti
2019-05-13 10:50   ` Tvrtko Ursulin
2019-05-13 10:53     ` Tvrtko Ursulin [this message]
2019-05-13  0:45 ` [igt-dev] [PATCH v23 11/14] test/i915: gem_exec_parallel: " Andi Shyti
2019-05-13 10:56   ` Tvrtko Ursulin
2019-05-13  0:45 ` [igt-dev] [PATCH v23 12/14] test/i915: gem_exec_store: " Andi Shyti
2019-05-13 11:44   ` Tvrtko Ursulin
2019-05-13 11:46   ` Tvrtko Ursulin
2019-05-13  0:45 ` [igt-dev] [PATCH v23 13/14] test/i915: gem_wait: " Andi Shyti
2019-05-13 11:46   ` Tvrtko Ursulin
2019-05-13  0:45 ` [igt-dev] [PATCH v23 14/14] test/i915: i915_hangman: " Andi Shyti
2019-05-13 11:49   ` Tvrtko Ursulin
2019-05-13  2:23 ` [igt-dev] ✓ Fi.CI.BAT: success for new engine discovery interface Patchwork
2019-05-13  3:27 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-05-13  9:04 ` [igt-dev] [PATCH v23 00/14] " Tvrtko Ursulin
2019-05-13  9:43   ` 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=28e6bfda-fb52-9bb2-eb54-bdfee1e8c4cc@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=andi@etezian.org \
    --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