From: Adam Miszczak <adam.miszczak@linux.intel.com>
To: nakshtra.goyal@intel.com, igt-dev@lists.freedesktop.org
Cc: adam.miszczak@intel.com, matthew.brost@intel.com
Subject: Re: [PATCH i-g-t] tests/intel/xe_exec_threads: Initializing exec_threads array
Date: Wed, 4 Mar 2026 07:13:59 +0100 [thread overview]
Message-ID: <f0488559-9333-42f2-8b17-98f208994e77@linux.intel.com> (raw)
In-Reply-To: <20260303063154.489637-1-nakshtra.goyal@intel.com>
On 3/3/2026 7:31 AM, nakshtra.goyal@intel.com wrote:
> From: Nakshtra Goyal <nakshtra.goyal@intel.com>
>
> Initialising exec_threads array to zero as threads-many-queues test
> fails on initial check to non_zero condition , it takes garbage
> value(non-zero) on first iteration , which call synobj_wait on a
> synobj that was never signalled.
>
> Signed-off-by: Nakshtra Goyal <nakshtra.goyal@intel.com>
> ---
> tests/intel/xe_exec_threads.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/intel/xe_exec_threads.c b/tests/intel/xe_exec_threads.c
> index 27d5a8928..f082a0eda 100644
> --- a/tests/intel/xe_exec_threads.c
> +++ b/tests/intel/xe_exec_threads.c
> @@ -502,7 +502,7 @@ test_legacy_mode(int fd, uint32_t vm, uint64_t addr, uint64_t userptr,
> .num_syncs = 2,
> .syncs = to_user_pointer(sync),
> };
> - uint32_t exec_queues[MAX_N_EXEC_QUEUES];
> + uint32_t exec_queues[MAX_N_EXEC_QUEUES] = {};
> uint32_t bind_exec_queues[MAX_N_EXEC_QUEUES];
> uint32_t syncobjs[MAX_N_EXEC_QUEUES];
> size_t bo_size;
Acked-by: Adam Miszczak <adam.miszczak@linux.intel.com>
next prev parent reply other threads:[~2026-03-04 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 6:31 [PATCH i-g-t] tests/intel/xe_exec_threads: Initializing exec_threads array nakshtra.goyal
2026-03-03 8:38 ` Dandamudi, Priyanka
2026-03-05 4:53 ` Dandamudi, Priyanka
2026-03-03 23:58 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-03-04 0:13 ` ✓ i915.CI.BAT: " Patchwork
2026-03-04 6:13 ` Adam Miszczak [this message]
2026-03-04 16:28 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-04 20:41 ` ✗ i915.CI.Full: " Patchwork
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=f0488559-9333-42f2-8b17-98f208994e77@linux.intel.com \
--to=adam.miszczak@linux.intel.com \
--cc=adam.miszczak@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=nakshtra.goyal@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