All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] dma-buf/sw_sync: force signal all unsignaled fences on dying timeline
Date: Fri, 8 Sep 2017 10:03:00 -0300	[thread overview]
Message-ID: <20170908130300.GA18055@jade> (raw)
In-Reply-To: <150481150489.4093.15815539749628106279@mail.alporthouse.com>

Hi Chris,

2017-09-07 Chris Wilson <chris@chris-wilson.co.uk>:

> Quoting Gustavo Padovan (2017-09-07 20:02:46)
> > From: Dominik Behr <dbehr@chromium.org>
> > 
> > To avoid hanging userspace components that might have been waiting on the
> > active fences of the destroyed timeline we need to signal with error all
> > remaining fences on such timeline.
> > 
> > This restore the default behaviour of the Android sw_sync framework, which
> > Android still relies on. It was broken on the dma fence conversion a few
> > years ago and never fixed.
> > 
> > v2: Do not bother with cleanup do the list (Chris Wilson)
> > 
> > Signed-off-by: Dominik Behr <dbehr@chromium.org>
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> > ---
> >  drivers/dma-buf/sw_sync.c | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> > 
> > diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c
> > index 38cc7389a6c1..f183eef074fd 100644
> > --- a/drivers/dma-buf/sw_sync.c
> > +++ b/drivers/dma-buf/sw_sync.c
> > @@ -321,9 +321,19 @@ static int sw_sync_debugfs_open(struct inode *inode, struct file *file)
> >  static int sw_sync_debugfs_release(struct inode *inode, struct file *file)
> >  {
> >         struct sync_timeline *obj = file->private_data;
> > +       struct sync_pt *pt, *next;
> >  
> >         smp_wmb();
> >  
> > +       spin_lock_irq(&obj->lock);
> 
> Given the spinlock, that uncommented barrier (what is it paired with?)
> above is redundant.

Okay, I'll remove the barrier and push that patch, I assume your r-b
will comtemplate that as well?

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

  reply	other threads:[~2017-09-08 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 19:02 [PATCH v2 1/2] selftests: sync: add test that waits on a destroyed timeline Gustavo Padovan
2017-09-07 19:02 ` [PATCH v2 2/2] dma-buf/sw_sync: force signal all unsignaled fences on dying timeline Gustavo Padovan
2017-09-07 19:11   ` Chris Wilson
2017-09-08 13:03     ` Gustavo Padovan [this message]
2017-09-08 13:07       ` Chris Wilson
2017-09-07 19:09 ` [PATCH v2 1/2] selftests: sync: add test that waits on a destroyed timeline Chris Wilson

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=20170908130300.GA18055@jade \
    --to=gustavo@padovan.org \
    --cc=chris@chris-wilson.co.uk \
    --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.