From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maarten Lankhorst Subject: Re: [PATCH v2 0/9] Updated fence patch series Date: Wed, 02 Jul 2014 11:12:32 +0200 Message-ID: <53B3CD00.5030003@canonical.com> References: <20140701103432.12718.82795.stgit@patser> <20140702053758.GA7578@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by gabe.freedesktop.org (Postfix) with ESMTP id 7AD446E3D4 for ; Wed, 2 Jul 2014 02:13:00 -0700 (PDT) In-Reply-To: <20140702053758.GA7578@kroah.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Greg KH Cc: linux-arch@vger.kernel.org, thellstrom@vmware.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, ccross@google.com, linux-media@vger.kernel.org List-Id: dri-devel@lists.freedesktop.org op 02-07-14 07:37, Greg KH schreef: > On Tue, Jul 01, 2014 at 12:57:02PM +0200, Maarten Lankhorst wrote: >> So after some more hacking I've moved dma-buf to its own subdirectory, >> drivers/dma-buf and applied the fence patches to its new place. I believe that the >> first patch should be applied regardless, and the rest should be ready now. >> :-) >> >> Changes to the fence api: >> - release_fence -> fence_release etc. >> - __fence_init -> fence_init >> - __fence_signal -> fence_signal_locked >> - __fence_is_signaled -> fence_is_signaled_locked >> - Changing BUG_ON to WARN_ON in fence_later, and return NULL if it triggers. >> >> Android can expose fences to userspace. It's possible to make the new fence >> mechanism expose the same fences to userspace by changing sync_fence_create >> to take a struct fence instead of a struct sync_pt. No other change is needed, >> because only the fence parts of struct sync_pt are used. But because the >> userspace fences are a separate problem and I haven't really looked at it yet >> I feel it should stay in staging, for now. > Ok, that's reasonable. > > At first glance, this all looks "sane" to me, any objection from anyone > if I merge this through my driver-core tree for 3.17? > Sounds good to me, let me know when you pull it in, so I can rebase my drm conversion on top of it. :-) ~Maarten