From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: martin.peres@intel.com, juha-pekka.heikkila@intel.com
Subject: [igt-dev] [PATCH i-g-t v15 0/1] Introduce i915 pipe stress test
Date: Thu, 12 Dec 2019 16:24:14 +0200 [thread overview]
Message-ID: <20191212142415.26517-1-stanislav.lisovskiy@intel.com> (raw)
This test case will challenge hardware, by using as maximum
display buffer/memory bandwidth as possible. To achieve that
it runs some workload on each CPU core, also it runs some GPU
load simultaneously, also uses kms to add as much planes as
possible using highest possible mode.
Stanislav Lisovskiy (1):
igt/tests: kms_plane_stress: Add plane stress test
tests/Makefile.sources | 3 +
tests/i915/i915_pipe_stress.c | 888 ++++++++++++++++++++++++++++++++++
tests/meson.build | 1 +
3 files changed, 892 insertions(+)
create mode 100644 tests/i915/i915_pipe_stress.c
--
2.17.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-12-12 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 14:24 Stanislav Lisovskiy [this message]
2019-12-12 14:24 ` [igt-dev] [PATCH i-g-t v15 1/1] igt/tests: kms_plane_stress: Add plane stress test Stanislav Lisovskiy
2019-12-12 15:40 ` [igt-dev] ✗ GitLab.Pipeline: warning for Introduce i915 pipe stress test (rev2) Patchwork
2019-12-12 16:16 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-12-13 8:35 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-12-12 18:15 [igt-dev] [PATCH i-g-t v15 0/1] Introduce i915 pipe stress test Stanislav Lisovskiy
2020-01-03 9:48 Stanislav Lisovskiy
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=20191212142415.26517-1-stanislav.lisovskiy@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=martin.peres@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