From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>
Cc: "Syrjala, Ville" <ville.syrjala@intel.com>,
"Peres, Martin" <martin.peres@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] igt/tests: kms_plane_stress: Add plane stress test
Date: Thu, 21 Mar 2019 13:44:25 +0000 [thread overview]
Message-ID: <f374340da75adb970edd5effc1a25c4a9d724f51.camel@intel.com> (raw)
In-Reply-To: <7b14f00c-f21c-e76f-36e7-93f1e9276392@linux.intel.com>
On Thu, 2019-03-21 at 14:06 +0100, Maarten Lankhorst wrote:
> Op 21-03-2019 om 13:59 schreef Lisovskiy, Stanislav:
> > On Thu, 2019-03-21 at 13:41 +0100, Maarten Lankhorst wrote:
> > > Op 21-03-2019 om 13:34 schreef Stanislav Lisovskiy:
> > > > This test attempts to utilize all connected
> > > > outputs at the same time, using maximum possible
> > > > resolution and amount of planes, to check whether
> > > > we are hiting any kind of bandwidth, watermark or
> > > > other limitations.
> > > >
> > > > Signed-off-by: Stanislav Lisovskiy <
> > > > stanislav.lisovskiy@intel.com>
> > > > ---
> > > > lib/igt_kms.h | 7 ++
> > > > tests/Makefile.sources | 1 +
> > > > tests/kms_plane_stress.c | 247
> > > > +++++++++++++++++++++++++++++++++++++++
> > > > tests/meson.build | 1 +
> > > > tests/test.png | Bin 0 -> 1068158 bytes
> > >
> > > Remove the test png? You can use cairo calls to draw something,
> > > or
> > > igt_create_pattern_fb to get a default pattern.
> >
> > Yes, can remove it. Just wanted some nice image here, however
> > probably
> > yeah will leave it for local testing.
> >
> > > How is this different from kms_atomic_transition btw? It tries
> > > the
> > > same at least.
> >
> > Well, I guess kms_atomic_transition doesn't utilize all pipe at the
> > same time, it goes just one by one. Here it tries to use all pipes
> > at the same time.
> >
>
> But it does have tests for all modes, see run_modeset_transition.
> Only thing missing is
>
> that we don't enable all planes yet. But this should be easy to add
> with try commit.
In fact the idea behind this as we discussed with Martin, was to add
additional stressing factors here, like generating some heavy memory
usage at the same time + gpu load in order to see how system behaves in
this case.
The goal here is to detect all kinds of bandwidth issues, similar to
ones, which we had recently. That is why I had to put this to a
separate test case.
>
> ~Maarten
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-21 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 12:34 [igt-dev] [PATCH i-g-t] igt/tests: kms_plane_stress: Add plane stress test Stanislav Lisovskiy
2019-03-21 12:41 ` Maarten Lankhorst
2019-03-21 12:59 ` Lisovskiy, Stanislav
2019-03-21 13:06 ` Maarten Lankhorst
2019-03-21 13:44 ` Lisovskiy, Stanislav [this message]
2019-03-21 13:59 ` Peres, Martin
2019-03-21 14:06 ` Maarten Lankhorst
2019-03-25 11:10 ` [igt-dev] ✗ Fi.CI.BAT: failure for igt/tests: kms_plane_stress: Add plane stress test (rev2) 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=f374340da75adb970edd5effc1a25c4a9d724f51.camel@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=martin.peres@intel.com \
--cc=ville.syrjala@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