Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@intel.com>
To: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "kamil.konieczny@linux.intel.com"
	<kamil.konieczny@linux.intel.com>,
	"Hajda, Andrzej" <andrzej.hajda@intel.com>,
	"Brost, Matthew" <matthew.brost@intel.com>
Subject: Re: [PATCH i-g-t v4] tests/intel/xe_exec_fault_mode: Don't return early
Date: Wed, 4 Sep 2024 12:41:43 +0200	[thread overview]
Message-ID: <f72f69a4-705c-46c4-94c4-043f62bd77ef@intel.com> (raw)
In-Reply-To: <SJ1PR11MB62047B49AD25D72861197DFC819C2@SJ1PR11MB6204.namprd11.prod.outlook.com>


On 9/4/2024 6:49 AM, Upadhyay, Tejas wrote:
>
>> -----Original Message-----
>> From: Das, Nirmoy <nirmoy.das@intel.com>
>> Sent: Thursday, August 29, 2024 11:31 PM
>> To: igt-dev@lists.freedesktop.org
>> Cc: kamil.konieczny@linux.intel.com; Das, Nirmoy <nirmoy.das@intel.com>;
>> Hajda, Andrzej <andrzej.hajda@intel.com>; Brost, Matthew
>> <matthew.brost@intel.com>; Upadhyay, Tejas <tejas.upadhyay@intel.com>
>> Subject: [PATCH i-g-t v4] tests/intel/xe_exec_fault_mode: Don't return early
>>
>> 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)) {
> Nit: double bracket (( not needed I think

Fixed it in the v5


Thanks

Nirmoy

>
> Tejas
>> +		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);
>> +		}
>> +	}
>> +
>>   	for (i = 0; i < n_exec_queues; i++) {
>>   		xe_exec_queue_destroy(fd, exec_queues[i]);
>>   		if (bind_exec_queues[i])
>> --
>> 2.42.0

      reply	other threads:[~2024-09-04 10:41 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 ` [PATCH i-g-t v4] tests/intel/xe_exec_fault_mode: Don't return early Andrzej Hajda
2024-09-03 20:44   ` Nirmoy Das
2024-09-04  4:49 ` Upadhyay, Tejas
2024-09-04 10:41   ` Nirmoy Das [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=f72f69a4-705c-46c4-94c4-043f62bd77ef@intel.com \
    --to=nirmoy.das@intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=matthew.brost@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