All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: mesa-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	Daniel Stone <daniels@collabora.com>
Subject: Re: [PATCH v1 00/13] Implement sw_sync test
Date: Wed, 24 Aug 2016 16:41:02 -0400	[thread overview]
Message-ID: <20160824204102.GH17171@joana> (raw)
In-Reply-To: <20160824060142.GY10980@phenom.ffwll.local>

2016-08-24 Daniel Vetter <daniel@ffwll.ch>:

> On Tue, Aug 23, 2016 at 01:56:02PM -0400, robert.foss@collabora.com wrote:
> > From: Robert Foss <robert.foss@collabora.com>
> > 
> > This series implements the sw_sync test and the lib/sw_sync helper functions
> > for said test.
> > 
> > Gustavo Padovans sw_sync series was just de-staged in
> > gregkh-staging/staging-next [1], and this test is targeted at verifying the
> > functionality implemented in that series.
> > 
> > The sw_sync subtests range from very basic tests of the sw_sync functionality,
> > to stress testing and randomized tests.
> > 
> > [1] http://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/
> 
> This seems to be patches against igt (but the series is lacking the i-g-t-
> subject tag per CONTRIBUTING). I'm ok with that, but I thought the idea
> was to merge these testcases into the kernel's selftests? Did the plan
> change?

We still have the tests for kernel's selftests and the plan is to
upstream them but I think getting complete tests explicit fencing
infrastructure in i-g-t is good idea too. We work on more complex tests
in there and leave kselftest with the basic tests from the initial
patchset for the sw_sync kselftest.

	Gustavo

_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

  parent reply	other threads:[~2016-08-24 20:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 17:56 [PATCH v1 00/13] Implement sw_sync test robert.foss
2016-08-23 17:56 ` [PATCH v1 01/13] lib/sw_sync: Add helper functions for managing synchronization primitives robert.foss
2016-08-23 22:05   ` [Mesa-dev] " Eric Engestrom
2016-08-23 17:56 ` [PATCH v1 02/13] tests/sw_sync: Add sw_sync test robert.foss
2016-08-23 22:12   ` [Mesa-dev] " Eric Engestrom
2016-08-23 17:56 ` [PATCH v1 03/13] tests/sw_sync: Add subtest test_alloc_fence robert.foss
2016-08-23 17:56 ` [PATCH v1 04/13] tests/sw_sync: Add subtest test_alloc_fence_invalid_timeline robert.foss
2016-08-23 17:56 ` [PATCH v1 05/13] tests/sw_sync: Add subtest test_alloc_merge_fence robert.foss
2016-08-23 17:56 ` [PATCH v1 06/13] tests/sw_sync: Add subtest test_sync_wait robert.foss
2016-08-23 17:56 ` [PATCH v1 07/13] tests/sw_sync: Add subtest test_sync_merge robert.foss
2016-08-23 17:56 ` [PATCH v1 08/13] tests/sw_sync: Add subtest test_sync_merge_same robert.foss
2016-08-23 17:56 ` [PATCH v1 09/13] tests/sw_sync: Add subtest test_sync_multi_consumer robert.foss
2016-08-23 17:56 ` [PATCH v1 10/13] tests/sw_sync: Add subtest test_sync_multi_consumer_producer robert.foss
2016-08-23 17:56 ` [PATCH v1 11/13] tests/sw_sync: Add subtest test_sync_random_merge robert.foss
2016-08-23 22:38   ` Eric Engestrom
2016-08-23 17:56 ` [PATCH v1 12/13] tests/sw_sync: Add subtest test_sync_multi_timeline_wait robert.foss
2016-08-23 17:56 ` [PATCH v1 13/13] tests/sw_sync: Add subtest test_sync_multi_producer_single_consumer robert.foss
2016-08-23 22:56 ` [Mesa-dev] [PATCH v1 00/13] Implement sw_sync test Eric Engestrom
2016-08-24 20:27   ` Robert Foss
2016-08-24  6:01 ` Daniel Vetter
2016-08-24 13:51   ` Robert Foss
2016-08-24 20:41   ` Gustavo Padovan [this message]
2016-08-25  6:56     ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2016-08-23 17:53 robert.foss

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=20160824204102.GH17171@joana \
    --to=gustavo.padovan@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mesa-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.