Re: [PATCH i-g-t 01/16] i915/gem_exec_schedule: Semaphore priority fixups

Tvrtko Ursulin
2019-05-14T09:39:01Z

On 08/05/2019 11:09, Chris Wilson wrote:
> A stray git add from my test boxen -- we were being careful enough to
> preserve priority and ordering to match the implicit policies.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> tests/i915/gem_exec_schedule.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/i915/gem_exec_schedule.c b/tests/i915/gem_exec_schedule.c
> index 330e8a54e..77a264a6a 100644
> --- a/tests/i915/gem_exec_schedule.c
> +++ b/tests/i915/gem_exec_schedule.c
> @@ -507,6 +507,7 @@ static void semaphore_resolve(int i915)
> uint32_t handle, cancel;
> uint32_t *cs, *map;
> igt_spin_t *spin;
> + int64_t poke = 1;
>
> if (!gem_can_store_dword(i915, engine))
> continue;
> @@ -587,6 +588,7 @@ static void semaphore_resolve(int i915)
> eb.buffer_count = 2;
> eb.rsvd1 = inner;
> gem_execbuf(i915, &eb);
> + gem_wait(i915, cancel, &poke);
> gem_close(i915, cancel);
>
> gem_sync(i915, handle); /* To hang unless cancel runs! */
>

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

Regards,

Tvrtko