From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@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: Fri, 03 Feb 2023 21:59:05 +0100 [thread overview]
Message-ID: <1780744.TLkxdtWsSY@jkrzyszt-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <Y91ews5O6nHf+2EX@orsosgc001.jf.intel.com>
Hi Umesh,
Thanks for taking a look.
On Friday, 3 February 2023 20:21:38 CET Umesh Nerlige Ramappa wrote:
> On Tue, Jan 31, 2023 at 10:17:29AM +0100, Janusz Krzysztofik wrote:
> >Users reported oopses on list corruptions when using i915 perf with a
> >number of concurrently running graphics applications. That indicates we
> >are currently missing some important tests for such scenarios. Cover
> >that gap.
>
> Any bug ids that were filed for the issue?
Yes, https://gitlab.freedesktop.org/drm/intel/issues/6333.
> Also what were the parameters
> passed to perf OA when the issues were reported? This could help
> actually root cause the issue and have a test closer to the actual use
> case.
Root cause has been already identified, and it lays not in perf, only in
barriers handling code, see https://patchwork.freedesktop.org/series/113636/
(submitted to trybot so far, soon to the public list).
Thanks,
Janusz
>
> Regards,
> Umesh
> >
> >Chris Wilson (1):
> > i915/perf: Stress opening of new perf streams against existing
> > contexts
> >
> >Janusz Krzysztofik (1):
> > tests/i915/perf: Exercise barrier race
> >
> > tests/i915/perf.c | 111 ++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 111 insertions(+)
> >
>
prev parent reply other threads:[~2023-02-03 20:59 UTC|newest]
Thread overview: 18+ 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 ` [igt-dev] [PATCH i-g-t 1/2] i915/perf: Stress opening of new perf streams against existing contexts Janusz Krzysztofik
2023-01-31 11:59 ` Kamil Konieczny
2023-01-31 14:14 ` Janusz Krzysztofik
2023-01-31 9:17 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/perf: Exercise barrier race Janusz Krzysztofik
2023-02-01 18:21 ` Kamil Konieczny
2023-02-01 19:16 ` Janusz Krzysztofik
2023-02-02 10:19 ` 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:55 ` Dixit, Ashutosh
2023-01-31 17:56 ` Janusz Krzysztofik
2023-01-31 17:36 ` Janusz Krzysztofik
2023-01-31 18:36 ` Dixit, Ashutosh
2023-02-01 15:51 ` Janusz Krzysztofik
2023-02-03 19:21 ` Umesh Nerlige Ramappa
2023-02-03 20:59 ` Janusz Krzysztofik [this message]
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=1780744.TLkxdtWsSY@jkrzyszt-mobl1.ger.corp.intel.com \
--to=janusz.krzysztofik@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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