Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: vitaly prosyak <vprosyak@amd.com>
To: "Zhang, Jesse(Jie)" <Jesse.Zhang@amd.com>,
	"Prosyak, Vitaly" <Vitaly.Prosyak@amd.com>,
	Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Koenig, Christian" <Christian.Koenig@amd.com>
Subject: Re: [PATCH i-g-t] test/amdgpu: fix unknow test issue for amdgpu queue test
Date: Tue, 27 Aug 2024 22:05:53 -0400	[thread overview]
Message-ID: <d2ff19f7-cc37-416e-b789-f7c1e2903d13@amd.com> (raw)
In-Reply-To: <DM4PR12MB5152F4675A22C9079370877AE3952@DM4PR12MB5152.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 6687 bytes --]

Thanks for catching this! You're correct; I've reverted my request to remove |sh_mem != NULL| since the |igt_fixture| isn't executed when the |--list-subtests| parameter is passed. I'll merge the changes tomorrow. Thanks again!


Vitaly

On 2024-08-27 22:00, Zhang, Jesse(Jie) wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Vitaly,
>
> -----Original Message-----
> From: Prosyak, Vitaly <Vitaly.Prosyak@amd.com>
> Sent: Wednesday, August 28, 2024 9:51 AM
> To: Zhang, Jesse(Jie) <Jesse.Zhang@amd.com>; Kamil Konieczny <kamil.konieczny@linux.intel.com>; igt-dev@lists.freedesktop.org
> Cc: Prosyak, Vitaly <Vitaly.Prosyak@amd.com>; Deucher, Alexander <Alexander.Deucher@amd.com>; Koenig, Christian <Christian.Koenig@amd.com>
> Subject: Re: [PATCH i-g-t] test/amdgpu: fix unknow test issue for amdgpu queue test
>
> Hi Jesse,
>
> The changes look good.
>
> Could you please remove the condition check for sh_mem? This check is redundant because we already have igt_require(sh_mem != NULL); in the igt_fixture.
>
>
> when we run sudo ./tests/amdgpu/amd_queue_reset --list-subtests, the sh_mem is NULL, and it should not call set_next_test_to_skip.
>
> if remove the check for sh_mem, it will have segmentation fault, like this:
>
> jenkins@image-update:~/workspace/tools/igt-gpu-tools/6code/igt-gpu-tools/build$ sudo ./tests/amdgpu/amd_queue_reset --list-subtests
> amdgpu-COMPUTE-CMD_STREAM_EXEC_INVALID_PACKET_LENGTH
> amdgpu-COMPUTE-CMD_STREAM_EXEC_INVALID_OPCODE
> amdgpu-COMPUTE-BACKEND_SE_GC_SHADER_INVALID_PROGRAM_ADDR
> amdgpu-COMPUTE-BACKEND_SE_GC_SHADER_INVALID_USER_DATA
> amdgpu-COMPUTE-BACKEND_SE_GC_SHADER_INVALID_SHADER
> amdgpu-GFX-CMD_STREAM_EXEC_INVALID_PACKET_LENGTH
> amdgpu-GFX-CMD_STREAM_EXEC_INVALID_OPCODE
> amdgpu-GFX-BACKEND_SE_GC_SHADER_INVALID_PROGRAM_ADDR
> amdgpu-GFX-BACKEND_SE_GC_SHADER_INVALID_USER_DATA
> amdgpu-GFX-BACKEND_SE_GC_SHADER_INVALID_SHADER
> Received signal SIGSEGV.
> Stack trace:
>  #0 [fatal_sig_handler+0x17b]
>  #1 [__sigaction+0x50]
>  #2 [__igt_unique____real_main1025+0x27e]
>  #3 [main+0x2d]
>  #4 [__libc_init_first+0x90]
>  #5 [__libc_start_main+0x80]
>  #6 [_start+0x25]
> Segmentation fault
>
> Thanks
> Jesse
>
> With that adjustment, the patch is:
>
> Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
>
> Thanks
>
>
> Vitaly
>
>
>
>
> On 2024-08-27 03:54, Zhang, Jesse(Jie) wrote:
>> [AMD Official Use Only - AMD Internal Distribution Only]
>>
>> Hi Kamil
>>
>> -----Original Message-----
>> From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>> Sent: Tuesday, August 27, 2024 3:24 PM
>> To: igt-dev@lists.freedesktop.org
>> Cc: Zhang, Jesse(Jie) <Jesse.Zhang@amd.com>; Prosyak, Vitaly
>> <Vitaly.Prosyak@amd.com>; Deucher, Alexander
>> <Alexander.Deucher@amd.com>; Koenig, Christian
>> <Christian.Koenig@amd.com>
>> Subject: Re: [PATCH i-g-t] test/amdgpu: fix unknow test issue for
>> amdgpu queue test
>>
>> Hi Jesse.zhang,
>> On 2024-08-27 at 13:19:32 +0800, Jesse.zhang@amd.com wrote:
>>> Queue reset does not exit properly when executing unknown subtests.
>>> Because other processes are still functioning.
>>>
>>> It should exit the other three processes (test, background, and
>>> monitor) for this case.
>>>
>>> Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>
>>> Cc: Alex Deucher <alexander.deucher@amd.com>
>>> Cc: Christian Koenig <christian.koenig@amd.com>
>>>
>>> Signed-off-by: Jesse Zhang <jesse.zhang@amd.com>
>>> ---
>>>  tests/amdgpu/amd_queue_reset.c | 10 ++++++++--
>>>  1 file changed, 8 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tests/amdgpu/amd_queue_reset.c
>>> b/tests/amdgpu/amd_queue_reset.c index 60208e085..85408e3ff 100644
>>> --- a/tests/amdgpu/amd_queue_reset.c
>>> +++ b/tests/amdgpu/amd_queue_reset.c
>>> @@ -70,6 +70,7 @@ struct shmbuf {
>>>       int count;
>>>       bool sub_test_completed;
>>>       bool sub_test_is_skipped;
>>> +     bool sub_test_is_existed;
>>>       unsigned int test_flags;
>>>       int test_error_code;
>>>       bool reset_completed;
>>> @@ -148,6 +149,7 @@ skip_sub_test(struct shmbuf *sh_mem)  {
>>>       sem_wait(&sh_mem->sem_state_mutex);
>>>       sh_mem->sub_test_is_skipped = true;
>>> +     sh_mem->sub_test_is_existed = true;
>>>       sem_post(&sh_mem->sem_state_mutex);
>>>  }
>> Do you re-implement igt infra?
>>
>> Hi Kamil
>>
>> No, in the queue reset test, we start three processes (test process,
>> background process, and monitoring process) when running any test (including unknown tests, such as such as:  sudo amd_queue_reset --run-subtest amdgpu_testxxx).
>>
>> The known process can exit with the other three processes.
>>
>> The unknown process can exit, but the other processes will not exit.
>>
>> This patch fixes the issue of other processes exiting in the unknown case.
>>
>> Regards
>> Jesse
>>
>> Regards,
>> Kamil
>>
>>> @@ -327,6 +329,7 @@ static void set_next_test_to_run(struct shmbuf *sh_mem, unsigned int error,
>>>       sh_mem->good_job.ip = ip_good;
>>>       sh_mem->good_job.ring_id = ring_id_good;
>>>       sh_mem->sub_test_is_skipped = false;
>>> +     sh_mem->sub_test_is_existed = true;
>>>       sem_post(&sh_mem->sem_state_mutex);
>>>
>>>       //sync and wait for complete
>>> @@ -405,6 +408,7 @@ shared_mem_create(struct shmbuf **ppbuf)
>>>       shmp->sub_test_completed = false;
>>>       shmp->reset_completed = false;
>>>       shmp->sub_test_is_skipped = false;
>>> +     shmp->sub_test_is_existed = false;
>>>
>>>       *ppbuf = shmp;
>>>       return shm_fd;
>>> @@ -1128,7 +1132,6 @@ igt_main
>>>                       create_contexts(device, &arr_context_handle, const_num_of_tests);
>>>               else if (process == PROCESS_BACKGROUND)
>>>                       fd_shm = shared_mem_open(&sh_mem);
>>> -
>>>               igt_require(fd_shm != -1);
>>>               igt_require(sh_mem != NULL);
>>>
>>> @@ -1136,7 +1139,6 @@ igt_main
>>>                       process, sh_mem, const_num_of_tests, info[0].hw_ip_version_major,
>>>                       &monitor_child, &test_child);
>>>       }
>>> -
>>>       for (int i = 0; i < ARRAY_SIZE(ip_tests); i++) {
>>>               reset_rings_numbers(&ring_id_good, &ring_id_bad, &ring_id_job_good, &ring_id_job_bad);
>>>               for (struct dynamic_test *it = &arr_err[0]; it->name;
>>> it++) { @@
>>> -1154,6 +1156,10 @@ igt_main
>>>                       }
>>>               }
>>>       }
>>> +
> Please, remove
>
> sh_mem
>
>>> +     if (sh_mem &&( !sh_mem->sub_test_is_existed))
>>> +             set_next_test_to_skip(sh_mem);
>>> +
>>>       igt_fixture {
>>>               if (process == PROCESS_TEST) {
>>>                       waitpid(monitor_child, &monitorExitMethod, 0);
>>> --
>>> 2.25.1
>>>

[-- Attachment #2: Type: text/html, Size: 8869 bytes --]

  reply	other threads:[~2024-08-28  2:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  5:19 [PATCH i-g-t] test/amdgpu: fix unknow test issue for amdgpu queue test Jesse.zhang@amd.com
2024-08-27  5:56 ` ✓ CI.xeBAT: success for " Patchwork
2024-08-27  6:04 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-27  7:24 ` [PATCH i-g-t] " Kamil Konieczny
2024-08-27  7:54   ` Zhang, Jesse(Jie)
2024-08-28  1:50     ` vitaly prosyak
2024-08-28  2:00       ` Zhang, Jesse(Jie)
2024-08-28  2:05         ` vitaly prosyak [this message]
2024-08-27 12:17 ` ✗ CI.xeFULL: failure for " Patchwork
2024-08-28  5:33 ` ✗ Fi.CI.IGT: " 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=d2ff19f7-cc37-416e-b789-f7c1e2903d13@amd.com \
    --to=vprosyak@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Jesse.Zhang@amd.com \
    --cc=Vitaly.Prosyak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox