From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
Chris Wilson <chris.p.wilson@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] tests/i915/perf: Add stress / race exercises
Date: Tue, 31 Jan 2023 10:36:50 -0800 [thread overview]
Message-ID: <877cx2v9dp.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <1949047.usQuhbGJ8B@jkrzyszt-mobl1.ger.corp.intel.com>
On Tue, 31 Jan 2023 09:36:30 -0800, Janusz Krzysztofik wrote:
>
> Since Chris' subtest didn't help in triggering the list corruption, I've
> developed a new subtest that can do it. Since it is almost identical to the
> one Chris added, I decided to reuse his code, then add my new subtest to perf
> as well. But maybe you are right that my subtest better fits to another test.
> not perf. I'll think this over.
>
> I hope this clarifies things for you.
Thanks Janusz. Of course the test is valid but because it is not triggering
bugs in perf perhaps it is better added to a different IGT file. Maybe
gem_ctx_persistence? Maybe perf is also ok. Anyway something to think
about.
Thanks.
--
Ashutosh
WARNING: multiple messages have this Message-ID (diff)
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org, Arkadiusz Hiler <arek@hiler.eu>,
intel-gfx@lists.freedesktop.org,
Petri Latvala <adrinael@adrinael.net>,
Chris Wilson <chris.p.wilson@linux.intel.com>
Subject: Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 0/2] tests/i915/perf: Add stress / race exercises
Date: Tue, 31 Jan 2023 10:36:50 -0800 [thread overview]
Message-ID: <877cx2v9dp.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <1949047.usQuhbGJ8B@jkrzyszt-mobl1.ger.corp.intel.com>
On Tue, 31 Jan 2023 09:36:30 -0800, Janusz Krzysztofik wrote:
>
> Since Chris' subtest didn't help in triggering the list corruption, I've
> developed a new subtest that can do it. Since it is almost identical to the
> one Chris added, I decided to reuse his code, then add my new subtest to perf
> as well. But maybe you are right that my subtest better fits to another test.
> not perf. I'll think this over.
>
> I hope this clarifies things for you.
Thanks Janusz. Of course the test is valid but because it is not triggering
bugs in perf perhaps it is better added to a different IGT file. Maybe
gem_ctx_persistence? Maybe perf is also ok. Anyway something to think
about.
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2023-01-31 18:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 9:17 [igt-dev] [PATCH i-g-t 0/2] tests/i915/perf: Add stress / race exercises Janusz Krzysztofik
2023-01-31 9:17 ` [Intel-gfx] " Janusz Krzysztofik
2023-01-31 9:17 ` [igt-dev] [PATCH i-g-t 1/2] i915/perf: Stress opening of new perf streams against existing contexts Janusz Krzysztofik
2023-01-31 9:17 ` [Intel-gfx] " Janusz Krzysztofik
2023-01-31 11:59 ` [igt-dev] " Kamil Konieczny
2023-01-31 11:59 ` [Intel-gfx] " Kamil Konieczny
2023-01-31 14:14 ` [igt-dev] " Janusz Krzysztofik
2023-01-31 14:14 ` [Intel-gfx] " Janusz Krzysztofik
2023-01-31 9:17 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/perf: Exercise barrier race Janusz Krzysztofik
2023-01-31 9:17 ` [Intel-gfx] " Janusz Krzysztofik
2023-02-01 18:21 ` [igt-dev] " Kamil Konieczny
2023-02-01 18:21 ` [Intel-gfx] " Kamil Konieczny
2023-02-01 19:16 ` [igt-dev] " Janusz Krzysztofik
2023-02-01 19:16 ` [Intel-gfx] " Janusz Krzysztofik
2023-02-02 10:19 ` [igt-dev] " Kamil Konieczny
2023-02-02 10:19 ` [Intel-gfx] " Kamil Konieczny
2023-01-31 11:16 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/perf: Add stress / race exercises Patchwork
2023-01-31 15:08 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-01-31 16:19 ` [igt-dev] [PATCH i-g-t 0/2] " Dixit, Ashutosh
2023-01-31 16:19 ` [Intel-gfx] " Dixit, Ashutosh
2023-01-31 16:55 ` Dixit, Ashutosh
2023-01-31 16:55 ` [Intel-gfx] " Dixit, Ashutosh
2023-01-31 17:56 ` Janusz Krzysztofik
2023-01-31 17:56 ` [Intel-gfx] " Janusz Krzysztofik
2023-01-31 17:36 ` Janusz Krzysztofik
2023-01-31 17:36 ` [Intel-gfx] " Janusz Krzysztofik
2023-01-31 18:36 ` Dixit, Ashutosh [this message]
2023-01-31 18:36 ` Dixit, Ashutosh
2023-02-01 15:51 ` Janusz Krzysztofik
2023-02-01 15:51 ` [Intel-gfx] " Janusz Krzysztofik
2023-02-03 19:21 ` Umesh Nerlige Ramappa
2023-02-03 19:21 ` [Intel-gfx] " Umesh Nerlige Ramappa
2023-02-03 20:59 ` Janusz Krzysztofik
2023-02-03 20:59 ` [Intel-gfx] " Janusz Krzysztofik
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=877cx2v9dp.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.