Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp5401230img; Wed, 27 Mar 2019 07:54:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqyGv2HKod5sok0kSdRYROETOw6ykEfLPxD2Suwt8/ICwdRtRKFllC4Dzd1aP7QoaD0FTRtf X-Received: by 2002:a62:307:: with SMTP id 7mr14148913pfd.259.1553698481922; Wed, 27 Mar 2019 07:54:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553698481; cv=none; d=google.com; s=arc-20160816; b=iz+rFLd7Isv1nyhEv5THsFICu1tB5iYrPjeNfin4nO2iWCcZF9C4+Y8OSSYqO/zPcd 8/e8ZygDaUjcBZcjZsd9iUAEGCuxpUrQd/bYFbf+YnMVQmpoI4DSW5rj8Y2wmxisrA+y AsWqx8zgTU9DnjqMSuHM96swOSDL5OW9E4UdJgUPky8nPt+V+LxcYi8oGsWE5OG31s9g tU1W4Ctg6fHHDpPTs66xjQKzsXGUpZtCn3gfKQFP4Xr6huEtraDyas7+QhnxzYJcky2R mzq99n2Bi2ooOmDjigSicBxKW/O+q8aGB63KDgwXeY29tTxvbMzUQhZJRDPOjqkpjSsR OpPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=mEpGIQC5OezqJU8AwwswvJ5tJSp4EH9zwnzBibNlD44=; b=CdyzGzN+BOgzJz+nWrZ/2gTgewL+k1+67aivECkUj0tcMlBi/2WX+AA6r50aM1A6DJ wJxelRnguquM2Yxr9suXVXTjw+vYlc0I01+++WM+jq9GAFyzJuMPgGtj5zkbDZbxqpRO gsZwoKuH5tYgXjaHxNl9LhuC56vIhhqIj/Vo13B1vVpgwh8nAvjidTrETRTrjjCx7awM eIDBJSAUJjXiC9vjTCecrfwkZLI8MjV0c9WLE25k0ncGwCWN34vs3aQpywkPzdwmmUi/ GUp3/+zu7Gfq0TF0cH3yW+vNWJj/K8VuBp+MOvhZ8a96SO5epL1WypdOc1X6ZysLkaLi ejUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=kDfBZYOC; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h6si18061311pfc.255.2019.03.27.07.54.26; Wed, 27 Mar 2019 07:54:41 -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=@gmail.com header.s=20161025 header.b=kDfBZYOC; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728581AbfC0OwX (ORCPT + 99 others); Wed, 27 Mar 2019 10:52:23 -0400 Received: from mail-ed1-f68.google.com ([209.85.208.68]:42549 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728079AbfC0OwX (ORCPT ); Wed, 27 Mar 2019 10:52:23 -0400 Received: by mail-ed1-f68.google.com with SMTP id x61so8618730edc.9; Wed, 27 Mar 2019 07:52:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mEpGIQC5OezqJU8AwwswvJ5tJSp4EH9zwnzBibNlD44=; b=kDfBZYOCsfrVcQAgDzL+tYP0Ca79Mbw5Md7oxrrtAYJ+NVY47qDB5pEE74teM0xTtl YRDRoPPT8Jf4np/JV/1limIO4SYJYen6Qbel387EMiQwaek/Z0wPW45BrYxY9pjUneOZ ESiKMDwjLXB6vZ/K42o82isK/+qWcPAiUyIt8b66ReMcwdYqe0fMCpoyKupZQW2VO4z9 WZKgWpWufkRrGOFi52jbJvK0VcdpaO6AmsSdTO9LIsuwGBn2C7OgStQRSVCXw7VBKS8F iDUBXA1ETjdFN/clyF47ib7BtE8+EB/K8Nex+rC+jIfW1EDCkiOdAwcTZdncNj8thtq4 F32w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mEpGIQC5OezqJU8AwwswvJ5tJSp4EH9zwnzBibNlD44=; b=Fft6DTYyPu5N5f44iTNJvuQK6wrO1wgeNcOrWFNgIcFYbu5tsC9cCGEO4zF7MBprXi Je6JbALJHJuJ3Mz4q2r49vn2KncxpmP5Z8b0sHTn4FWY5dOxbFS5JEURHSjn3EceVxWE cPY3zJrmsYAAYKDVBNyMaBkwSJn23yFvs3Xd6yqYxTOp5Z5on/WhVnWFQxl952cvvAM3 eJ1hOLCpPqNSiWbbolMhPY5aGCjL/VHtwqH4qnIn87mEEU4ENBY0D1YgW/3YmmJ9v8X3 EuPB9/6dG0IYeM40FUh1H7yYjw9bjaW+2WdXsve5U1LlCozlW6tmio3LEEMUAUMpBhJX nzLQ== X-Gm-Message-State: APjAAAVj1QpEbXV3pCgZGSSxXBxt4+10oxkK3NJEGmzPUbJXQa5mRB+3 U1lk62w9AD7AO93hx0BbxoOs/lED7If21IBPmx8= X-Received: by 2002:a17:906:69c3:: with SMTP id g3mr20707127ejs.245.1553698340825; Wed, 27 Mar 2019 07:52:20 -0700 (PDT) MIME-Version: 1.0 References: <20190314002027.7833-1-helen.koike@collabora.com> <20190314002027.7833-4-helen.koike@collabora.com> In-Reply-To: <20190314002027.7833-4-helen.koike@collabora.com> From: Rob Clark Date: Wed, 27 Mar 2019 10:52:09 -0400 Message-ID: Subject: Re: [PATCH v3 3/5] drm/msm: fix fb references in async update To: Helen Koike Cc: dri-devel , nicholas.kazlauskas@amd.com, "Grodzovsky, Andrey" , Daniel Vetter , Linux Kernel Mailing List , Tomasz Figa , boris.brezillon@collabora.com, David Airlie , Sean Paul , kernel@collabora.com, Harry Wentland , =?UTF-8?Q?St=C3=A9phane_Marchesin?= , stable , Sean Paul , linux-arm-msm , =?UTF-8?B?VmlsbGUgU3lyasOkbMOk?= , Maarten Lankhorst , freedreno , Mamta Shukla , Daniel Vetter Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 13, 2019 at 8:21 PM Helen Koike wrote: > > Async update callbacks are expected to set the old_fb in the new_state > so prepare/cleanup framebuffers are balanced. > > Cc: # v4.14+ > Fixes: 224a4c970987 ("drm/msm: update cursors asynchronously through atomic") > Suggested-by: Boris Brezillon > Signed-off-by: Helen Koike > > --- > Hello, > > As mentioned in the cover letter, > But I couldn't test on MSM because I don't have the hardware and I would > appreciate if anyone could test it. > > In other platforms (VC4, AMD, Rockchip), there is a hidden > drm_framebuffer_get(new_fb)/drm_framebuffer_put(old_fb) in async_update > that is wrong, but I couldn't identify those here, not sure if it is hidden > somewhere else, but if tests fail this is probably the cause. > > Thanks! > Helen Apologies, I haven't had a chance to test this yet, and it is likely to be a few weeks before I have a chance.. That said, not refcnt'ing the fb seems suspicious. I read the explanation in the other patches, but kind of think it is more clear to keep the extra refcnt'ing.. or at least have a comment. I do a bit wonder if we hold the ref to the outgoing cursor long enough.. I think the hw will actually continue to scan it out until the next vblank. But Archit was the one who added async_update support so maybe that is handled somewhere else. It's been a while since I've looked at this. BR, -R > > Changes in v3: None > Changes in v2: > - update CC stable and Fixes tag > > drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c b/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c > index be13140967b4..b854f471e9e5 100644 > --- a/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c > +++ b/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c > @@ -502,6 +502,8 @@ static int mdp5_plane_atomic_async_check(struct drm_plane *plane, > static void mdp5_plane_atomic_async_update(struct drm_plane *plane, > struct drm_plane_state *new_state) > { > + struct drm_framebuffer *old_fb = plane->state->fb; > + > plane->state->src_x = new_state->src_x; > plane->state->src_y = new_state->src_y; > plane->state->crtc_x = new_state->crtc_x; > @@ -524,6 +526,8 @@ static void mdp5_plane_atomic_async_update(struct drm_plane *plane, > > *to_mdp5_plane_state(plane->state) = > *to_mdp5_plane_state(new_state); > + > + new_state->fb = old_fb; > } > > static const struct drm_plane_helper_funcs mdp5_plane_helper_funcs = { > -- > 2.20.1 >