From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, igt-dev@lists.freedesktop.org
Cc: kamil.konieczny@linux.intel.com,
Matthew Brost <matthew.brost@intel.com>,
Tejas Upadhyay <tejas.upadhyay@intel.com>
Subject: Re: [PATCH i-g-t v4] tests/intel/xe_exec_fault_mode: Don't return early
Date: Tue, 3 Sep 2024 16:48:00 +0200 [thread overview]
Message-ID: <fdf77e79-3ab4-4209-93d0-d084f31cc27e@intel.com> (raw)
In-Reply-To: <20240829180051.3286-1-nirmoy.das@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2074 bytes --]
On 29.08.2024 20:00, Nirmoy Das wrote:
> Tests that are causing pagefaults should wait for exec to queue
> ban/finish otherwise pending engine resets because of on-going
> pagefaults would cause failure in subsequent tests to fail.
>
> Not all execs will generate page faults and in such case reading ban
> property is not enough but the signal should either -EIO or 0.
> so read that instead.
>
> v2: specify timeout reason and iterate over exec_queues(Andrzej)
> v3: increase timeout
> v4: check for signal status to be -EIO/0.
>
> Cc: Andrzej Hajda<andrzej.hajda@intel.com>
> Cc: Kamil Konieczny<kamil.konieczny@linux.intel.com>
> Cc: Matthew Brost<matthew.brost@intel.com>
> Cc: Tejas Upadhyay<tejas.upadhyay@intel.com>
> Link:https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1630
> Signed-off-by: Nirmoy Das<nirmoy.das@intel.com>
> ---
> tests/intel/xe_exec_fault_mode.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/tests/intel/xe_exec_fault_mode.c b/tests/intel/xe_exec_fault_mode.c
> index 1f1f1e50b..fa050d0dc 100644
> --- a/tests/intel/xe_exec_fault_mode.c
> +++ b/tests/intel/xe_exec_fault_mode.c
> @@ -329,6 +329,17 @@ test_exec(int fd, struct drm_xe_engine_class_instance *eci,
> igt_assert_eq(data[i].data, 0xc0ffee);
> }
>
> + if ((flags & INVALID_FAULT)) {
> + for (i = 0; i < n_execs; i++) {
> + int ret;
> + int64_t timeout = NSEC_PER_SEC;
> +
> + ret = __xe_wait_ufence(fd, &data[i].exec_sync, USER_FENCE_VALUE,
> + exec_queues[i % n_exec_queues], &timeout);
> + igt_assert(ret == -EIO || ret ==0);
"ret ==0" - missing space.
Btw in theory we have n_execs * 1second (128sec???) total wait time.
> + }
> + }
> +
If I placed change correctly in the code it could be replaced by chain:
if ((flags & INVALID_FAULT)) {
// your change
} else if !(flags & INVALID_VA) { ... } Up to you. Reviewed-by: Andrzej
Hajda <andrzej.hajda@intel.com> Regards Andrzej
> for (i = 0; i < n_exec_queues; i++) {
> xe_exec_queue_destroy(fd, exec_queues[i]);
> if (bind_exec_queues[i])
[-- Attachment #2: Type: text/html, Size: 3701 bytes --]
next prev parent reply other threads:[~2024-09-03 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 18:00 [PATCH i-g-t v4] tests/intel/xe_exec_fault_mode: Don't return early Nirmoy Das
2024-08-29 19:47 ` ✓ CI.xeBAT: success for tests/intel/xe_exec_fault_mode: Don't return early (rev5) Patchwork
2024-08-29 20:05 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-08-30 9:50 ` ✗ CI.xeFULL: " Patchwork
2024-08-30 13:16 ` ✓ Fi.CI.BAT: success for tests/intel/xe_exec_fault_mode: Don't return early (rev6) Patchwork
2024-08-30 13:17 ` ✓ CI.xeBAT: " Patchwork
2024-08-30 23:22 ` ✗ CI.xeFULL: failure " Patchwork
2024-09-01 2:18 ` ✓ Fi.CI.IGT: success " Patchwork
2024-09-03 14:48 ` Andrzej Hajda [this message]
2024-09-03 20:44 ` [PATCH i-g-t v4] tests/intel/xe_exec_fault_mode: Don't return early Nirmoy Das
2024-09-04 4:49 ` Upadhyay, Tejas
2024-09-04 10:41 ` Nirmoy Das
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=fdf77e79-3ab4-4209-93d0-d084f31cc27e@intel.com \
--to=andrzej.hajda@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=nirmoy.das@intel.com \
--cc=tejas.upadhyay@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