From: Matthew Auld <matthew.auld@intel.com>
To: "Bernatowicz, Marcin" <marcin.bernatowicz@linux.intel.com>,
Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
igt-dev@lists.freedesktop.org
Cc: Stuart Summers <stuart.summers@intel.com>,
Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_exec_reset: Skip syncobj_wait during the gt_reset
Date: Fri, 27 Sep 2024 11:22:23 +0100 [thread overview]
Message-ID: <53783573-6681-49ec-b400-cb85dfedcf8f@intel.com> (raw)
In-Reply-To: <05ef47a7-663a-4fc4-a069-0c3f3f4c385b@linux.intel.com>
On 27/09/2024 11:05, Bernatowicz, Marcin wrote:
>
>
> On 9/25/2024 12:31 PM, Bommu Krishnaiah wrote:
>> From: "Bommu Krishnaiah" <krishnaiah.bommu@intel.com>
>>
>> Skipping the syncobj_wait for the workloads which is submitted
>> before gt reset, since After gt reset There is no expectation
>> from the hardware/GuC/KMD that the workload will then
>> re-execute and complete.
>>
>> Signed-off-by: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
>> Cc: Stuart Summers <stuart.summers@intel.com>
>> ---
>> tests/intel/xe_exec_reset.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/tests/intel/xe_exec_reset.c b/tests/intel/xe_exec_reset.c
>> index b5d5f43ea..b1a7548c6 100644
>> --- a/tests/intel/xe_exec_reset.c
>> +++ b/tests/intel/xe_exec_reset.c
>> @@ -263,8 +263,9 @@ test_balancer(int fd, int gt, int class, int
>> n_exec_queues, int n_execs,
>> }
>> for (i = 0; i < n_exec_queues && n_execs; i++)
>> - igt_assert(syncobj_wait(fd, &syncobjs[i], 1, INT64_MAX, 0,
>> - NULL));
>> + if (!(flags & GT_RESET))
>> + igt_assert(syncobj_wait(fd, &syncobjs[i], 1, INT64_MAX,
>
> What happens when the user waits on syncobj in case of GT reset ?
> Maybe there is no expectation that there will be re-execute, but
> shouldn't the syncobj be notified or a timeout hit ?
Yeah, this sounds like KMD bug. Expectation is that dma fences should
eventually signal no matter what, and in a reasonable amount of time.
Possibly relevant fix (very recently merged):
https://patchwork.freedesktop.org/patch/605681/?series=136463&rev=1
>
>> + 0, NULL));
>> igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0,
>> NULL));
>> sync[0].flags |= DRM_XE_SYNC_FLAG_SIGNAL;
>> @@ -410,7 +411,8 @@ test_legacy_mode(int fd, struct
>> drm_xe_engine_class_instance *eci,
>> }
>> for (i = 0; i < n_exec_queues && n_execs; i++)
>> - igt_assert(syncobj_wait(fd, &syncobjs[i], 1, INT64_MAX, 0,
>> + if (!(flags & GT_RESET))
>> + igt_assert(syncobj_wait(fd, &syncobjs[i], 1, INT64_MAX, 0,
>> NULL));
>> igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0,
>> NULL));
>
next prev parent reply other threads:[~2024-09-27 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 10:31 [PATCH i-g-t] tests/intel/xe_exec_reset: Skip syncobj_wait during the gt_reset Bommu Krishnaiah
2024-09-26 5:18 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-09-26 5:24 ` ✓ CI.xeBAT: success " Patchwork
2024-09-26 17:03 ` ✗ CI.xeFULL: failure " Patchwork
2024-09-27 10:05 ` [PATCH i-g-t] " Bernatowicz, Marcin
2024-09-27 10:22 ` Matthew Auld [this message]
2024-09-30 10:18 ` Bommu, Krishnaiah
2024-10-03 16:08 ` Matthew Brost
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=53783573-6681-49ec-b400-cb85dfedcf8f@intel.com \
--to=matthew.auld@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=krishnaiah.bommu@intel.com \
--cc=marcin.bernatowicz@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=stuart.summers@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