From: vitaly prosyak <vprosyak@amd.com>
To: "Jesse.zhang@amd.com" <jesse.zhang@amd.com>,
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>
Subject: Re: [PATCH i-g-t 4/4] tests/amd_dispatch: add the filter for amd dispatch
Date: Sun, 10 Nov 2024 19:44:17 -0500 [thread overview]
Message-ID: <f20a778e-74fc-41c1-a699-60eb5bb00765@amd.com> (raw)
In-Reply-To: <20241107020510.350132-4-jesse.zhang@amd.com>
these 4 patches looks good to me.
Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
On 2024-11-06 21:05, Jesse.zhang@amd.com wrote:
> From: "Jesse.zhang@amd.com" <Jesse.zhang@amd.com>
>
> Check sysfs reset mask before enabling certain subtests.
>
> Signed-off-by: Jesse Zhang <Jesse.Zhang@amd.com>
> ---
> tests/amdgpu/amd_dispatch.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/tests/amdgpu/amd_dispatch.c b/tests/amdgpu/amd_dispatch.c
> index 76b62128d..23d07561c 100644
> --- a/tests/amdgpu/amd_dispatch.c
> +++ b/tests/amdgpu/amd_dispatch.c
> @@ -116,7 +116,8 @@ igt_main
>
> igt_describe("Test GPU reset using a binary shader to hang the job on gfx ring");
> igt_subtest_with_dynamic("amdgpu-dispatch-hang-test-gfx-with-IP-GFX") {
> - if (arr_cap[AMD_IP_GFX]) {
> + if (arr_cap[AMD_IP_GFX] &&
> + is_reset_enable(AMD_IP_COMPUTE, AMDGPU_RESET_TYPE_PER_QUEUE)) {
> igt_dynamic_f("amdgpu-dispatch-hang-test-gfx")
> amdgpu_dispatch_hang_gfx(device, BACKEND_SE_GC_SHADER_INVALID_SHADER);
> }
> @@ -124,7 +125,8 @@ igt_main
>
> igt_describe("Test GPU reset using a binary shader to hang the job on compute ring");
> igt_subtest_with_dynamic("amdgpu-dispatch-hang-test-compute-with-IP-COMPUTE") {
> - if (arr_cap[AMD_IP_COMPUTE]) {
> + if (arr_cap[AMD_IP_COMPUTE] &&
> + is_reset_enable(AMD_IP_COMPUTE, AMDGPU_RESET_TYPE_PER_QUEUE)) {
> igt_dynamic_f("amdgpu-dispatch-hang-test-compute")
> amdgpu_dispatch_hang_compute(device, BACKEND_SE_GC_SHADER_INVALID_SHADER);
> }
> @@ -132,7 +134,8 @@ igt_main
>
> igt_describe("Test GPU reset using a invalid shader program address to hang the job on compute ring");
> igt_subtest_with_dynamic("amdgpu-dispatch-invalid-program-addr-test-compute-with-IP-COMPUTE") {
> - if (arr_cap[AMD_IP_COMPUTE]) {
> + if (arr_cap[AMD_IP_COMPUTE] &&
> + is_reset_enable(AMD_IP_COMPUTE, AMDGPU_RESET_TYPE_PER_QUEUE)) {
> igt_dynamic_f("amdgpu-dispatch-invalid-program-addr-test-compute")
> amdgpu_dispatch_hang_compute(device, BACKEND_SE_GC_SHADER_INVALID_PROGRAM_ADDR);
> }
> @@ -140,7 +143,8 @@ igt_main
>
> igt_describe("Test GPU reset using a invalid shader program setting to hang the job on compute ring");
> igt_subtest_with_dynamic("amdgpu-dispatch-invalid-setting-test-compute-with-IP-COMPUTE") {
> - if (arr_cap[AMD_IP_COMPUTE]) {
> + if (arr_cap[AMD_IP_COMPUTE] &&
> + is_reset_enable(AMD_IP_COMPUTE, AMDGPU_RESET_TYPE_PER_QUEUE)) {
> igt_dynamic_f("amdgpu-dispatch-invalid-setting-test-compute")
> amdgpu_dispatch_hang_compute(device, BACKEND_SE_GC_SHADER_INVALID_PROGRAM_SETTING);
> }
> @@ -148,7 +152,8 @@ igt_main
>
> igt_describe("Test GPU reset using a invalid shader user data to hang the job on compute ring");
> igt_subtest_with_dynamic("amdgpu-dispatch-invalid-user-data-test-compute-with-IP-COMPUTE") {
> - if (arr_cap[AMD_IP_COMPUTE]) {
> + if (arr_cap[AMD_IP_COMPUTE] &&
> + is_reset_enable(AMD_IP_COMPUTE, AMDGPU_RESET_TYPE_PER_QUEUE)) {
> igt_dynamic_f("amdgpu-dispatch-invalid-user-data-test-compute")
> amdgpu_dispatch_hang_compute(device, BACKEND_SE_GC_SHADER_INVALID_USER_DATA);
> }
next prev parent reply other threads:[~2024-11-11 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 2:05 [PATCH i-g-t 1/4] lib/amdgpu: add gpu reset check Jesse.zhang@amd.com
2024-11-07 2:05 ` [PATCH i-g-t 2/4] tests/amd_queue_reset: modify the asic filter Jesse.zhang@amd.com
2024-11-07 2:05 ` [PATCH i-g-t 3/4] tests/amd_deadlock: add the filter for amd deadlock Jesse.zhang@amd.com
2024-11-07 2:05 ` [PATCH i-g-t 4/4] tests/amd_dispatch: add the filter for amd dispatch Jesse.zhang@amd.com
2024-11-11 0:44 ` vitaly prosyak [this message]
2024-11-07 2:54 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/4] lib/amdgpu: add gpu reset check Patchwork
2024-11-07 3:02 ` ✓ CI.xeBAT: " Patchwork
2024-11-07 3:56 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-11-08 9:08 ` ✗ CI.xeFULL: " Patchwork
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=f20a778e-74fc-41c1-a699-60eb5bb00765@amd.com \
--to=vprosyak@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jesse.zhang@amd.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=vitaly.prosyak@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