[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <569983CC.7000207@google.com>
Date: Fri, 15 Jan 2016 15:42:04 -0800
From: Greg Hackmann <ghackmann@...gle.com>
To: Gustavo Padovan <gustavo.padovan@...labora.co.uk>,
John Harrison <John.C.Harrison@...el.com>
Cc: Gustavo Padovan <gustavo@...ovan.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
dri-devel@...ts.freedesktop.org, daniels@...labora.com,
Arve Hjønnevåg <arve@...roid.com>,
Riley Andrews <riandrews@...roid.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Rob Clark <robdclark@...il.com>,
Maarten Lankhorst <maarten.lankhorst@...onical.com>,
tomcherry@...gle.com, dtor@...gle.com
Subject: Re: [RFC 26/29] dma-buf/fence: remove pointless fence_timeline_signal
at destroy phase
On 01/15/2016 10:02 AM, Gustavo Padovan wrote:
> Patches 27 and 28 are attempt to fix that. I assumed that if some code is
> calling fence_timeline_destroy() it wants to stop everything so I
> worked on a solution that stops any waiter and allows the timeline to be
> destroyed.
>
> No one is using fence_timeline_destroy() in mainline now, so it is
> definately a behaviour we can discuss.
>
> Gustavo
>
+Tom Cherry and Dmitry Torokhov recently discovered that this was broken
by the refactoring of Android sync on top of dma-buf fences.
Tom and Dmitry, did you send the proposed fix upstream?
Powered by blists - more mailing lists