Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6097088yba; Tue, 14 May 2019 01:25:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqxQssYu2d5BgAZujtqr9/fWLIcDk1HVUY3ONVgRyC8WqXQPV2OxCs7MHRLDQiw1jj3j9O9l X-Received: by 2002:aa7:8e04:: with SMTP id c4mr38908631pfr.48.1557822344291; Tue, 14 May 2019 01:25:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557822344; cv=none; d=google.com; s=arc-20160816; b=k0u8XoPYCUKuMImd7+S+qnfKADkWfTFyfOjdblVn6PnTAQ286DxOLtEtYQiJpZ0Zmf aM7MyyauEUguAdACnyoXvICPcmRM9tJblkUsSgTDcW6SQXumPxCX4JGbtz76yXYiFEez PdIOh3K5DFH/9zh3JE7bCoVgn7RCh6p+EJl/vltfi9zW8itiSlXfsVmGAarA/WIgxZqg wXu7uWwOWUNHMBatubtXApAsyx60VhAeqfCAReEzHS7ihdjQMJRT6dwvcceNKnWl8EAj rBzDUPB/Rct7MPf0MJo+7JI6XJFkJ14sVtwLec7k0LbEbO70mQHkh789LGH3V1WmMM68 wIDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=uKFpAT7GrQSucExulDdH+qORJ6Ns2etUzr/PYek6Ejo=; b=wdzWaybAVkMg2zV3piovJg36XQTLuoPvVKu/aJ/b2PjR1MITy/Q5m7830VQuLM4X65 wzpuOREYW+1qOipXtY+H1PnY7AChVgYLeYofF+Dan43laaC1GVJWRN354rFxvGp3+1WT iIVdW7MWgRyp1+Vpf8ikQKBWvFyDTJL/PMI7eZFC0kgllQsiJmXTPHTUQECzzDl4fJ34 QVRl0O6EmHedm5Pc5fYTSv00TeZKGo2MbbzyGJwcjtQvG9wlQ6W5NXYK5VADB7k2d4VZ qIes196qS4Vc+nqoTVeZ5u3AnYAEB9m26XBHc7hxGj8cWVTbMcgVX+gRvaXCdhklCsjD VD9w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@imgtec.com header.s=dk201812 header.b=uv78+xKC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id ay1si13972147plb.96.2019.05.14.01.25.29; Tue, 14 May 2019 01:25:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@imgtec.com header.s=dk201812 header.b=uv78+xKC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726406AbfENIXO (ORCPT + 99 others); Tue, 14 May 2019 04:23:14 -0400 Received: from mx07-00376f01.pphosted.com ([185.132.180.163]:28378 "EHLO mx07-00376f01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725985AbfENIXO (ORCPT ); Tue, 14 May 2019 04:23:14 -0400 X-Greylist: delayed 1637 seconds by postgrey-1.27 at vger.kernel.org; Tue, 14 May 2019 04:23:12 EDT Received: from pps.filterd (m0168889.ppops.net [127.0.0.1]) by mx07-00376f01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4E7hLLU012623; Tue, 14 May 2019 08:55:42 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imgtec.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=dk201812; bh=uKFpAT7GrQSucExulDdH+qORJ6Ns2etUzr/PYek6Ejo=; b=uv78+xKCIP2KAgoPoLFzjakPS3sRS4qdQA4jVZnoFVUCXbE0As6rDPZpgOZFpxLGLw5W bIgn2bPSswq6S4LlAeBOwR0sw2DOFb3JllXfs8GWs0xiuKQ8IgqzN+kyPHvDUU3PqoCw IRV+wOq11mv3MpakmxE0ekRjIuIFa3VtKZM/e0EoaVlXPqT14i542tlMsrRjMRD9795t hksBwX+1eIgBFbGa3JodYXnlkXS7cP6rvyVR9Vv/7RSK1NC1dbZRjsWvqQxADTOKmbQ5 eOeRvzAV+5lB7ngjVxdFv6BoqQkOQJl9QQceVp5A7qSN2c60J9n9x31u1kDFBScL4lU8 tw== Received: from hhmail02.hh.imgtec.org ([217.156.249.195]) by mx07-00376f01.pphosted.com with ESMTP id 2sdpft2tqw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 14 May 2019 08:55:42 +0100 Received: from michael-imgtec (10.80.17.22) by hhmail02.hh.imgtec.org (10.100.10.21) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 14 May 2019 08:55:41 +0100 Date: Tue, 14 May 2019 15:55:37 +0800 From: Michael Yang To: Chris Wilson CC: , , , , , , Subject: Re: [EXTERNAL] Re: [PATCH] sync_file: Return reasonable timestamp when merging signaled fences Message-ID: <20190514075537.GA7483@michael-imgtec> References: <1554710495-6646-1-git-send-email-michael.yang@imgtec.com> <1557376451-20164-1-git-send-email-michael.yang@imgtec.com> <155740236592.28545.17880521046408313036@skylake-alporthouse-com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <155740236592.28545.17880521046408313036@skylake-alporthouse-com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Originating-IP: [10.80.17.22] Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 09, 2019 at 12:46:05PM +0100, Chris Wilson wrote: > Quoting Michael Yang (2019-05-09 05:34:11) > > If all the sync points were signaled in both fences a and b, > > there was only one sync point in merged fence which is a_fence[0]. > > The Fence structure in android framework might be confused about > > timestamp if there were any sync points which were signaled after > > a_fence[0]. It might be more reasonable to use timestamp of last signaled > > sync point to represent the merged fence. > > The issue can be found from EGL extension ANDROID_get_frame_timestamps. > > Sometimes the return value of EGL_READS_DONE_TIME_ANDROID is head of > > the return value of EGL_RENDERING_COMPLETE_TIME_ANDROID. > > That means display/composition had been completed before rendering > > was completed that is incorrect. > > > > Some discussion can be found at: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__android-2Dreview.googlesource.com_c_kernel_common_-2B_907009&d=DwIFaQ&c=bq9ppmgvSw3oQFfR871D_w&r=Ngg6vhouPkgwSIbDMU7rDN0ZfT2Qax50xuWkXXqQ3zw&m=N9R9dXGJ3zk0e0gXNM4tsiro7xCOLlWx6c3HAEseSSw&s=6sY2t9i2wvylWH-rPUlvY1MIuWKjCPzT8SeCgpZOIGk&e= > > > > Signed-off-by: Michael Yang > > --- > > Hi, > > I didn't get response since I previously sent this a month ago. > > Could someone have a chance to look at it please? > > Thanks. > > drivers/dma-buf/sync_file.c | 25 +++++++++++++++++++++++-- > > 1 file changed, 23 insertions(+), 2 deletions(-) > > > > diff --git a/drivers/dma-buf/sync_file.c b/drivers/dma-buf/sync_file.c > > index 4f6305c..d46bfe1 100644 > > --- a/drivers/dma-buf/sync_file.c > > +++ b/drivers/dma-buf/sync_file.c > > @@ -274,8 +274,29 @@ static struct sync_file *sync_file_merge(const char *name, struct sync_file *a, > > for (; i_b < b_num_fences; i_b++) > > add_fence(fences, &i, b_fences[i_b]); > > > > - if (i == 0) > > - fences[i++] = dma_fence_get(a_fences[0]); > > + /* If all the sync pts were signaled, then adding the sync_pt who > > + * was the last signaled to the fence. > > + */ > > + if (i == 0) { > > + struct dma_fence *last_signaled_sync_pt = a_fences[0]; > > + int iter; > > + > > + for (iter = 1; iter < a_num_fences; iter++) { > > If there is more than one fence, sync_file->fence is a fence_array and > its timestamp is what you want. If there is one fence, sync_file->fence > is a pointer to that fence, and naturally has the right timestamp. > > In short, this should be handled by dma_fence_array_create() when given > a complete set of signaled fences, it too should inherit the signaled > status with the timestamp being taken from the last fence. It should > also be careful to inherit the error status. > -Chris Thanks Chris for the inputs. For this case, there will be only one fence in sync_file->fence after doing sync_file_merge(). Regarding to the current implementation, dma_fence_array_create() is not called as num_fences is equal to 1. I was wondering do you suggest that we pass a complete set of signaled fences to sync_file_set_fence() and handle it in dma_fence_array_create(). Thanks. - Michael