From: veeras@codeaurora.org To: dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org, sumit.semwal@linaro.org, gustavo@padovan.org, airlied@linux.ie, daniel@ffwll.ch Cc: robdclark@gmail.com, sean@poorly.run, pdhaval@codeaurora.org, abhinavk@codeaurora.org, jsanka@codeaurora.org Subject: Re: [PATCH RESEND 1/2] dma-fence: allow signaling drivers to set fence timestamp Date: Wed, 18 Nov 2020 12:27:59 -0800 [thread overview] Message-ID: <56c9f6721234666dea40d316e0dd24b6@codeaurora.org> (raw) In-Reply-To: <1605205643-12746-1-git-send-email-veeras@codeaurora.org> On 2020-11-12 10:27, Veera Sundaram Sankaran wrote: > Some drivers have hardware capability to get the precise timestamp of > certain events based on which the fences are triggered. This allows it > to set accurate timestamp factoring out any software and IRQ latencies. > Move the timestamp parameter out of union in dma_fence struct to allow > signaling drivers to set it. If the parameter is not set, ktime_get is > used to set the current time to fence timestamp during > dma_fence_signal. > @Sumit Semwal / @Gustavo Padovan, Can you please help in reviewing this change as it falls in dma-fence files. Thanks, Veera > Signed-off-by: Veera Sundaram Sankaran <veeras@codeaurora.org> > --- > drivers/dma-buf/dma-fence.c | 18 ++++++++++-------- > include/linux/dma-fence.h | 15 +++------------ > 2 files changed, 13 insertions(+), 20 deletions(-) > > diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c > index 43624b4..7cef49a 100644 > --- a/drivers/dma-buf/dma-fence.c > +++ b/drivers/dma-buf/dma-fence.c > @@ -4,6 +4,7 @@ > * > * Copyright (C) 2012 Canonical Ltd > * Copyright (C) 2012 Texas Instruments > + * Copyright (c) 2020 The Linux Foundation. All rights reserved. > * > * Authors: > * Rob Clark <robdclark@gmail.com> > @@ -329,7 +330,6 @@ void __dma_fence_might_wait(void) > int dma_fence_signal_locked(struct dma_fence *fence) > { > struct dma_fence_cb *cur, *tmp; > - struct list_head cb_list; > > lockdep_assert_held(fence->lock); > > @@ -337,16 +337,18 @@ int dma_fence_signal_locked(struct dma_fence > *fence) > &fence->flags))) > return -EINVAL; > > - /* Stash the cb_list before replacing it with the timestamp */ > - list_replace(&fence->cb_list, &cb_list); > - > - fence->timestamp = ktime_get(); > + /* set current time, if not set by signaling driver */ > + if (!fence->timestamp) > + fence->timestamp = ktime_get(); > set_bit(DMA_FENCE_FLAG_TIMESTAMP_BIT, &fence->flags); > trace_dma_fence_signaled(fence); > > - list_for_each_entry_safe(cur, tmp, &cb_list, node) { > - INIT_LIST_HEAD(&cur->node); > - cur->func(fence, cur); > + if (!list_empty(&fence->cb_list)) { > + list_for_each_entry_safe(cur, tmp, &fence->cb_list, node) { > + INIT_LIST_HEAD(&cur->node); > + cur->func(fence, cur); > + } > + INIT_LIST_HEAD(&fence->cb_list); > } > > return 0; > diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h > index 09e23ad..a9eebaf 100644 > --- a/include/linux/dma-fence.h > +++ b/include/linux/dma-fence.h > @@ -4,6 +4,7 @@ > * > * Copyright (C) 2012 Canonical Ltd > * Copyright (C) 2012 Texas Instruments > + * Copyright (c) 2020 The Linux Foundation. All rights reserved. > * > * Authors: > * Rob Clark <robdclark@gmail.com> > @@ -70,26 +71,16 @@ struct dma_fence { > * release the fence it is unused. No one should be adding to the > * cb_list that they don't themselves hold a reference for. > * > - * The lifetime of the timestamp is similarly tied to both the > - * rcu freelist and the cb_list. The timestamp is only set upon > - * signaling while simultaneously notifying the cb_list. Ergo, we > - * only use either the cb_list of timestamp. Upon destruction, > - * neither are accessible, and so we can use the rcu. This means > - * that the cb_list is *only* valid until the signal bit is set, > - * and to read either you *must* hold a reference to the fence, > - * and not just the rcu_read_lock. > - * > * Listed in chronological order. > */ > union { > struct list_head cb_list; > - /* @cb_list replaced by @timestamp on dma_fence_signal() */ > - ktime_t timestamp; > - /* @timestamp replaced by @rcu on dma_fence_release() */ > + /* @cb_list replaced by @rcu on dma_fence_release() */ > struct rcu_head rcu; > }; > u64 context; > u64 seqno; > + ktime_t timestamp; > unsigned long flags; > struct kref refcount; > int error;
WARNING: multiple messages have this Message-ID (diff)
From: veeras@codeaurora.org To: dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org, sumit.semwal@linaro.org, gustavo@padovan.org, airlied@linux.ie, daniel@ffwll.ch Cc: pdhaval@codeaurora.org, sean@poorly.run, abhinavk@codeaurora.org Subject: Re: [PATCH RESEND 1/2] dma-fence: allow signaling drivers to set fence timestamp Date: Wed, 18 Nov 2020 12:27:59 -0800 [thread overview] Message-ID: <56c9f6721234666dea40d316e0dd24b6@codeaurora.org> (raw) In-Reply-To: <1605205643-12746-1-git-send-email-veeras@codeaurora.org> On 2020-11-12 10:27, Veera Sundaram Sankaran wrote: > Some drivers have hardware capability to get the precise timestamp of > certain events based on which the fences are triggered. This allows it > to set accurate timestamp factoring out any software and IRQ latencies. > Move the timestamp parameter out of union in dma_fence struct to allow > signaling drivers to set it. If the parameter is not set, ktime_get is > used to set the current time to fence timestamp during > dma_fence_signal. > @Sumit Semwal / @Gustavo Padovan, Can you please help in reviewing this change as it falls in dma-fence files. Thanks, Veera > Signed-off-by: Veera Sundaram Sankaran <veeras@codeaurora.org> > --- > drivers/dma-buf/dma-fence.c | 18 ++++++++++-------- > include/linux/dma-fence.h | 15 +++------------ > 2 files changed, 13 insertions(+), 20 deletions(-) > > diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c > index 43624b4..7cef49a 100644 > --- a/drivers/dma-buf/dma-fence.c > +++ b/drivers/dma-buf/dma-fence.c > @@ -4,6 +4,7 @@ > * > * Copyright (C) 2012 Canonical Ltd > * Copyright (C) 2012 Texas Instruments > + * Copyright (c) 2020 The Linux Foundation. All rights reserved. > * > * Authors: > * Rob Clark <robdclark@gmail.com> > @@ -329,7 +330,6 @@ void __dma_fence_might_wait(void) > int dma_fence_signal_locked(struct dma_fence *fence) > { > struct dma_fence_cb *cur, *tmp; > - struct list_head cb_list; > > lockdep_assert_held(fence->lock); > > @@ -337,16 +337,18 @@ int dma_fence_signal_locked(struct dma_fence > *fence) > &fence->flags))) > return -EINVAL; > > - /* Stash the cb_list before replacing it with the timestamp */ > - list_replace(&fence->cb_list, &cb_list); > - > - fence->timestamp = ktime_get(); > + /* set current time, if not set by signaling driver */ > + if (!fence->timestamp) > + fence->timestamp = ktime_get(); > set_bit(DMA_FENCE_FLAG_TIMESTAMP_BIT, &fence->flags); > trace_dma_fence_signaled(fence); > > - list_for_each_entry_safe(cur, tmp, &cb_list, node) { > - INIT_LIST_HEAD(&cur->node); > - cur->func(fence, cur); > + if (!list_empty(&fence->cb_list)) { > + list_for_each_entry_safe(cur, tmp, &fence->cb_list, node) { > + INIT_LIST_HEAD(&cur->node); > + cur->func(fence, cur); > + } > + INIT_LIST_HEAD(&fence->cb_list); > } > > return 0; > diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h > index 09e23ad..a9eebaf 100644 > --- a/include/linux/dma-fence.h > +++ b/include/linux/dma-fence.h > @@ -4,6 +4,7 @@ > * > * Copyright (C) 2012 Canonical Ltd > * Copyright (C) 2012 Texas Instruments > + * Copyright (c) 2020 The Linux Foundation. All rights reserved. > * > * Authors: > * Rob Clark <robdclark@gmail.com> > @@ -70,26 +71,16 @@ struct dma_fence { > * release the fence it is unused. No one should be adding to the > * cb_list that they don't themselves hold a reference for. > * > - * The lifetime of the timestamp is similarly tied to both the > - * rcu freelist and the cb_list. The timestamp is only set upon > - * signaling while simultaneously notifying the cb_list. Ergo, we > - * only use either the cb_list of timestamp. Upon destruction, > - * neither are accessible, and so we can use the rcu. This means > - * that the cb_list is *only* valid until the signal bit is set, > - * and to read either you *must* hold a reference to the fence, > - * and not just the rcu_read_lock. > - * > * Listed in chronological order. > */ > union { > struct list_head cb_list; > - /* @cb_list replaced by @timestamp on dma_fence_signal() */ > - ktime_t timestamp; > - /* @timestamp replaced by @rcu on dma_fence_release() */ > + /* @cb_list replaced by @rcu on dma_fence_release() */ > struct rcu_head rcu; > }; > u64 context; > u64 seqno; > + ktime_t timestamp; > unsigned long flags; > struct kref refcount; > int error; _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-18 20:28 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-12 18:27 [PATCH RESEND 1/2] dma-fence: allow signaling drivers to set fence timestamp Veera Sundaram Sankaran 2020-11-12 18:27 ` Veera Sundaram Sankaran 2020-11-12 18:27 ` [PATCH RESEND 2/2] drm/drm_vblank: set the dma-fence timestamp during send_vblank_event Veera Sundaram Sankaran 2020-11-12 18:27 ` Veera Sundaram Sankaran 2020-11-13 20:45 ` Daniel Vetter 2020-11-13 20:45 ` Daniel Vetter 2020-11-19 1:26 ` veeras 2020-11-19 1:26 ` veeras 2020-11-19 11:50 ` Daniel Vetter 2020-11-19 11:50 ` Daniel Vetter 2020-11-18 20:27 ` veeras [this message] 2020-11-18 20:27 ` [PATCH RESEND 1/2] dma-fence: allow signaling drivers to set fence timestamp veeras 2020-11-18 20:45 ` Daniel Vetter 2020-11-18 20:45 ` Daniel Vetter 2020-11-19 11:58 ` Daniel Vetter 2020-11-19 11:58 ` Daniel Vetter 2020-12-03 1:14 ` veeras 2020-12-03 1:14 ` veeras
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=56c9f6721234666dea40d316e0dd24b6@codeaurora.org \ --to=veeras@codeaurora.org \ --cc=abhinavk@codeaurora.org \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=gustavo@padovan.org \ --cc=jsanka@codeaurora.org \ --cc=linux-media@vger.kernel.org \ --cc=pdhaval@codeaurora.org \ --cc=robdclark@gmail.com \ --cc=sean@poorly.run \ --cc=sumit.semwal@linaro.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: linkBe 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.