From: Shuah Khan <shuah@kernel.org>
To: "Emilio López" <emilio.lopez@collabora.co.uk>
Cc: devel@driverdev.osuosl.org, gustavo.padovan@collabora.co.uk,
riandrews@android.com, daniel.vetter@ffwll.ch,
John.C.Harrison@Intel.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, ghackmann@google.com,
robdclark@gmail.com, linux-kselftest@vger.kernel.org,
maarten.lankhorst@linux.intel.com, daniels@collabora.com,
arve@android.com, emil.l.velikov@gmail.com, mpe@ellerman.id.au,
Shuah Khan <shuahkh@osg.samsung.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v2 0/7] Tests for sync infrastructure
Date: Thu, 1 Dec 2016 18:17:48 -0700 [thread overview]
Message-ID: <39b7b048-e8fb-87d3-6663-53a6ec82b5d9@kernel.org> (raw)
In-Reply-To: <20161019124954.29232-1-emilio.lopez@collabora.co.uk>
On 10/19/2016 06:49 AM, Emilio López wrote:
> 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.
>
> These tests were originally part of a battery of tests shipping with
> Android's libsync that were rewritten to use the new userspace interfaces.
>
> This is the second iteration of the test suite. Main changes over v1 are
> a reworked Makefile and small code style fixes.
>
> If you are testing this on v4.9-rc1, do note that the last test will
> currently fail due to a regression[0].
Hi Emilio,
Thanks. I will apply these to linux-kselftest next for 4.10-rc1
-- Shuah
>
> As usual, all comments are welcome.
>
> Cheers!
> Emilio
>
> [0] https://patchwork.kernel.org/patch/9343347/
>
> Emilio López (7):
> 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: stress test for parallelism
> selftest: sync: stress consumer/producer test
> selftest: sync: stress test for merges
>
> tools/testing/selftests/Makefile | 1 +
> tools/testing/selftests/sync/.gitignore | 1 +
> tools/testing/selftests/sync/Makefile | 24 +++
> tools/testing/selftests/sync/sw_sync.h | 46 +++++
> tools/testing/selftests/sync/sync.c | 221 +++++++++++++++++++++
> tools/testing/selftests/sync/sync.h | 40 ++++
> tools/testing/selftests/sync/sync_alloc.c | 74 +++++++
> tools/testing/selftests/sync/sync_fence.c | 132 ++++++++++++
> 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 | 79 ++++++++
> tools/testing/selftests/sync/sync_wait.c | 91 +++++++++
> tools/testing/selftests/sync/synctest.h | 66 ++++++
> 15 files changed, 1246 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_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
>
next prev parent reply other threads:[~2016-12-02 1:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 21:11 [PATCH 0/7] Tests for sync infrastructure Emilio López
2016-09-21 21:11 ` [PATCH 1/7] selftest: sync: basic tests for sw_sync framework Emilio López
2016-09-22 9:43 ` Michael Ellerman
2016-09-22 14:23 ` Emilio López
2016-09-27 4:23 ` Michael Ellerman
2016-09-27 14:51 ` Emilio López
2016-10-05 1:00 ` Michael Ellerman
2016-09-21 21:12 ` [PATCH 2/7] selftest: sync: fence " Emilio López
2016-09-21 21:12 ` [PATCH 3/7] selftest: sync: merge " Emilio López
2016-09-21 21:12 ` [PATCH 4/7] selftest: sync: wait " Emilio López
2016-09-21 21:12 ` [PATCH 5/7] selftest: sync: stress test for parallelism Emilio López
2016-09-21 21:12 ` [PATCH 6/7] selftest: sync: stress consumer/producer test Emilio López
2016-09-21 21:12 ` [PATCH 7/7] selftest: sync: stress test for merges Emilio López
2016-10-19 12:49 ` [PATCH v2 0/7] Tests for sync infrastructure Emilio López
2016-10-19 12:49 ` [PATCH v2 1/7] selftest: sync: basic tests for sw_sync framework Emilio López
2016-11-01 16:18 ` Gustavo Padovan
2016-12-13 16:46 ` Shuah Khan
2016-10-19 12:49 ` [PATCH v2 2/7] selftest: sync: fence " Emilio López
2016-10-19 12:49 ` [PATCH v2 3/7] selftest: sync: merge " Emilio López
2016-10-19 12:49 ` [PATCH v2 4/7] selftest: sync: wait " Emilio López
2016-10-19 12:49 ` [PATCH v2 5/7] selftest: sync: stress test for parallelism Emilio López
2016-10-19 12:49 ` [PATCH v2 6/7] selftest: sync: stress consumer/producer test Emilio López
2016-10-19 12:49 ` [PATCH v2 7/7] selftest: sync: stress test for merges Emilio López
2016-12-02 1:17 ` Shuah Khan [this message]
2016-12-02 14:08 ` [PATCH v2 0/7] Tests for sync infrastructure Shuah Khan
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=39b7b048-e8fb-87d3-6663-53a6ec82b5d9@kernel.org \
--to=shuah@kernel.org \
--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=emil.l.velikov@gmail.com \
--cc=emilio.lopez@collabora.co.uk \
--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=mpe@ellerman.id.au \
--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;
as well as URLs for NNTP newsgroup(s).