[PATCH i-g-t] tests/intel/xe_exec_compute_mode: Print engine name on error

[Cavitt, Jonathan]

-----Original Message-----
From: igt-dev <igt-dev-bounces at lists.freedesktop.org> On Behalf Of Nirmoy Das
Sent: Monday, October 7, 2024 5:32 AM
To: igt-dev at lists.freedesktop.org
Cc: Das, Nirmoy <nirmoy.das at intel.com>; Kamil Konieczny <kamil.konieczny at linux.intel.com>
Subject: [PATCH i-g-t] tests/intel/xe_exec_compute_mode: Print engine name on error
> 
> Print engine name on error for debugging.
> 
> Cc: Kamil Konieczny <kamil.konieczny at linux.intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das at intel.com>

LGTM.  All tests that run using test_exec are run through xe_for_each_engine,
and no other tests in xe_exec_compute_mode do so, so this is comprehensive.

Reviewed-by: Jonathan Cavitt <jonathan.cavitt at intel.com>
-Jonathan Cavitt

> ---
>  tests/intel/xe_exec_compute_mode.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tests/intel/xe_exec_compute_mode.c b/tests/intel/xe_exec_compute_mode.c
> index 7d434f798..82e607848 100644
> --- a/tests/intel/xe_exec_compute_mode.c
> +++ b/tests/intel/xe_exec_compute_mode.c
> @@ -122,6 +122,7 @@ test_exec(int fd, struct drm_xe_engine_class_instance *eci,
>  	int64_t fence_timeout;
>  	void *dummy;
>  
> +	igt_debug("%s running on: %s\n", __func__, xe_engine_class_string(eci->engine_class));
>  	igt_assert_lte(n_exec_queues, MAX_N_EXECQUEUES);
>  
>  	vm = xe_vm_create(fd, DRM_XE_VM_CREATE_FLAG_LR_MODE, 0);
> -- 
> 2.46.0
> 
>