From: Derek Morton <derek.j.morton@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.com
Subject: [PATCH i-g-t v3 0/6] Scheduler tests
Date: Thu, 10 Mar 2016 11:03:28 +0000 [thread overview]
Message-ID: <1457607814-18751-1-git-send-email-derek.j.morton@intel.com> (raw)
This patch set adds scheduler tests.
Patch 1 Makes gem_has_ring() non static as the test will need to call it
Patch 2 adds library code used by the tests. There are other tests under
development which are planned to reuse some of these libraries.
Patch 3 adds some basic tests, read dependency tests and write dependency tests.
Patch 4 Is the patch previously submitted by John Harrison to update
gem_ctx_param_basic with ioctls to set context priorities. It is included as
part of this patch set as Patch 6 & 7 are dependant on it.
Patch 5 adds subtests to check sheduler behaviour for batch buffers submitted at
differing priorities.
Patch 6 adds subtests to check priority bumping behaviour.
v2: Updates for comments from Daniele Ceraolo Spurio and Daniel Vetter
Added tests requested by Joonas Lahtinen
v3: Removed the patch to update gem_has_ring() and updated the test to
use BSD if there is 1 ring and BSD1 / BSD2 if there are two.
Derek Morton (5):
ioctl_wrappers: make gem_has_ring non static
lib/intel_batchbuffer: Add functions to be used in the scheduler test
tests/gem_scheduler: Add gem_scheduler test
tests/gem_scheduler: Add subtests to test batch priority behaviour
gem_scheduler: Added subtests to test priority bumping
John Harrison (1):
igt/gem_ctx_param_basic: Updated to support scheduler priority
interface
lib/intel_batchbuffer.c | 384 ++++++++++++++++++++++++++-
lib/intel_batchbuffer.h | 14 +
lib/ioctl_wrappers.c | 2 +-
lib/ioctl_wrappers.h | 2 +
tests/Makefile.sources | 1 +
tests/gem_ctx_param_basic.c | 34 ++-
tests/gem_scheduler.c | 630 ++++++++++++++++++++++++++++++++++++++++++++
7 files changed, 1060 insertions(+), 7 deletions(-)
create mode 100644 tests/gem_scheduler.c
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-03-10 11:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 11:03 Derek Morton [this message]
2016-03-10 11:03 ` [PATCH i-g-t v3 1/6] ioctl_wrappers: make gem_has_ring non static Derek Morton
2016-03-14 12:29 ` Daniele Ceraolo Spurio
2016-03-29 13:08 ` Morton, Derek J
2016-03-10 11:03 ` [PATCH i-g-t v3 2/6] lib/intel_batchbuffer: Add functions to be used in the scheduler test Derek Morton
2016-03-14 12:16 ` Daniele Ceraolo Spurio
2016-03-29 15:04 ` Morton, Derek J
2016-03-10 11:03 ` [PATCH i-g-t v3 3/6] tests/gem_scheduler: Add gem_scheduler test Derek Morton
2016-03-17 8:49 ` Daniele Ceraolo Spurio
2016-03-17 10:33 ` Daniele Ceraolo Spurio
2016-03-10 11:03 ` [PATCH i-g-t v3 4/6] igt/gem_ctx_param_basic: Updated to support scheduler priority interface Derek Morton
2016-03-10 11:03 ` [PATCH i-g-t v3 5/6] tests/gem_scheduler: Add subtests to test batch priority behaviour Derek Morton
2016-03-17 8:58 ` Daniele Ceraolo Spurio
2016-03-30 8:19 ` Morton, Derek J
2016-03-10 11:03 ` [PATCH i-g-t v3 6/6] gem_scheduler: Added subtests to test priority bumping Derek Morton
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=1457607814-18751-1-git-send-email-derek.j.morton@intel.com \
--to=derek.j.morton@intel.com \
--cc=daniel.vetter@ffwll.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