All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: <vitaly.prosyak@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Christian Koenig <christian.koenig@amd.com>,
	Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	Jesse Zhang <Jesse.Zhang@amd.com>
Subject: [PATCH] tests/amdgpu: improve fuzzing test
Date: Sat, 27 Apr 2024 00:09:46 -0400	[thread overview]
Message-ID: <20240427040946.539853-1-vitaly.prosyak@amd.com> (raw)

From: Vitaly Prosyak <vitaly.prosyak@amd.com>

Improve cs wait for fuzzing test by using all possible IP blocks.
Due to some IP blocks being different for different ASICs's the
return code for ioctl  DRM_IOCTL_AMDGPU_WAIT_CS is ignored.

Cc: Alex Deucher <alexander.deucher@amd.com>
Cc: Christian Koenig <christian.koenig@amd.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: Jesse Zhang <Jesse.Zhang@amd.com>
Signed-off-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
---
 tests/amdgpu/amd_fuzzing.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/tests/amdgpu/amd_fuzzing.c b/tests/amdgpu/amd_fuzzing.c
index b47b26cf0..b2bba83fa 100644
--- a/tests/amdgpu/amd_fuzzing.c
+++ b/tests/amdgpu/amd_fuzzing.c
@@ -91,7 +91,6 @@ void amd_cs_wait_fuzzing(int fd, const enum amd_ip_block_type types[], int size)
 		r = igt_ioctl(fd, DRM_IOCTL_AMDGPU_WAIT_CS, &cs_wait);
 		igt_info("%s AMDGPU_WAIT_CS %s r %d\n", __func__,
 				amd_ip_type_arr[types[i]].name, r);
-		igt_assert_eq(r, 0);
 	}
 }
 
@@ -160,7 +159,10 @@ igt_main
 {
 	int fd = -1;
 	const enum amd_ip_block_type arr_types[] = {
-			AMD_IP_VCE, AMD_IP_VCN_ENC, AMD_IP_VCN_JPEG, AMD_IP_VPE };
+			AMD_IP_GFX, AMD_IP_COMPUTE, AMD_IP_DMA, AMD_IP_UVD,
+			AMD_IP_VCE, AMD_IP_UVD_ENC, AMD_IP_VCN_DEC, AMD_IP_VCN_ENC,
+			AMD_IP_VCN_JPEG, AMD_IP_VPE
+	};
 
 	igt_fixture {
 		fd = drm_open_driver(DRIVER_AMDGPU);
-- 
2.25.1


             reply	other threads:[~2024-04-27  4:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27  4:09 vitaly.prosyak [this message]
2024-04-27  4:44 ` ✓ CI.xeBAT: success for tests/amdgpu: improve fuzzing test Patchwork
2024-04-27  4:53 ` ✓ Fi.CI.BAT: " Patchwork
2024-04-27  5:42 ` ✗ CI.xeFULL: failure " Patchwork
2024-04-27  5:59 ` ✗ Fi.CI.IGT: " Patchwork
2024-04-28  1:37 ` [PATCH] " Zhang, Jesse(Jie)

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=20240427040946.539853-1-vitaly.prosyak@amd.com \
    --to=vitaly.prosyak@amd.com \
    --cc=Jesse.Zhang@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.