Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp465480ybj; Tue, 5 May 2020 01:54:01 -0700 (PDT) X-Google-Smtp-Source: APiQypJY+V7DR9RinHHDMf+LK0wPx+YwUobYCcJX8vnedReqeXI9c+cA/vG+zh2s+JxXKB1NSEvq X-Received: by 2002:a50:e806:: with SMTP id e6mr1668213edn.153.1588668841376; Tue, 05 May 2020 01:54:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588668841; cv=none; d=google.com; s=arc-20160816; b=u0BGuFJJXQJZlSbxFTz3VTqUEVeerqWFxlEM0y/8phbOLWCBZhhPqr4XvJFneC/Mjw m8IwC1Ha7WJf5jheCgToium9bSgGTjITsHbVpQUmJnQKwPOz8JRl4UDeyeveKfeuz6HT r2NUQDGqGPhxON70Zzpl3gTaOy/TNtCOg30Tclvq2J3Kj+iKwRoKcdJYJUhE9w5SNDPq vJHTOXN1qwf3kWwJ8JTkTarJmgqiR8Vd20n4SzoV2dKl6zqw1bHChXRInn8J/l9u28uq 3ZCn8bGS/a+vMgtdS4VcXZ8zbO3j3I9XjtdqrD7tfZAzqO7uYySawe8dmTfCaokhCBa+ e3xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature; bh=T87EAHnU6d/aEcc9kDIRejNNG+CQtK0nds65OFUdB2k=; b=wrBs1X7OQh6IffHqUp4pTlG29D6P0FoE6CmR5bO6a6kW63XVlB8txwIE0HgxA1hghm Iomtb9IXxoTc397mFjzvy1DM6qrUxv048qVW8W++vaq2A62nc0WbzZEsx4n6b+29mmOp MiKgWLwAJCcYB218iPiA54wAqQOU8SjwYAV4AtdQCQ1/rp4s5oa36NDnfPNfLMUDW9jQ M/1XHmFTTN2kJtKeqIrnp2sMUeoDByUzmkJyjHpCgrg075f1YsBKC6QyQAhn/qhtOrC/ +hiM5ja66yL43HfLO2ALVmQRpdOgNIIVe1zFjx+RcENMl8q/N5gGPkGazknr9QwEy8Qw D7kA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=GT3MqCeI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a4si1200225edf.478.2020.05.05.01.53.37; Tue, 05 May 2020 01:54:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=GT3MqCeI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728565AbgEEIvw (ORCPT + 99 others); Tue, 5 May 2020 04:51:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54550 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725833AbgEEIvv (ORCPT ); Tue, 5 May 2020 04:51:51 -0400 Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 32729C061A0F for ; Tue, 5 May 2020 01:51:51 -0700 (PDT) Received: by mail-wr1-x441.google.com with SMTP id j5so932499wrq.2 for ; Tue, 05 May 2020 01:51:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=T87EAHnU6d/aEcc9kDIRejNNG+CQtK0nds65OFUdB2k=; b=GT3MqCeICZy9CIyFOHqZX6Yg1scVFmfTnRXXaIbRCeHkJi27McjD5e/cKji1EmM1KG LgWFDNXuxeo0Jwy/n2dN9jf0QvEjkOjdMv9zxxr0aQzAJCISnc19CL1lbe/noiLO+hMm nU1cRCbxcD5mB2F8u6iC2iItkHLL101ca+G1Q= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to; bh=T87EAHnU6d/aEcc9kDIRejNNG+CQtK0nds65OFUdB2k=; b=RONAHjFufhvh9hXl+G66nOn13I07GcIaqnN4SJ2kKqwruh/RrIqqOIpVAH7PeyImlp xa+tLLghGY2xruuKnS19x7c7mIojni8ABGetkOqL4mbgAKvjVoFPT+IVGTwSN5FPv+4A HWfKXgz3EkX+V3Hr4Swqdi+Cm8x1XyndmXPmGE/6inJGumekAoOxQhWSKkdXdwFYsLm0 ov+BQQFQBCEAHM9XKU4AcxSGkewuWM5sHYTr16j/G1k2egmCnLsN/7dDHV49STyJ/E7w nqngzQg+HeBnsUyWwxl7e9uapXu/WQHnJTQlnRfpgp+Ah+KQVObuhsqQDqU3S21lMsxm lroA== X-Gm-Message-State: AGi0PuYnsUDNd2e40fv2w+tFLUi0RmWlwmIS5CSXaK5MzaZWnIhdA/oM UW1uq/pDM3Hgox1t4NoKwV3s2g== X-Received: by 2002:a5d:494a:: with SMTP id r10mr2300695wrs.136.1588668709915; Tue, 05 May 2020 01:51:49 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:57f4:0:efd0:b9e5:5ae6:c2fa]) by smtp.gmail.com with ESMTPSA id q184sm2623921wma.25.2020.05.05.01.51.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 May 2020 01:51:48 -0700 (PDT) Date: Tue, 5 May 2020 10:51:47 +0200 From: Daniel Vetter To: =?utf-8?B?TWljaGHFgiBPcnplxYI=?= Cc: Sean Paul , Jani Nikula , Daniel Vetter , Maxime Ripard , Thomas Zimmermann , Dave Airlie , Intel Graphics Development , Linux Kernel Mailing List , dri-devel Subject: Re: [PATCH] drm: Replace drm_modeset_lock/unlock_all with DRM_MODESET_LOCK_ALL_* helpers Message-ID: <20200505085147.GO10381@phenom.ffwll.local> Mail-Followup-To: =?utf-8?B?TWljaGHFgiBPcnplxYI=?= , Sean Paul , Jani Nikula , Maxime Ripard , Thomas Zimmermann , Dave Airlie , Intel Graphics Development , Linux Kernel Mailing List , dri-devel References: <1588093804-30446-1-git-send-email-michalorzel.eng@gmail.com> <875zdiacv2.fsf@intel.com> <520d517e-5e8f-a6c7-1c8a-38d1a368a79f@gmail.com> <20200504115309.GJ10381@phenom.ffwll.local> <9cd2487b-c6a8-b057-e53c-b3dd1e7141aa@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9cd2487b-c6a8-b057-e53c-b3dd1e7141aa@gmail.com> X-Operating-System: Linux phenom 5.4.0-4-amd64 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 05, 2020 at 07:55:00AM +0200, Michał Orzeł wrote: > > > On 04.05.2020 13:53, Daniel Vetter wrote: > > On Fri, May 01, 2020 at 05:49:33PM +0200, Michał Orzeł wrote: > >> > >> > >> On 30.04.2020 20:30, Daniel Vetter wrote: > >>> On Thu, Apr 30, 2020 at 5:38 PM Sean Paul wrote: > >>>> > >>>> On Wed, Apr 29, 2020 at 4:57 AM Jani Nikula wrote: > >>>>> > >>>>> On Tue, 28 Apr 2020, Michal Orzel wrote: > >>>>>> As suggested by the TODO list for the kernel DRM subsystem, replace > >>>>>> the deprecated functions that take/drop modeset locks with new helpers. > >>>>>> > >>>>>> Signed-off-by: Michal Orzel > >>>>>> --- > >>>>>> drivers/gpu/drm/drm_mode_object.c | 10 ++++++---- > >>>>>> 1 file changed, 6 insertions(+), 4 deletions(-) > >>>>>> > >>>>>> diff --git a/drivers/gpu/drm/drm_mode_object.c b/drivers/gpu/drm/drm_mode_object.c > >>>>>> index 35c2719..901b078 100644 > >>>>>> --- a/drivers/gpu/drm/drm_mode_object.c > >>>>>> +++ b/drivers/gpu/drm/drm_mode_object.c > >>>>>> @@ -402,12 +402,13 @@ int drm_mode_obj_get_properties_ioctl(struct drm_device *dev, void *data, > >>>>>> { > >>>>>> struct drm_mode_obj_get_properties *arg = data; > >>>>>> struct drm_mode_object *obj; > >>>>>> + struct drm_modeset_acquire_ctx ctx; > >>>>>> int ret = 0; > >>>>>> > >>>>>> if (!drm_core_check_feature(dev, DRIVER_MODESET)) > >>>>>> return -EOPNOTSUPP; > >>>>>> > >>>>>> - drm_modeset_lock_all(dev); > >>>>>> + DRM_MODESET_LOCK_ALL_BEGIN(dev, ctx, 0, ret); > >>>>> > >>>>> I cry a little every time I look at the DRM_MODESET_LOCK_ALL_BEGIN and > >>>>> DRM_MODESET_LOCK_ALL_END macros. :( > >>>>> > >>>>> Currently only six users... but there are ~60 calls to > >>>>> drm_modeset_lock_all{,_ctx} that I presume are to be replaced. I wonder > >>>>> if this will come back and haunt us. > >>>>> > >>>> > >>>> What's the alternative? Seems like the options without the macros is > >>>> to use incorrect scope or have a bunch of retry/backoff cargo-cult > >>>> everywhere (and hope the copy source is done correctly). > >>> > >>> Yeah Sean & me had a bunch of bikesheds and this is the least worst > >>> option we could come up with. You can't make it a function because of > >>> the control flow. You don't want to open code this because it's tricky > >>> to get right, if all you want is to just grab all locks. But it is > >>> magic hidden behind a macro, which occasionally ends up hurting. > >>> -Daniel > >> So what are we doing with this problem? Should we replace at once approx. 60 calls? > > > > I'm confused by your question - dradual conversion is entirely orthogonal > > to what exactly we're converting too. All I added here is that we've > > discussed this at length, and the macro is the best thing we've come up > > with. I still think it's the best compromise. > > > > Flag-day conversion for over 60 calls doesn't work, no matter what. > > -Daniel > > > I agree with that. All I wanted to ask was whether I should add something additional to this patch or not. Patch looks good and passed CI, so I went ahead and applied it. Thanks, Daniel > > Thanks, > Michal > >> > >> Michal > >>> > >>>> Sean > >>>> > >>>>> BR, > >>>>> Jani. > >>>>> > >>>>> > >>>>>> > >>>>>> obj = drm_mode_object_find(dev, file_priv, arg->obj_id, arg->obj_type); > >>>>>> if (!obj) { > >>>>>> @@ -427,7 +428,7 @@ int drm_mode_obj_get_properties_ioctl(struct drm_device *dev, void *data, > >>>>>> out_unref: > >>>>>> drm_mode_object_put(obj); > >>>>>> out: > >>>>>> - drm_modeset_unlock_all(dev); > >>>>>> + DRM_MODESET_LOCK_ALL_END(ctx, ret); > >>>>>> return ret; > >>>>>> } > >>>>>> > >>>>>> @@ -449,12 +450,13 @@ static int set_property_legacy(struct drm_mode_object *obj, > >>>>>> { > >>>>>> struct drm_device *dev = prop->dev; > >>>>>> struct drm_mode_object *ref; > >>>>>> + struct drm_modeset_acquire_ctx ctx; > >>>>>> int ret = -EINVAL; > >>>>>> > >>>>>> if (!drm_property_change_valid_get(prop, prop_value, &ref)) > >>>>>> return -EINVAL; > >>>>>> > >>>>>> - drm_modeset_lock_all(dev); > >>>>>> + DRM_MODESET_LOCK_ALL_BEGIN(dev, ctx, 0, ret); > >>>>>> switch (obj->type) { > >>>>>> case DRM_MODE_OBJECT_CONNECTOR: > >>>>>> ret = drm_connector_set_obj_prop(obj, prop, prop_value); > >>>>>> @@ -468,7 +470,7 @@ static int set_property_legacy(struct drm_mode_object *obj, > >>>>>> break; > >>>>>> } > >>>>>> drm_property_change_valid_put(prop, ref); > >>>>>> - drm_modeset_unlock_all(dev); > >>>>>> + DRM_MODESET_LOCK_ALL_END(ctx, ret); > >>>>>> > >>>>>> return ret; > >>>>>> } > >>>>> > >>>>> -- > >>>>> Jani Nikula, Intel Open Source Graphics Center > >>> > >>> > >>> > > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch