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 09/14] test/i915: gem_ctx_exec: use the gem_engine_topology library
Date: Mon, 13 May 2019 11:46:48 +0100	[thread overview]
Message-ID: <8b2a8f81-170f-e74d-f89c-4920b32846e1@linux.intel.com> (raw)
In-Reply-To: <20190513004508.8042-10-andi@etezian.org>


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>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
>   tests/i915/gem_ctx_exec.c | 15 +++++++--------
>   1 file changed, 7 insertions(+), 8 deletions(-)
> 
> diff --git a/tests/i915/gem_ctx_exec.c b/tests/i915/gem_ctx_exec.c
> index b8e0e0743892..c3543bfe5dd1 100644
> --- a/tests/i915/gem_ctx_exec.c
> +++ b/tests/i915/gem_ctx_exec.c
> @@ -111,7 +111,8 @@ static void big_exec(int fd, uint32_t handle, int ring)
>   	gem_sync(fd, handle);
>   }
>   
> -static void invalid_context(int fd, unsigned ring, uint32_t handle)
> +static void invalid_context(int fd, struct intel_execution_engine2 *e,
> +			    uint32_t handle)
>   {
>   	struct drm_i915_gem_exec_object2 obj = {
>   		.handle = handle,
> @@ -119,7 +120,7 @@ static void invalid_context(int fd, unsigned ring, uint32_t handle)
>   	struct drm_i915_gem_execbuffer2 execbuf = {
>   		.buffers_ptr = to_user_pointer(&obj),
>   		.buffer_count = 1,
> -		.flags = ring,
> +		.flags = e->flags,
>   	};
>   	unsigned int i;
>   	uint32_t ctx;
> @@ -198,7 +199,7 @@ static void norecovery(int i915)
>   igt_main
>   {
>   	const uint32_t batch[2] = { 0, MI_BATCH_BUFFER_END };
> -	const struct intel_execution_engine *e;
> +	struct intel_execution_engine2 *e;

I think if you added const new parameter in invalid_context this one 
here would be able to stay. It would have been nicer I think but never mind.

>   	uint32_t handle;
>   	uint32_t ctx_id;
>   	int fd;
> @@ -228,11 +229,9 @@ igt_main
>   		gem_sync(fd, handle);
>   	}
>   
> -	for (e = intel_execution_engines; e->name; e++) {
> -		igt_subtest_f("basic-invalid-context-%s", e->name) {
> -			gem_require_ring(fd, e->exec_id | e->flags);
> -			invalid_context(fd, e->exec_id | e->flags, handle);
> -		}
> +	__for_each_physical_engine(fd, e) {
> +		igt_subtest_f("basic-invalid-context-%s", e->name)
> +			invalid_context(fd, e, handle);
>   	}
>   
>   	igt_subtest("eviction")
> 
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

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

  reply	other threads:[~2019-05-13 10:46 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 [this message]
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
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=8b2a8f81-170f-e74d-f89c-4920b32846e1@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