From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 15/16] drm/i915: Add a simple fence selftest to i915_gem_request
Date: Fri, 9 Dec 2016 16:02:49 +0000 [thread overview]
Message-ID: <88e74ae4-04b5-9c08-8f85-042c9f4e2249@linux.intel.com> (raw)
In-Reply-To: <20161207135833.32740-16-chris@chris-wilson.co.uk>
On 07/12/2016 13:58, Chris Wilson wrote:
> Do a quick selftest on in the interoperability of dma_fence_wait on a
> i915_gem_request.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem_request.c | 51 +++++++++++++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_request.c b/drivers/gpu/drm/i915/i915_gem_request.c
> index 9ba17d3e35cb..2bde3fc8e8bf 100644
> --- a/drivers/gpu/drm/i915/i915_gem_request.c
> +++ b/drivers/gpu/drm/i915/i915_gem_request.c
> @@ -1648,11 +1648,62 @@ static int igt_wait_request(void *ignore)
> return err;
> }
>
> +static int igt_fence_wait(void *ignore)
> +{
> + struct drm_i915_private *i915;
> + struct drm_i915_gem_request *request;
> + int err = -ENOMEM;
> +
> + i915 = mock_device();
> + if (!i915)
> + goto out;
> +
> + err = -EINVAL;
> + mutex_lock(&i915->drm.struct_mutex);
> + request = mock_request(i915->engine[RCS],
> + i915->kernel_context,
> + HZ);
Even slower than the previous one. :)
> + if (!request) {
> + mutex_unlock(&i915->drm.struct_mutex);
> + goto out_device;
> + }
> +
> + i915_add_request(request);
> + mutex_unlock(&i915->drm.struct_mutex);
> +
> + if (dma_fence_is_signaled(&request->fence)) {
> + pr_err("fence signaled immediately!\n");
> + goto out_device;
> + }
> +
> + if (dma_fence_wait_timeout(&request->fence, false, 1) != -ETIME) {
> + pr_err("fence wait success after submit (expected timeout)!\n");
> + goto out_device;
> + }
> +
> + if (dma_fence_wait_timeout(&request->fence, false, 2 * HZ) <= 0) {
> + pr_err("fence wait timed out (expected success)!\n");
> + goto out_device;
> + }
> +
> + if (!dma_fence_is_signaled(&request->fence)) {
> + pr_err("fence unsignaled after waiting!\n");
> + goto out_device;
> + }
And the error codes.
> +
> + err = 0;
> +out_device:
> + mock_device_free(i915);
> +out:
> + return err;
> +}
> +
> int i915_gem_request_selftest(void)
> {
> static const struct i915_subtest tests[] = {
> SUBTEST(igt_add_request),
> SUBTEST(igt_wait_request),
> + SUBTEST(igt_fence_wait),
> };
>
> return i915_subtests(tests, NULL);
>
See if you can speed it up, but that is optional.
Just some better failure codes from the test and then:
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-09 16:03 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 13:58 [RFC] Smattering of selftests Chris Wilson
2016-12-07 13:58 ` [PATCH 01/16] drm/i915: Provide a hook for selftests Chris Wilson
2016-12-08 10:47 ` Tvrtko Ursulin
2016-12-08 11:15 ` Chris Wilson
2016-12-08 12:30 ` Tvrtko Ursulin
2016-12-08 12:40 ` Chris Wilson
2016-12-07 13:58 ` [PATCH 02/16] kselftests: Exercise hw-independent mock tests for i915.ko Chris Wilson
2016-12-07 14:09 ` Chris Wilson
2016-12-08 15:50 ` Shuah Khan
2016-12-08 16:01 ` Chris Wilson
2016-12-08 16:44 ` Shuah Khan
2016-12-07 13:58 ` [PATCH 03/16] drm/i915: Add unit tests for the breadcrumb rbtree, insert/remove Chris Wilson
2016-12-08 11:00 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 04/16] drm/i915: Add unit tests for the breadcrumb rbtree, completion Chris Wilson
2016-12-08 11:47 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 05/16] drm/i915: Add unit tests for the breadcrumb rbtree, wakeups Chris Wilson
2016-12-08 17:38 ` Tvrtko Ursulin
2016-12-08 21:04 ` Chris Wilson
2016-12-09 9:33 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 06/16] drm/i915: Add a reminder that i915_vma_move_to_active() requires struct_mutex Chris Wilson
2016-12-08 17:40 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 07/16] drm/i915: Move intel_lrc_context_pin() to avoid the forward declaration Chris Wilson
2016-12-08 17:45 ` Tvrtko Ursulin
2016-12-08 20:55 ` Chris Wilson
2016-12-07 13:58 ` [PATCH 08/16] drm/i915: Unify active context tracking between legacy/execlists/guc Chris Wilson
2016-12-09 11:48 ` Tvrtko Ursulin
2016-12-09 12:17 ` Chris Wilson
2016-12-07 13:58 ` [PATCH 09/16] drm/i915: Simplify releasing context reference Chris Wilson
2016-12-09 15:03 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 10/16] drm/i915: Mark the shadow gvt context as closed Chris Wilson
2016-12-09 15:07 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 11/16] drm/i915/execlists: Request the kernel context be pinned high Chris Wilson
2016-12-09 15:08 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 12/16] drm/i915: Swap if(enable_execlists) in i915_gem_request_alloc for a vfunc Chris Wilson
2016-12-09 15:16 ` Tvrtko Ursulin
2016-12-09 15:25 ` Chris Wilson
2016-12-09 15:53 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 13/16] drm/i915: Add selftests for i915_gem_request Chris Wilson
2016-12-09 15:51 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 14/16] drm/i915: Add a simple request selftest for waiting Chris Wilson
2016-12-09 15:59 ` Tvrtko Ursulin
2016-12-07 13:58 ` [PATCH 15/16] drm/i915: Add a simple fence selftest to i915_gem_request Chris Wilson
2016-12-09 16:02 ` Tvrtko Ursulin [this message]
2016-12-07 13:58 ` [PATCH 16/16] drm/i915: Add selftests for object allocation, phys Chris Wilson
2016-12-13 17:10 ` Tvrtko Ursulin
2016-12-17 13:55 ` Chris Wilson
2016-12-07 14:04 ` [RFC] Smattering of selftests Chris Wilson
2016-12-07 15:45 ` ✓ Fi.CI.BAT: success for series starting with [01/16] drm/i915: Provide a hook for selftests Patchwork
2016-12-07 18:52 ` [PATCH 1/2] drm/i915: Move uncore selfchecks to late selftest infrastructure Chris Wilson
2016-12-07 18:52 ` [PATCH 2/2] drm/i915: Test all fw tables during mock selftests Chris Wilson
2016-12-08 12:14 ` Tvrtko Ursulin
2016-12-08 12:28 ` Chris Wilson
2016-12-08 13:11 ` Joonas Lahtinen
2016-12-08 16:52 ` Tvrtko Ursulin
2016-12-08 22:29 ` Chris Wilson
2016-12-09 9:41 ` Tvrtko Ursulin
2016-12-09 10:18 ` Chris Wilson
2016-12-09 10:35 ` Tvrtko Ursulin
2016-12-09 10:51 ` Chris Wilson
2016-12-08 11:58 ` [PATCH 1/2] drm/i915: Move uncore selfchecks to late selftest infrastructure Tvrtko Ursulin
2016-12-07 19:56 ` [RFC] Smattering of selftests Paulo Zanoni
2016-12-07 20:52 ` ✓ Fi.CI.BAT: success for series starting with [01/16] drm/i915: Provide a hook for selftests (rev2) 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=88e74ae4-04b5-9c08-8f85-042c9f4e2249@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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