From: Robert Foss <robert.foss@collabora.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
IGT development <igt-dev@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/5] tests/sw_sync: use igt_fork_helper
Date: Fri, 2 Nov 2018 13:26:53 +0100 [thread overview]
Message-ID: <8924f45e-037e-30c7-8a6a-03377e2ac9b6@collabora.com> (raw)
In-Reply-To: <20181102095726.9052-1-daniel.vetter@ffwll.ch>
Hey Daniel,
This looks good and compiles for me, feel free to add my r-b:
Reviewed-by: Robert Foss <robert.foss@collabora.com>
On 2018-11-02 10:57, Daniel Vetter wrote:
> I'll need to wrap a bit of magic around all the fork() calls in our
> tests. Simplest way to get there is to roll out the existing helpers,
> which even saves a bit of boilerplate code.
>
> Cc: Robert Foss <robert.foss@collabora.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> tests/sw_sync.c | 54 +++++++++++++++++--------------------------------
> 1 file changed, 18 insertions(+), 36 deletions(-)
>
> diff --git a/tests/sw_sync.c b/tests/sw_sync.c
> index 59603763f663..207908ed7e70 100644
> --- a/tests/sw_sync.c
> +++ b/tests/sw_sync.c
> @@ -175,6 +175,7 @@ static void test_sync_busy_fork_unixsocket(void)
> int timeline;
> int skip = 0;
> int sv[2];
> + struct igt_helper_process proc;
>
>
> timeline = sw_sync_timeline_create();
> @@ -185,9 +186,7 @@ static void test_sync_busy_fork_unixsocket(void)
> goto out;
> }
>
> - switch (fork()) {
> - case 0:
> - {
> + igt_fork_helper(&proc) {
> /* Child process */
> int socket = sv[1];
> int socket_timeline;
> @@ -213,17 +212,8 @@ static void test_sync_busy_fork_unixsocket(void)
>
> /* Advance timeline from 0 -> 1 */
> sw_sync_timeline_inc(socket_timeline, 1);
> -
> - _Exit(0);
> - break;
> - }
> - case -1:
> - {
> - /* Failed fork */
> - skip = 1;
> - break;
> }
> - default:
> +
> {
> /* Parent process */
> int socket = sv[0];
> @@ -252,15 +242,14 @@ static void test_sync_busy_fork_unixsocket(void)
>
> if (sendmsg(socket, &msg, 0) < 0) {
> skip = 1;
> - goto out;
> + } else {
> + igt_assert_f(sync_fence_wait(fence, 2*1000) == 0,
> + "Fence not signaled (timeline value 1 fence seqno 1)\n");
> }
> -
> - igt_assert_f(sync_fence_wait(fence, 2*1000) == 0,
> - "Fence not signaled (timeline value 1 fence seqno 1)\n");
> - break;
> - }
> }
>
> + igt_stop_helper(&proc);
> +
> out:
> close(fence);
> close(timeline);
> @@ -272,32 +261,25 @@ static void test_sync_busy_fork(void)
> int fence;
> int timeline;
> int skip = 0;
> + struct igt_helper_process proc;
>
> timeline = sw_sync_timeline_create();
> fence = sw_sync_timeline_create_fence(timeline, 1);
>
> - switch (fork()) {
> - case 0:
> - /* Child process */
> + igt_fork_helper(&proc) {
> usleep(1*1000*1000);
> /* Advance timeline from 0 -> 1 */
> sw_sync_timeline_inc(timeline, 1);
> - _Exit(0);
> - break;
> - case -1:
> - /* Failed fork */
> - skip = 1;
> - break;
> - default:
> - /* Parent process */
> - igt_assert_f(sync_fence_wait(fence, 0) == -ETIME,
> - "Fence signaled (it should not have been signalled yet)\n");
> -
> - igt_assert_f(sync_fence_wait(fence, 2*1000) == 0,
> - "Fence not signaled (timeline value 1 fence seqno 1)\n");
> - break;
> }
>
> + igt_assert_f(sync_fence_wait(fence, 0) == -ETIME,
> + "Fence signaled (it should not have been signalled yet)\n");
> +
> + igt_assert_f(sync_fence_wait(fence, 2*1000) == 0,
> + "Fence not signaled (timeline value 1 fence seqno 1)\n");
> +
> + igt_stop_helper(&proc);
> +
> close(fence);
> close(timeline);
> igt_require(!skip);
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-11-02 12:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 9:57 [igt-dev] [PATCH i-g-t 1/5] tests/sw_sync: use igt_fork_helper Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 2/5] tests/debugfs: use igt_display_require Daniel Vetter
2018-11-02 11:16 ` Chris Wilson
2018-11-06 17:18 ` Antonio Argenziano
2018-11-06 22:05 ` Daniel Vetter
2018-11-06 22:09 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 3/5] tests: Use igt_display_require Daniel Vetter
2018-11-06 22:09 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 4/5] lib/kms: Drop igt_display_init Daniel Vetter
2018-11-02 9:57 ` [igt-dev] [PATCH i-g-t 5/5] lib/kms: warn if we commit without outputs Daniel Vetter
2018-11-02 12:11 ` Maarten Lankhorst
2018-11-20 10:21 ` Daniel Vetter
2018-11-20 11:09 ` Maarten Lankhorst
2018-11-21 12:23 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2018-11-02 10:36 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] tests/sw_sync: use igt_fork_helper Patchwork
2018-11-02 12:07 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-11-02 12:26 ` Robert Foss [this message]
2018-11-07 19:41 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] tests/sw_sync: use igt_fork_helper (rev3) Patchwork
2018-11-08 7:23 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-11-21 15:01 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/5] tests/sw_sync: use igt_fork_helper (rev4) Patchwork
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=8924f45e-037e-30c7-8a6a-03377e2ac9b6@collabora.com \
--to=robert.foss@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@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