All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: zhoucm1 <zhoucm1@amd.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Zhou, David(ChunMing)" <David1.Zhou@amd.com>
Subject: Re: drm-sync timeline signaling
Date: Tue, 21 May 2019 14:27:23 +0100	[thread overview]
Message-ID: <9c61a8ac-9b3b-f143-4ecd-dd90b6957418@intel.com> (raw)
In-Reply-To: <cb50e114-f2e2-e8c7-e852-30bfb2fe9312@amd.com>

Thanks David,

Initially I thought we could run into wait issues with a dma_fence_chain 
with a value = 0, but you're right, it works fine.

We could just avoid to create a dma_fence_chain object, but maybe we 
don't care.

-Lionel

On 21/05/2019 09:51, zhoucm1 wrote:
> Sorry for late response.
>
> Although we don't expect that, drm_syncobj_timeline_signal_ioctl 
> already handle this case I think. Which can handle both (point value > 
> 0) and (point value = 0).
>
>
> -David
>
>
> On 2019年05月21日 16:44, Lionel Landwerlin wrote:
>> [CAUTION: External Email]
>>
>> Ping?
>>
>> On 16/05/2019 15:49, Lionel Landwerlin wrote:
>>> Hi all,
>>>
>>> While picking up the IGT tests for timeline syncobj,
>>> I noticed that although we deal with multi wait across both timeline
>>> (with point value > 0) and binary (point value = 0) syncobjs,
>>> we don't seem to have a similar behavior with signaling.
>>>
>>> Do you have any thought on this?
>>> I'm considering writing some docs but I'm not quite sure whether this
>>> difference between signaling/waiting was intentional or just 
>>> overlooked.
>>>
>>> Thanks,
>>>
>>> -Lionel
>>> _______________________________________________
>>> dri-devel mailing list
>>> dri-devel@lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
>>
>
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2019-05-21 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 14:49 drm-sync timeline signaling Lionel Landwerlin
2019-05-21  8:44 ` Lionel Landwerlin
2019-05-21  8:51   ` zhoucm1
2019-05-21 13:27     ` Lionel Landwerlin [this message]

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=9c61a8ac-9b3b-f143-4ecd-dd90b6957418@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=David1.Zhou@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=zhoucm1@amd.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 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.