All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: "Koenig, Christian" <Christian.Koenig@amd.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] dma-fence: Simply wrap dma_fence_signal_locked with dma_fence_signal
Date: Fri, 16 Aug 2019 21:07:24 +0200	[thread overview]
Message-ID: <CAKMK7uGWV431+Ru7qTMWk72dHPXe_UJDj-PA02p64PET0XYZEg@mail.gmail.com> (raw)
In-Reply-To: <77eab42b-2404-0ba4-b323-948c040c3759@amd.com>

On Fri, Aug 16, 2019 at 9:02 PM Koenig, Christian
<Christian.Koenig@amd.com> wrote:
>
> Am 16.08.19 um 17:21 schrieb Chris Wilson:
> > Currently dma_fence_signal() tries to avoid the spinlock and only takes
> > it if absolutely required to walk the callback list. However, to allow
> > for some users to surreptitiously insert lazy signal callbacks that
> > do not depend on enabling the signaling mechanism around every fence,
> > we always need to notify the callbacks on signaling. As such, we will
> > always need to take the spinlock and dma_fence_signal() effectively
> > becomes a clone of dma_fence_signal_locked().
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Christian König <christian.koenig@amd.com>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > ---
> >   drivers/dma-buf/dma-fence.c | 19 +++++--------------
> >   1 file changed, 5 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c
> > index ff0cd6eae766..f23eb9f19b4e 100644
> > --- a/drivers/dma-buf/dma-fence.c
> > +++ b/drivers/dma-buf/dma-fence.c
> > @@ -176,6 +176,7 @@ EXPORT_SYMBOL(dma_fence_signal_locked);
> >   int dma_fence_signal(struct dma_fence *fence)
> >   {
> >       unsigned long flags;
> > +     int ret;
> >
> >       if (!fence)
> >               return -EINVAL;
> > @@ -183,21 +184,11 @@ int dma_fence_signal(struct dma_fence *fence)
> >       if (test_and_set_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->flags))
> >               return -EINVAL;
>
> I need to take my review back. You also need to drop this
> test_and_set_bit here or your completely break drivers using this.

Time for a pile of dma_fence selftests? Maybe with a bit of dma_resv
thrown in for good? This stuff is tricky, and it feels like we had a
few oopsies in review recently ...
-Daniel

> Regards,
> Christian.
>
> >
> > -     fence->timestamp = ktime_get();
> > -     set_bit(DMA_FENCE_FLAG_TIMESTAMP_BIT, &fence->flags);
> > -     trace_dma_fence_signaled(fence);
> > -
> > -     if (test_bit(DMA_FENCE_FLAG_ENABLE_SIGNAL_BIT, &fence->flags)) {
> > -             struct dma_fence_cb *cur, *tmp;
> > +     spin_lock_irqsave(fence->lock, flags);
> > +     ret = dma_fence_signal_locked(fence);
> > +     spin_unlock_irqrestore(fence->lock, flags);
> >
> > -             spin_lock_irqsave(fence->lock, flags);
> > -             list_for_each_entry_safe(cur, tmp, &fence->cb_list, node) {
> > -                     list_del_init(&cur->node);
> > -                     cur->func(fence, cur);
> > -             }
> > -             spin_unlock_irqrestore(fence->lock, flags);
> > -     }
> > -     return 0;
> > +     return ret;
> >   }
> >   EXPORT_SYMBOL(dma_fence_signal);
> >
>


-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-08-16 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 15:21 [PATCH 1/2] dma-buf: Avoid list_del during fence->cb_list iteration Chris Wilson
2019-08-16 15:21 ` [PATCH 2/2] dma-fence: Simply wrap dma_fence_signal_locked with dma_fence_signal Chris Wilson
2019-08-16 19:02   ` Koenig, Christian
2019-08-16 19:07     ` Daniel Vetter [this message]
2019-08-16 19:28       ` Chris Wilson
2019-08-16 16:14 ` [PATCH 1/2] dma-buf: Avoid list_del during fence->cb_list iteration Koenig, Christian

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=CAKMK7uGWV431+Ru7qTMWk72dHPXe_UJDj-PA02p64PET0XYZEg@mail.gmail.com \
    --to=daniel.vetter@ffwll.ch \
    --cc=Christian.Koenig@amd.com \
    --cc=dri-devel@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.