intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: add syncobj timeline support
Date: Thu, 23 May 2019 15:15:05 +0100	[thread overview]
Message-ID: <0f831de4-c263-24a3-86b9-462630657ed8@intel.com> (raw)
In-Reply-To: <155861998217.28319.181082569082578511@skylake-alporthouse-com>

On 23/05/2019 14:59, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2019-05-23 14:46:42)
>> On 23/05/2019 12:52, Chris Wilson wrote:
>>> Quoting Lionel Landwerlin (2019-05-23 12:46:20)
>>>> -               syncobj = drm_syncobj_find(file, fence.handle);
>>>> -               if (!syncobj) {
>>>> -                       DRM_DEBUG("Invalid syncobj handle provided\n");
>>>> -                       err = -ENOENT;
>>>> -                       goto err;
>>>> +                       if (user_fence.flags & __I915_EXEC_FENCE_UNKNOWN_FLAGS) {
>>>> +                               err = -EINVAL;
>>>> +                               goto err;
>>>> +                       }
>>>> +
>>>> +                       if (user_fence.flags & I915_EXEC_FENCE_WAIT) {
>>>> +                               err = drm_syncobj_find_fence(
>>>> +                                       file, user_fence.handle, user_fence.value,
>>>> +                                       DRM_SYNCOBJ_WAIT_FLAGS_WAIT_FOR_SUBMIT,
>>>> +                                       &syncobj, &fence);
>>> Is this still a synchronous wait? That would be an unfortunate change in
>>> behaviour and antithesis to having a scheduler.
>>> -Chris
>>>
>> Not sure what you mean by synchronous wait.
> drm_syncobj_find_fence() has an open-coded wait_event loop. That is
> synchronous and inconsistent with using a scheduler; where one only need
> to return a proxy fence that will be populated when the syncpt is known,
> and be signaled as a result of that syncpt.
> -Chris
>

Right,


I see this changes the behavior for existing drm_syncobjs, which was not 
intended.


For timeline drm-syncobjs, we're aware this will block and might fail if 
the fence doesn't materialize.

The Vulkan spec doesn't give a specific amount of time of which the 
submit fails, apart from it being non zero.


Will fix, thanks a lot for pointing this out.


-Lionel

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-05-23 14:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 11:46 [PATCH 0/2] drm/i915: timeline semaphore support Lionel Landwerlin
2019-05-23 11:46 ` [PATCH 1/2] drm/syncobj: add an output syncobj parameter to find_fence Lionel Landwerlin
2019-05-23 12:11   ` Zhou, David(ChunMing)
2019-05-23 13:35     ` Lionel Landwerlin
2019-05-23 13:37       ` Lionel Landwerlin
2019-05-23 11:46 ` [PATCH 2/2] drm/i915: add syncobj timeline support Lionel Landwerlin
2019-05-23 11:52   ` Chris Wilson
2019-05-23 13:46     ` Lionel Landwerlin
2019-05-23 13:59       ` Chris Wilson
2019-05-23 14:15         ` Lionel Landwerlin [this message]
2019-06-03 16:29         ` Lionel Landwerlin
2019-05-23 15:44 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: timeline semaphore support Patchwork
2019-05-23 16:16 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-25  0:59 ` ✓ Fi.CI.IGT: " 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=0f831de4-c263-24a3-86b9-462630657ed8@intel.com \
    --to=lionel.g.landwerlin@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;
as well as URLs for NNTP newsgroup(s).