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] tests/amdgpu: add timeout for queue reset
Date: Thu, 15 Aug 2024 20:57:21 -0400 [thread overview]
Message-ID: <9b4a3d64-61c4-4e92-95db-1261d31f2a22@amd.com> (raw)
In-Reply-To: <20240814101140.3165345-1-jesse.zhang@amd.com>
[-- Attachment #1: Type: text/plain, Size: 4028 bytes --]
The change looks good to me.
Please do some tiny modifications below.
It is related to explicitly having a code block for timeout avoid checking:
if (sh_mem->reset_flags == 0)
This prevents a potential race condition between processes.
Since a timeout implies that we do not need to check the flags, this check can be safely omitted.
Reviewed-by: Vitaly Prosyak vitaly.prosyak@amd.com
On 2024-08-14 06:11, Jesse.zhang@amd.com wrote:
> 1.If the test case cannot trigger any reset on some ASIC,
> It should be considered a failure.
>
> 2. Fix code style
>
> Signed-off-by: Jesse Zhang <jesse.zhang@amd.com>
> ---
> tests/amdgpu/amd_queue_reset.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/tests/amdgpu/amd_queue_reset.c b/tests/amdgpu/amd_queue_reset.c
> index 6819892e0..249676407 100644
> --- a/tests/amdgpu/amd_queue_reset.c
> +++ b/tests/amdgpu/amd_queue_reset.c
> @@ -30,6 +30,7 @@
> #define SHARED_CHILD_DESCRIPTOR 3
>
> #define SHARED_MEM_NAME "/queue_reset_shm"
> +#define TEST_TIMEOUT 100 //100 seconds
>
> enum process_type {
> PROCESS_UNKNOWN,
> @@ -49,6 +50,7 @@ enum error_code_bits {
> };
>
> enum reset_code_bits {
> + NO_RESET_SET_BIT,
> QUEUE_RESET_SET_BIT,
> GPU_RESET_BEGIN_SET_BIT,
> GPU_RESET_END_SUCCESS_SET_BIT,
Change to
ALL_RESET_BITS = 0x1f,
Since we have now 5 states after you added NO_RESET_SET_BIT
> @@ -307,6 +309,7 @@ static void set_next_test_to_run(struct shmbuf *sh_mem, unsigned int error,
> sync_point_enter(sh_mem);
> wait_for_complete_iteration(sh_mem);
> sync_point_exit(sh_mem);
> + igt_assert_neq(sh_mem->reset_flags, 1U << NO_RESET_SET_BIT);
> }
>
> static int
> @@ -473,6 +476,9 @@ run_monitor_child(amdgpu_device_handle device, amdgpu_context_handle *arr_contex
> int state_machine = 0;
> int error_code;
> unsigned int flags;
> + int64_t cnt = 0;
> + time_t start, end;
> + double elapsed = 0;
>
> after_reset_state = after_reset_hangs = 0;
> init_flags = in_process_flags = 0;
> @@ -487,7 +493,8 @@ run_monitor_child(amdgpu_device_handle device, amdgpu_context_handle *arr_contex
> error_code = 0;
> flags = 0;
> set_reset_state(sh_mem, false, ALL_RESET_BITS);
> - while (1) {
Please, keep while(1)
> + time(&start);
> + while (elapsed < TEST_TIMEOUT) {
> if (state_machine == 0) {
> amdgpu_cs_query_reset_state2(arr_context[test_counter], &init_flags);
>
> @@ -533,7 +540,15 @@ run_monitor_child(amdgpu_device_handle device, amdgpu_context_handle *arr_contex
> break;
> }
> }
> + cnt++;
> + if (cnt % 1000000 == 0) {
> + time(&end);
> + elapsed = difftime(end, start);
if ( elapsed >= TEST_TIMEOUT) {
set_reset_state(sh_mem, true, NO_RESET_SET_BIT);
break;
}
> + }
> }
> + elapsed = 0;
remove 2 lines below:
> + if (sh_mem->reset_flags == 0) //remove this
> + set_reset_state(sh_mem, true, NO_RESET_SET_BIT);
> sync_point_exit(sh_mem);
> num_of_tests--;
> test_counter++;
> @@ -1000,7 +1015,7 @@ igt_main
> igt_describe("Stressful-and-multiple-cs-of-bad and good length-operations-using-multiple-processes");
> igt_subtest_with_dynamic_f("amdgpu-%s-%s", ip_tests[i] == AMD_IP_COMPUTE ? "COMPUTE":"GRAFIX", it->name) {
> if (arr_cap[ip_tests[i]] && get_next_rings(ring_id_good, info, &ring_id_good, &ring_id_bad, i)) {
> - igt_dynamic_f("amdgpu-%s-ring-good-%d-bad-%d-%s", it->name,ring_id_good, ring_id_bad, ip_tests[i] == AMD_IP_COMPUTE ? "COMPUTE":"GRAFIX")
> + igt_dynamic_f("amdgpu-%s-ring-good-%d-bad-%d-%s", it->name, ring_id_good, ring_id_bad, ip_tests[i] == AMD_IP_COMPUTE ? "COMPUTE":"GRAFIX")
> set_next_test_to_run(sh_mem, it->test, ip_background, ip_tests[i], ring_id_good, ring_id_bad);
> }
> }
[-- Attachment #2: Type: text/html, Size: 6168 bytes --]
prev parent reply other threads:[~2024-08-16 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 10:11 [PATCH i-g-t] tests/amdgpu: add timeout for queue reset Jesse.zhang@amd.com
2024-08-14 15:09 ` ✓ CI.xeBAT: success for " Patchwork
2024-08-14 15:22 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-14 19:31 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-14 20:23 ` ✗ CI.xeFULL: " Patchwork
2024-08-16 0:57 ` vitaly prosyak [this message]
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=9b4a3d64-61c4-4e92-95db-1261d31f2a22@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