[PATCH] drm/ci: Add msm tests

Abhinav Kumar quic_abhinavk at quicinc.com
Mon Jan 8 22:58:16 UTC 2024



On 1/8/2024 11:50 AM, Rob Clark wrote:
> From: Rob Clark <robdclark at chromium.org>
> 
> The msm tests should skip on non-msm hw, so I think it should be safe to
> enable everywhere.
> 
> Signed-off-by: Rob Clark <robdclark at chromium.org>
> ---
>   drivers/gpu/drm/ci/testlist.txt | 49 +++++++++++++++++++++++++++++++++
>   1 file changed, 49 insertions(+)
> 

I do see that all these tests use igt_msm_dev_open() to make sure it 
opens only the MSM card.

But if igt_msm_dev_open() fails, I dont see a igt_require() on some of 
the tests to skip them. So how will it safely skip on non-msm HW?

Unless i am missing something here ....

> diff --git a/drivers/gpu/drm/ci/testlist.txt b/drivers/gpu/drm/ci/testlist.txt
> index f82cd90372f4..eaeb751bb0ad 100644
> --- a/drivers/gpu/drm/ci/testlist.txt
> +++ b/drivers/gpu/drm/ci/testlist.txt
> @@ -2910,3 +2910,52 @@ kms_writeback at writeback-invalid-parameters
>   kms_writeback at writeback-fb-id
>   kms_writeback at writeback-check-output
>   prime_mmap_kms at buffer-sharing
> +msm_shrink at copy-gpu-sanitycheck-8
> +msm_shrink at copy-gpu-sanitycheck-32
> +msm_shrink at copy-gpu-8
> +msm_shrink at copy-gpu-32
> +msm_shrink at copy-gpu-madvise-8
> +msm_shrink at copy-gpu-madvise-32
> +msm_shrink at copy-gpu-oom-8
> +msm_shrink at copy-gpu-oom-32
> +msm_shrink at copy-mmap-sanitycheck-8
> +msm_shrink at copy-mmap-sanitycheck-32
> +msm_shrink at copy-mmap-8
> +msm_shrink at copy-mmap-32
> +msm_shrink at copy-mmap-madvise-8
> +msm_shrink at copy-mmap-madvise-32
> +msm_shrink at copy-mmap-oom-8
> +msm_shrink at copy-mmap-oom-32
> +msm_shrink at copy-mmap-dmabuf-sanitycheck-8
> +msm_shrink at copy-mmap-dmabuf-sanitycheck-32
> +msm_shrink at copy-mmap-dmabuf-8
> +msm_shrink at copy-mmap-dmabuf-32
> +msm_shrink at copy-mmap-dmabuf-madvise-8
> +msm_shrink at copy-mmap-dmabuf-madvise-32
> +msm_shrink at copy-mmap-dmabuf-oom-8
> +msm_shrink at copy-mmap-dmabuf-oom-32
> +msm_mapping at ring
> +msm_mapping at sqefw
> +msm_mapping at shadow
> +msm_submitoverhead at submitbench-10-bos
> +msm_submitoverhead at submitbench-10-bos-no-implicit-sync
> +msm_submitoverhead at submitbench-100-bos
> +msm_submitoverhead at submitbench-100-bos-no-implicit-sync
> +msm_submitoverhead at submitbench-250-bos
> +msm_submitoverhead at submitbench-250-bos-no-implicit-sync
> +msm_submitoverhead at submitbench-500-bos
> +msm_submitoverhead at submitbench-500-bos-no-implicit-sync
> +msm_submitoverhead at submitbench-1000-bos
> +msm_submitoverhead at submitbench-1000-bos-no-implicit-sync
> +msm_recovery at hangcheck
> +msm_recovery at gpu-fault
> +msm_recovery at gpu-fault-parallel
> +msm_recovery at iova-fault
> +msm_submit at empty-submit
> +msm_submit at invalid-queue-submit
> +msm_submit at invalid-flags-submit
> +msm_submit at invalid-in-fence-submit
> +msm_submit at invalid-duplicate-bo-submit
> +msm_submit at invalid-cmd-idx-submit
> +msm_submit at invalid-cmd-type-submit
> +msm_submit at valid-submit


More information about the dri-devel mailing list