Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752127AbcDOS3i (ORCPT ); Fri, 15 Apr 2016 14:29:38 -0400 Received: from mail-pf0-f169.google.com ([209.85.192.169]:35879 "EHLO mail-pf0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751005AbcDOS3g convert rfc822-to-8bit (ORCPT ); Fri, 15 Apr 2016 14:29:36 -0400 Date: Fri, 15 Apr 2016 11:29:34 -0700 From: Gustavo Padovan To: Daniel Vetter Cc: Christian =?iso-8859-1?Q?K=F6nig?= , dri-devel , Linux Kernel Mailing List , Daniel Stone , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Riley Andrews , Rob Clark , Greg Hackmann , John Harrison , Laurent Pinchart , Sean Paul , =?iso-8859-1?Q?St=E9phane?= Marchesin , m.chehab@samsung.com, Maarten Lankhorst , Gustavo Padovan Subject: Re: [RFC 1/8] dma-buf/fence: add fence_collection fences Message-ID: <20160415182934.GB23954@joana> Mail-Followup-To: Gustavo Padovan , Daniel Vetter , Christian =?iso-8859-1?Q?K=F6nig?= , dri-devel , Linux Kernel Mailing List , Daniel Stone , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Riley Andrews , Rob Clark , Greg Hackmann , John Harrison , Laurent Pinchart , Sean Paul , =?iso-8859-1?Q?St=E9phane?= Marchesin , m.chehab@samsung.com, Maarten Lankhorst , Gustavo Padovan References: <1460683781-22535-1-git-send-email-gustavo@padovan.org> <1460683781-22535-2-git-send-email-gustavo@padovan.org> <20160415080254.GQ2510@phenom.ffwll.local> <5710AE61.9040308@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: 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: 979 Lines: 23 2016-04-15 Daniel Vetter : > On Fri, Apr 15, 2016 at 11:03 AM, Christian K?nig > wrote: > > Might be that how amdgpu uses the fence context and sequence number is a bit > > questionable, but this will completely break it. > > You mean it tries to qualesce fences in the same context down to just > the last one? That's how it's supposed to be done, and > fence_collections do break this somewhat. Without fixing up > fence_is_later and friends. Sounds like amdgpu is a good use case to > make sure the changes in semantics in these functions result in > sensible code. In a way a fence_collection is a fence where the > timeline never matches with any other timeline (since it's a > combiation). > > And yeah I think fence_collection should probably compress down the > fences to 1 per timeline. But then that's just an implementation > detail we can fix later on. You mean asking for a new context for every collection? Gustavo