From: "Emilio López" <emilio.lopez@collabora.co.uk>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: devel@driverdev.osuosl.org,
"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>,
"Riley Andrews" <riandrews@android.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"John Harrison" <John.C.Harrison@Intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Greg Hackmann" <ghackmann@google.com>,
"Rob Clark" <robdclark@gmail.com>,
linux-kselftest@vger.kernel.org,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Daniel Stone" <daniels@collabora.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Emilio López" <emilio.lopez@collabora.co.uk>
Subject: [RFC PATCH v1 0/9] Tests for sync infrastructure
Date: Wed, 9 Mar 2016 12:28:53 -0300 [thread overview]
Message-ID: <1457537342-678-1-git-send-email-emilio.lopez@collabora.co.uk> (raw)
Hello everyone,
This is a series of tests to exercise the sync kernel infrastructure. It is
meant to be a test suite for the work Gustavo has been doing to destage it,
see [0] for his latest series to date.
These tests were originally part of a battery of tests shipping with
Android's libsync that were rewritten to use the new userspace interfaces.
As usual, all comments are welcome.
Cheers!
Emilio
[0] https://lists.freedesktop.org/archives/dri-devel/2016-March/102204.html
Emilio López (9):
selftest: sync: basic tests for sw_sync framework
selftest: sync: fence tests for sw_sync framework
selftest: sync: merge tests for sw_sync framework
selftest: sync: wait tests for sw_sync framework
selftest: sync: destruction tests for sw_sync framework
selftest: sync: stress test for parallelism
selftest: sync: stress consumer/producer test
selftest: sync: stress test for merges
selftest: sync: disable tests that rely on not yet defined behaviour
tools/testing/selftests/Makefile | 1 +
tools/testing/selftests/sync/.gitignore | 1 +
tools/testing/selftests/sync/Makefile | 28 +++
tools/testing/selftests/sync/sw_sync.h | 46 +++++
tools/testing/selftests/sync/sync.c | 203 +++++++++++++++++++++
tools/testing/selftests/sync/sync.h | 119 ++++++++++++
tools/testing/selftests/sync/sync_alloc.c | 74 ++++++++
tools/testing/selftests/sync/sync_destroyed.c | 90 +++++++++
tools/testing/selftests/sync/sync_fence.c | 134 ++++++++++++++
tools/testing/selftests/sync/sync_merge.c | 60 ++++++
.../testing/selftests/sync/sync_stress_consumer.c | 185 +++++++++++++++++++
tools/testing/selftests/sync/sync_stress_merge.c | 115 ++++++++++++
.../selftests/sync/sync_stress_parallelism.c | 111 +++++++++++
tools/testing/selftests/sync/sync_test.c | 87 +++++++++
tools/testing/selftests/sync/sync_wait.c | 95 ++++++++++
tools/testing/selftests/sync/synctest.h | 69 +++++++
16 files changed, 1418 insertions(+)
create mode 100644 tools/testing/selftests/sync/.gitignore
create mode 100644 tools/testing/selftests/sync/Makefile
create mode 100644 tools/testing/selftests/sync/sw_sync.h
create mode 100644 tools/testing/selftests/sync/sync.c
create mode 100644 tools/testing/selftests/sync/sync.h
create mode 100644 tools/testing/selftests/sync/sync_alloc.c
create mode 100644 tools/testing/selftests/sync/sync_destroyed.c
create mode 100644 tools/testing/selftests/sync/sync_fence.c
create mode 100644 tools/testing/selftests/sync/sync_merge.c
create mode 100644 tools/testing/selftests/sync/sync_stress_consumer.c
create mode 100644 tools/testing/selftests/sync/sync_stress_merge.c
create mode 100644 tools/testing/selftests/sync/sync_stress_parallelism.c
create mode 100644 tools/testing/selftests/sync/sync_test.c
create mode 100644 tools/testing/selftests/sync/sync_wait.c
create mode 100644 tools/testing/selftests/sync/synctest.h
--
2.5.0
next reply other threads:[~2016-03-09 15:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 15:28 Emilio López [this message]
2016-03-09 15:28 ` [RFC PATCH v1 1/9] selftest: sync: basic tests for sw_sync framework Emilio López
2016-03-28 11:56 ` Emil Velikov
2016-03-28 12:20 ` Emilio López
2016-03-28 13:48 ` Emil Velikov
2016-04-04 4:12 ` Emilio López
2016-04-07 14:47 ` Emil Velikov
2016-03-09 15:28 ` [RFC PATCH v1 2/9] selftest: sync: fence " Emilio López
2016-03-09 15:28 ` [RFC PATCH v1 3/9] selftest: sync: merge " Emilio López
2016-03-09 15:28 ` [RFC PATCH v1 4/9] selftest: sync: wait " Emilio López
2016-03-09 15:28 ` [RFC PATCH v1 5/9] selftest: sync: destruction " Emilio López
2016-03-09 15:28 ` [RFC PATCH v1 6/9] selftest: sync: stress test for parallelism Emilio López
2016-03-09 15:29 ` [RFC PATCH v1 7/9] selftest: sync: stress consumer/producer test Emilio López
2016-03-09 15:29 ` [RFC PATCH v1 8/9] selftest: sync: stress test for merges Emilio López
2016-03-09 15:29 ` [RFC PATCH v1 9/9] selftest: sync: disable tests that rely on not yet defined behaviour Emilio López
2016-03-09 16:14 ` Shuah Khan
2016-03-28 12:33 ` Emilio López
2016-03-09 16:13 ` [RFC PATCH v1 0/9] Tests for sync infrastructure Shuah Khan
2016-03-28 12:32 ` Emilio López
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=1457537342-678-1-git-send-email-emilio.lopez@collabora.co.uk \
--to=emilio.lopez@collabora.co.uk \
--cc=John.C.Harrison@Intel.com \
--cc=arve@android.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ghackmann@google.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=riandrews@android.com \
--cc=robdclark@gmail.com \
--cc=shuahkh@osg.samsung.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
all inboxes | Powered by JetHome®