Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Welty, Brian" <brian.welty@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
	<igt-dev@lists.freedesktop.org>
Cc: saurabhg.gupta@intel.com
Subject: Re: [PATCH i-g-t] tests/intel/xe_exec_reset: Do not validate data on GT reset
Date: Fri, 12 Jan 2024 11:27:50 -0800	[thread overview]
Message-ID: <35878e85-b17b-41bf-b9e7-047841a0504b@intel.com> (raw)
In-Reply-To: <20240112154611.1395699-1-jonathan.cavitt@intel.com>



On 1/12/2024 7:46 AM, Jonathan Cavitt wrote:
> In the cm-gt-reset test, data validation is blocked because a GT reset
> means that we cannot verify the completion of the exec operations.
> Extend this logic to all other tests that perform GT resets in
> xe_exec_reset.
> 
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>

Thanks for extending the fix to the other subtests.

Reviewed-by: Brian Welty <brian.welty@intel.com>



> ---
>   tests/intel/xe_exec_reset.c | 12 ++++++++----
>   1 file changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/intel/xe_exec_reset.c b/tests/intel/xe_exec_reset.c
> index 0cd5b10517..168523c64c 100644
> --- a/tests/intel/xe_exec_reset.c
> +++ b/tests/intel/xe_exec_reset.c
> @@ -294,8 +294,10 @@ test_balancer(int fd, int gt, int class, int n_exec_queues, int n_execs,
>   	xe_vm_unbind_async(fd, vm, 0, 0, addr, bo_size, sync, 1);
>   	igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0, NULL));
>   
> -	for (i = bad_batches; i < n_execs; i++)
> -		igt_assert_eq(data[i].data, 0xc0ffee);
> +	if (!(flags & GT_RESET)) {
> +		for (i = bad_batches; i < n_execs; i++)
> +			igt_assert_eq(data[i].data, 0xc0ffee);
> +	}
>   
>   	syncobj_destroy(fd, sync[0].handle);
>   	for (i = 0; i < n_exec_queues; i++) {
> @@ -462,8 +464,10 @@ test_legacy_mode(int fd, struct drm_xe_engine_class_instance *eci,
>   	xe_vm_unbind_async(fd, vm, 0, 0, addr, bo_size, sync, 1);
>   	igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0, NULL));
>   
> -	for (i = 1; i < n_execs; i++)
> -		igt_assert_eq(data[i].data, 0xc0ffee);
> +	if (!(flags & GT_RESET)) {
> +		for (i = 1; i < n_execs; i++)
> +			igt_assert_eq(data[i].data, 0xc0ffee);
> +	}
>   
>   	syncobj_destroy(fd, sync[0].handle);
>   	for (i = 0; i < n_exec_queues; i++) {

WARNING: multiple messages have this Message-ID (diff)
From: "Welty, Brian" <brian.welty@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: saurabhg.gupta@intel.com
Subject: Re: [PATCH i-g-t] tests/intel/xe_exec_reset: Do not validate data on GT reset
Date: Fri, 12 Jan 2024 11:27:50 -0800	[thread overview]
Message-ID: <35878e85-b17b-41bf-b9e7-047841a0504b@intel.com> (raw)
Message-ID: <20240112192750.02ogLvREH1AubVGsaXD0ow_XSgrTha5egP-v_Ah75p0@z> (raw)
In-Reply-To: <20240112154611.1395699-1-jonathan.cavitt@intel.com>



On 1/12/2024 7:46 AM, Jonathan Cavitt wrote:
> In the cm-gt-reset test, data validation is blocked because a GT reset
> means that we cannot verify the completion of the exec operations.
> Extend this logic to all other tests that perform GT resets in
> xe_exec_reset.
> 
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>

Thanks for extending the fix to the other subtests.

Reviewed-by: Brian Welty <brian.welty@intel.com>



> ---
>   tests/intel/xe_exec_reset.c | 12 ++++++++----
>   1 file changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/intel/xe_exec_reset.c b/tests/intel/xe_exec_reset.c
> index 0cd5b10517..168523c64c 100644
> --- a/tests/intel/xe_exec_reset.c
> +++ b/tests/intel/xe_exec_reset.c
> @@ -294,8 +294,10 @@ test_balancer(int fd, int gt, int class, int n_exec_queues, int n_execs,
>   	xe_vm_unbind_async(fd, vm, 0, 0, addr, bo_size, sync, 1);
>   	igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0, NULL));
>   
> -	for (i = bad_batches; i < n_execs; i++)
> -		igt_assert_eq(data[i].data, 0xc0ffee);
> +	if (!(flags & GT_RESET)) {
> +		for (i = bad_batches; i < n_execs; i++)
> +			igt_assert_eq(data[i].data, 0xc0ffee);
> +	}
>   
>   	syncobj_destroy(fd, sync[0].handle);
>   	for (i = 0; i < n_exec_queues; i++) {
> @@ -462,8 +464,10 @@ test_legacy_mode(int fd, struct drm_xe_engine_class_instance *eci,
>   	xe_vm_unbind_async(fd, vm, 0, 0, addr, bo_size, sync, 1);
>   	igt_assert(syncobj_wait(fd, &sync[0].handle, 1, INT64_MAX, 0, NULL));
>   
> -	for (i = 1; i < n_execs; i++)
> -		igt_assert_eq(data[i].data, 0xc0ffee);
> +	if (!(flags & GT_RESET)) {
> +		for (i = 1; i < n_execs; i++)
> +			igt_assert_eq(data[i].data, 0xc0ffee);
> +	}
>   
>   	syncobj_destroy(fd, sync[0].handle);
>   	for (i = 0; i < n_exec_queues; i++) {

  parent reply	other threads:[~2024-01-12 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:46 [PATCH i-g-t] tests/intel/xe_exec_reset: Do not validate data on GT reset Jonathan Cavitt
2024-01-12 17:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-01-12 17:10 ` ✓ CI.xeBAT: " Patchwork
2024-01-12 19:27 ` Welty, Brian [this message]
2024-01-12 19:27   ` [PATCH i-g-t] " Welty, Brian
2024-01-12 21:00 ` ✗ Fi.CI.IGT: failure for " Patchwork
2024-01-15 13:48   ` Kamil Konieczny

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=35878e85-b17b-41bf-b9e7-047841a0504b@intel.com \
    --to=brian.welty@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=saurabhg.gupta@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