From: Jesse Zhang <jesse.zhang@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: Tim Huang <tim.huang@amd.com>,
Luben Tuikov <luben.tuikov@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: [igt-dev] [PATCH] tests/amd_dispatch: add dispatch test for gfx and compute
Date: Wed, 25 Oct 2023 17:24:32 +0800 [thread overview]
Message-ID: <20231025092432.726460-1-jesse.zhang@amd.com> (raw)
Add dispatch test on gfx and compute ring.
Through memset shader and memcpy shader,
and validate the result.
Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>
Cc: Luben Tuikov <luben.tuikov@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>
Cc: Christian Koenig <christian.koenig@amd.com>
Cc: Tim Huang <tim.huang@amd.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
Signed-off-by: Jesse Zhang <Jesse.Zhang@amd.com>
---
tests/amdgpu/amd_dispatch.c | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/tests/amdgpu/amd_dispatch.c b/tests/amdgpu/amd_dispatch.c
index 323284306..d62dc7a3d 100644
--- a/tests/amdgpu/amd_dispatch.c
+++ b/tests/amdgpu/amd_dispatch.c
@@ -36,6 +36,16 @@ amdgpu_dispatch_hang_compute(amdgpu_device_handle device_handle)
amdgpu_gfx_dispatch_test(device_handle, AMDGPU_HW_IP_COMPUTE, 1);
}
+static void
+amdgpu_gfx_dispatch_test_gfx(amdgpu_device_handle device_handle) {
+ amdgpu_gfx_dispatch_test(device_handle, AMDGPU_HW_IP_GFX, 0);
+}
+
+static void
+amdgpu_gfx_dispatch_test_compute(amdgpu_device_handle device_handle) {
+ amdgpu_gfx_dispatch_test(device_handle, AMDGPU_HW_IP_COMPUTE, 0);
+}
+
static void
amdgpu_gpu_reset_test(amdgpu_device_handle device_handle, int drm_amdgpu)
{
@@ -97,6 +107,23 @@ igt_main
asic_rings_readness(device, 1, arr_cap);
}
+
+ igt_describe("Check-dispatch-test-gfx-for-each-ring-using-memset-memcpy-shaders-and-validate-after");
+ igt_subtest_with_dynamic("amdgpu-dispatch-test-gfx-with-IP-GFX") {
+ if (arr_cap[AMD_IP_GFX]) {
+ igt_dynamic_f("amdgpu-dispatch-test-gfx")
+ amdgpu_gfx_dispatch_test_gfx(device);
+ }
+ }
+
+ igt_describe("Check-dispatch-test-compute-for-each-ring-using-memset-memcpy-shaders-and-validate-after");
+ igt_subtest_with_dynamic("amdgpu-dispatch-test-compute-with-IP-COMPUTE") {
+ if (arr_cap[AMD_IP_COMPUTE]) {
+ igt_dynamic_f("amdgpu-dispatch-test-compute")
+ amdgpu_gfx_dispatch_test_compute(device);
+ }
+ }
+
igt_describe("Test GPU reset using a binary shader to slow hang the job on compute ring");
igt_subtest_with_dynamic("amdgpu-dispatch-test-compute-with-IP-COMPUTE") {
if (arr_cap[AMD_IP_COMPUTE]) {
--
2.25.1
next reply other threads:[~2023-10-25 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 9:24 Jesse Zhang [this message]
2023-10-25 10:15 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/amd_dispatch: add dispatch test for gfx and compute Patchwork
2023-10-25 10:44 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-10-25 12:13 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-10-25 16:56 ` [igt-dev] [PATCH] " Kamil Konieczny
2023-10-26 13:29 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-10-26 5:56 [igt-dev] [PATCH] " Jesse Zhang
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=20231025092432.726460-1-jesse.zhang@amd.com \
--to=jesse.zhang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=luben.tuikov@amd.com \
--cc=tim.huang@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox