From: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [RFC i-g-t] Extract autotuned dummy load into lib
Date: Wed, 12 Oct 2016 14:59:51 +0300 [thread overview]
Message-ID: <20161012115954.16803-1-abdiel.janulgue@linux.intel.com> (raw)
A lot of igt testcases need some dummy load to make sure a race
window is big enough. Unfortunately having a fixed amount of
workload leads to spurious test failures or overtly long runtimes
on some fast/slow platforms. This library contains functionality
to submit GPU workloads that is dynamically tuned to consume a
specific amount of time.
This functionality is generalized to lib from existing features in
gem_wait and kms_flip. In the future, we could update test cases
that could benefit from auto-tuned dummy workloads to use this
new api.
Abdiel Janulgue (3):
lib: add igt_dummyload
igt/gem_wait: Use new igt_dummyload api
igt/kms_flip: Use new igt_dummyload api
lib/Makefile.sources | 2 +
lib/igt.h | 1 +
lib/igt_dummyload.c | 419 +++++++++++++++++++++++++++++++++++++++
lib/igt_dummyload.h | 63 ++++++
tests/gem_wait.c | 77 ++-----
tests/kms_flip.c | 191 +-----------------
6 files changed, 507 insertions(+), 246 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-10-12 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 11:59 Abdiel Janulgue [this message]
2016-10-12 11:59 ` [RFC i-g-t PATCH 1/3] lib: add igt_dummyload Abdiel Janulgue
2016-10-12 11:59 ` [RFC i-g-t PATCH 2/3] igt/gem_wait: Use new igt_dummyload api Abdiel Janulgue
2016-10-12 12:07 ` Chris Wilson
2016-10-13 9:31 ` Abdiel Janulgue
2016-10-13 9:49 ` Chris Wilson
2016-10-13 15:17 ` Daniel Vetter
2016-10-14 10:17 ` Abdiel Janulgue
2016-10-12 11:59 ` [RFC i-g-t PATCH 3/3] igt/kms_flip: " Abdiel Janulgue
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=20161012115954.16803-1-abdiel.janulgue@linux.intel.com \
--to=abdiel.janulgue@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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