Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753454AbaGGNXU (ORCPT ); Mon, 7 Jul 2014 09:23:20 -0400 Received: from mail-ie0-f173.google.com ([209.85.223.173]:59320 "EHLO mail-ie0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753077AbaGGNXR (ORCPT ); Mon, 7 Jul 2014 09:23:17 -0400 MIME-Version: 1.0 X-Originating-IP: [84.73.67.144] In-Reply-To: <20140702053758.GA7578@kroah.com> References: <20140701103432.12718.82795.stgit@patser> <20140702053758.GA7578@kroah.com> Date: Mon, 7 Jul 2014 15:23:17 +0200 X-Google-Sender-Auth: KkbiSprKk9QHc6Ikruh-y7KlA_k Message-ID: Subject: Re: [PATCH v2 0/9] Updated fence patch series From: Daniel Vetter To: Greg KH Cc: Maarten Lankhorst , "open list:GENERIC INCLUDE/A..." , Thomas Hellstrom , Linux Kernel Mailing List , dri-devel , "linaro-mm-sig@lists.linaro.org" , "Clark, Rob" , Thierry Reding , Colin Cross , Sumit Semwal , "linux-media@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 2, 2014 at 7:37 AM, Greg KH wrote: >> 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? Ack from my side fwiw. Just for the record (again) about android syncpts. I think using android syncpts stuff as the official userspace interfaces for fences for userspace that wants to do explicit syncing is the sane approach - after all the (only) big platform using explicit fencing is Android since opencl is kinda not yet there really on linux (which would be the other guy really interested in explicit fencing). But before we de-stage android syncpts (and so bake in the userspace abi forever) I really want to see a full upstream gpu driver implementation using fences and running on both X+DRI userspace (implicit syncing) and android (expclicit syncing), including good test coverage for corner-cases to make sure we've addressed all warts and hidden dragons. i915 looks like the most likely candidate to get there first (we have the code for both use-cases out-of-tree after all) so I'll keep on pestering people. No promises though ;-) Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/