[igt-dev] [Intel-gfx] [PATCH i-g-t] igt/gem_eio: Make reset-stress safe

[Antonio Argenziano]

On 15/06/18 11:56, Chris Wilson wrote:
> As we hang ctx0 quite frequently, it needs to be harden against being
> banned.
> 
> Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala at intel.com>

For some reason I thought we had more hang stress tests.

Reviewed-by: Antonio Argenziano <antonio.argenziano at intel.com>

> ---
>   tests/gem_eio.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/gem_eio.c b/tests/gem_eio.c
> index e1aff639d..5faf7502b 100644
> --- a/tests/gem_eio.c
> +++ b/tests/gem_eio.c
> @@ -642,7 +642,7 @@ static void test_inflight_internal(int fd, unsigned int wait)
>    */
>   static void test_reset_stress(int fd, unsigned int flags)
>   {
> -	uint32_t ctx0 = gem_context_create(fd);
> +	uint32_t ctx0 = context_create_safe(fd);

I guess until (before Mika's patch) now we were covered by 'ctx'
being created and destroyed all the time.

Thanks,
Antonio

>   
>   	igt_until_timeout(5) {
>   		struct drm_i915_gem_execbuffer2 execbuf = { };
>