Bug 109049

Previously we created 4147 contexts & submissions within a 2s setup period.

Moving the bug back to i915 because of the following issue:

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_168/fi-skl-6700k2/igt@kms_atomic_transition@plane-all-modeset-transition.html

Starting subtest: plane-all-modeset-transition
(kms_atomic_transition:1188) igt_kms-CRITICAL: Test assertion failure function do_display_commit, file ../lib/igt_kms.c:3320:
(kms_atomic_transition:1188) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_atomic_transition:1188) igt_kms-CRITICAL: Last errno: 28, No space left on device
(kms_atomic_transition:1188) igt_kms-CRITICAL: error: -28 != 0
Subtest plane-all-modeset-transition failed.

(In reply to Martin Peres from comment #2)
> Moving the bug back to i915 because of the following issue:
> 
> https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_168/fi-skl-6700k2/
> igt@kms_atomic_transition@plane-all-modeset-transition.html
> 
> Starting subtest: plane-all-modeset-transition
> (kms_atomic_transition:1188) igt_kms-CRITICAL: Test assertion failure
> function do_display_commit, file ../lib/igt_kms.c:3320:
> (kms_atomic_transition:1188) igt_kms-CRITICAL: Failed assertion: ret == 0
> (kms_atomic_transition:1188) igt_kms-CRITICAL: Last errno: 28, No space left
> on device
> (kms_atomic_transition:1188) igt_kms-CRITICAL: error: -28 != 0
> Subtest plane-all-modeset-transition failed.

Nothing to do with the amdgpu ENOSPC.

Now limited to 4095 contexts. Isn't that a coincidence!

Regression from

commit 08d1bdd4cc57e89d037205687a61d2b6ff9dddd4
Author: Rex Zhu <Rex.Zhu@amd.com>
Date:   Wed Oct 24 16:10:33 2018 +0800

    drm/amdgpu: Limit vm max ctx number to 4096
    
    driver need to reserve resource for each ctx for
    some hw features. so add this limitation.
    
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Rex Zhu <Rex.Zhu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

Stopped being so stringent about allocating so many contexts, and just focus on testing fence import:

commit 270da20849db4d170db09673c6b67712c90ec9fe (HEAD, upstream/master)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Dec 13 11:54:36 2018 +0000

    igt/amdgpu_amd_prime: Bail if we fail to create more contexts
    
    amdgpu has started to report out of space after creating a few contexts.
    This is not the scope of this test as here we are just verifying that
    fences created in amd can be imported and used for synchronisation by
    i915 and for that we just need at least one context created!
    
    References: https://bugs.freedesktop.org/show_bug.cgi?id=109049
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Antonio Argenziano <antonio.argenziano@intel.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>

(In reply to Chris Wilson from comment #6)
> Stopped being so stringent about allocating so many contexts, and just focus
> on testing fence import:
> 
> commit 270da20849db4d170db09673c6b67712c90ec9fe (HEAD, upstream/master)
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Thu Dec 13 11:54:36 2018 +0000
> 
>     igt/amdgpu_amd_prime: Bail if we fail to create more contexts
>     
>     amdgpu has started to report out of space after creating a few contexts.
>     This is not the scope of this test as here we are just verifying that
>     fences created in amd can be imported and used for synchronisation by
>     i915 and for that we just need at least one context created!
>     
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=109049
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Reviewed-by: Antonio Argenziano <antonio.argenziano@intel.com>
>     Acked-by: Alex Deucher <alexander.deucher@amd.com>

Thanks, it did the trick!

Archiving :)