Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752314AbcCaKEq (ORCPT ); Thu, 31 Mar 2016 06:04:46 -0400 Received: from mail-wm0-f53.google.com ([74.125.82.53]:35918 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750849AbcCaKEo (ORCPT ); Thu, 31 Mar 2016 06:04:44 -0400 Date: Thu, 31 Mar 2016 12:04:46 +0200 From: Daniel Vetter To: Daniel Stone Cc: Inki Dae , Rob Clark , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Daniel Vetter , Riley Andrews , Gustavo Padovan , John Harrison Subject: Re: [RFC 0/6] drm/fences: add in-fences to DRM Message-ID: <20160331100446.GY2510@phenom.ffwll.local> Mail-Followup-To: Daniel Stone , Inki Dae , Rob Clark , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Riley Andrews , Gustavo Padovan , John Harrison References: <56F47D01.7040508@samsung.com> <56F88828.5050304@samsung.com> <56F9E613.1030902@samsung.com> <56FCD5A3.4040700@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Linux phenom 4.4.0-1-amd64 User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 707 Lines: 16 On Thu, Mar 31, 2016 at 10:35:11AM +0100, Daniel Stone wrote: > Well, it has to be one or the other: mixing explicit and implicit, > defeats the purpose of using explicit fencing. So, when explicit > fencing is in use, implicit fences must be ignored. You can mix it, if you're careful. CrOS wants that to better mesh android with Ozone, and we'll be discussing what needs to be added to be able to make it work implicit and explicit fencing work together, in both directions. Of course this should only be used for shared buffers, e.g. explicit syncing in an android client running on top of implicitly synced ozone/kms. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch