From: Matthew Brost <matthew.brost@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tests/xe_exec_threads: Fill in GT field for second balancer thread
Date: Thu, 21 Mar 2024 01:04:37 +0000 [thread overview]
Message-ID: <ZfuHpR6TCEnzLw8X@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <7vgrnkw4ndo5ydxybh3qoqriovorgyvrrsatt4tgifis7xo3ju@3g7qmeluwrps>
On Wed, Mar 20, 2024 at 03:47:57PM -0500, Lucas De Marchi wrote:
> On Wed, Mar 20, 2024 at 12:23:56PM -0700, Matt Roper wrote:
> > The balancer subtests spawn two pthreads per engine class if there are
> > multiple instances of the class. The GT field of the data structure is
> > filled in properly for the first thread, but not for the second,
> > effectively leaving it set to "0."
> >
> > For platforms with standalone media, this will result in failures when
> > the thread tries to find the instances of a media class on GT0 and trips
> > the "igt_assert(num_placements > 1)" assertion in test_balancer().
> >
> > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
>
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> do you know why we unrolled a loop in there and did a wrong copy and
I think the for_gt loop was added after the original version of this.
Likely an ommision when that was added.
> paste? That together with vertical spacing on flow control seems to be a
> good source of bugs. Good find.
>
> The only difference between the first and second thread data I'm seeing
> is flags VIRTUAL vs PARALLEL. Matt Brost, is this test from you? Could
Yes, I wrote this one. Not my finest work in terms of copy / pasting,
indeed the only difference should be VIRTUAL vs. PARALLEL. I think this
should be consolidated into a loop.
> you add an overview to its documentation? The boilerplate doc added
> there after the fact looks less than helpful.
>
What kinda of documentation were you thinking of? Most all the IGTs are
light on doc but updating the doc for ones I wrote is on my todo list...
Matt
> Lucas De Marchi
>
> > ---
> > tests/intel/xe_exec_threads.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tests/intel/xe_exec_threads.c b/tests/intel/xe_exec_threads.c
> > index 55907e2b3..977e8c600 100644
> > --- a/tests/intel/xe_exec_threads.c
> > +++ b/tests/intel/xe_exec_threads.c
> > @@ -1081,6 +1081,7 @@ static void threads(int fd, int flags)
> > threads_data[i].fd = 0;
> > else
> > threads_data[i].fd = fd;
> > + threads_data[i].gt = gt;
> > threads_data[i].vm_legacy_mode =
> > vm_legacy_mode;
> > threads_data[i].class = class;
> > --
> > 2.43.0
> >
next prev parent reply other threads:[~2024-03-21 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 19:23 [PATCH i-g-t] tests/xe_exec_threads: Fill in GT field for second balancer thread Matt Roper
2024-03-20 20:47 ` Lucas De Marchi
2024-03-21 1:04 ` Matthew Brost [this message]
2024-03-21 6:01 ` Lucas De Marchi
2024-03-21 18:43 ` Matthew Brost
2024-03-20 21:02 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-03-20 21:11 ` ✓ CI.xeBAT: " Patchwork
2024-03-20 21:35 ` Matt Roper
2024-03-21 9:14 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-21 13:23 ` Kamil Konieczny
2024-03-25 8:54 ` ✓ Fi.CI.IGT: success " 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=ZfuHpR6TCEnzLw8X@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@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