Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp1767190pxb; Fri, 1 Oct 2021 19:38:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy7Egp9GI5jokBZIerJczPlWXMWC9ULIpkZihQuh5240DiQ3rRUNssj/eGpWc2KhdGoUuL+ X-Received: by 2002:a17:906:9484:: with SMTP id t4mr1612026ejx.483.1633142317813; Fri, 01 Oct 2021 19:38:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633142317; cv=none; d=google.com; s=arc-20160816; b=BCLljw9BCiOn5eGM+ln5GugffoQXj07Mz2Z9lmCGvjfjG4+LWZH0T0ZRiPqcqrjmyj 6XfAmeJ4lDkAjZilK8PFTJb7BKgET5MeG01PikFYCMhfYGm0ZIeLdrJTk/Cg39RM4gsK 7/lQlesPERQpbM4RXiPtpg2NcxejGRIvz774ANupRlo+BC8r+1H6D9DICcSLR+2KIayI vRqV5H8uudLfpjQM+15yQoF6y3Fe8db3hBLUwxYOrPhSaD1GwPwNGnP+eYyDh/ZtCMmO rutwVw2aSse0ifMH6qZ4s+OR5TMqPUPo0N3KHaocSPPrPTZQpQZ8dwA0DsrmyCJCDYqZ /9sQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=G5n7KcgYVlbaKc3lhQLNKLcwP2hlrLV/7iNHmf9KKjk=; b=UDL3TQob7lzsO5HOkToQ4FL/2Nrr3XA1nXbDGrLaG0AQxNutdpiNS2TGGL01GlpaRJ GTKt16Hcanl1Yi8EXv5W6NFa/MNVyrVEMPriBlV4kcm9l3KPngkrWQbAmSnsBQayyIgq FGNTtpiXoqwzaEdLIB+pWCF5umYIQDh7zNCDJRfAFqmwXCTkWJIXhv7tqnRPmByv1auI EdvjN/ts6NHzGJiH7RorK8hoSq9oyPukHmPUjSFhgYv0QhuedNRSrMn/5KTzpa56bw/e lJTxAQ1G72pb+IRf2TVX9bXcR0EfpAtGuBuztvTFbeY7EKjOE50Ld8d91hZn2IoHpuus SiNA== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dn25si6416080edb.509.2021.10.01.19.38.10; Fri, 01 Oct 2021 19:38:37 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232479AbhJBCcj (ORCPT + 99 others); Fri, 1 Oct 2021 22:32:39 -0400 Received: from mga17.intel.com ([192.55.52.151]:57897 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230386AbhJBCcj (ORCPT ); Fri, 1 Oct 2021 22:32:39 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10124"; a="205792401" X-IronPort-AV: E=Sophos;i="5.85,340,1624345200"; d="scan'208";a="205792401" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Oct 2021 19:30:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.85,340,1624345200"; d="scan'208";a="521577655" Received: from stinkbox.fi.intel.com (HELO stinkbox) ([10.237.72.171]) by fmsmga008.fm.intel.com with SMTP; 01 Oct 2021 19:30:49 -0700 Received: by stinkbox (sSMTP sendmail emulation); Sat, 02 Oct 2021 05:30:49 +0300 Date: Sat, 2 Oct 2021 05:30:49 +0300 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Sean Paul Cc: Fernando Ramos , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, amd-gfx@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, nouveau@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, linux-tegra@vger.kernel.org Subject: Re: [Intel-gfx] [PATCH v2 00/17] drm: cleanup: Use DRM_MODESET_LOCK_ALL_* helpers where possible Message-ID: References: <20210924064324.229457-1-greenfoo@u92.eu> <20211001183655.GW2515@art_vandelay> <20211001204815.GA2515@art_vandelay> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Patchwork-Hint: comment Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 02, 2021 at 01:05:47AM +0300, Ville Syrj?l? wrote: > On Fri, Oct 01, 2021 at 04:48:15PM -0400, Sean Paul wrote: > > On Fri, Oct 01, 2021 at 10:00:50PM +0300, Ville Syrj?l? wrote: > > > On Fri, Oct 01, 2021 at 02:36:55PM -0400, Sean Paul wrote: > > > > On Fri, Sep 24, 2021 at 08:43:07AM +0200, Fernando Ramos wrote: > > > > > Hi all, > > > > > > > > > > One of the things in the DRM TODO list ("Documentation/gpu/todo.rst") was to > > > > > "use DRM_MODESET_LOCAL_ALL_* helpers instead of boilerplate". That's what this > > > > > patch series is about. > > > > > > > > > > You will find two types of changes here: > > > > > > > > > > - Replacing "drm_modeset_lock_all_ctx()" (and surrounding boilerplate) with > > > > > "DRM_MODESET_LOCK_ALL_BEGIN()/END()" in the remaining places (as it has > > > > > already been done in previous commits such as b7ea04d2) > > > > > > > > > > - Replacing "drm_modeset_lock_all()" with "DRM_MODESET_LOCK_ALL_BEGIN()/END()" > > > > > in the remaining places (as it has already been done in previous commits > > > > > such as 57037094) > > > > > > > > > > Most of the changes are straight forward, except for a few cases in the "amd" > > > > > and "i915" drivers where some extra dancing was needed to overcome the > > > > > limitation that the DRM_MODESET_LOCK_ALL_BEGIN()/END() macros can only be used > > > > > once inside the same function (the reason being that the macro expansion > > > > > includes *labels*, and you can not have two labels named the same inside one > > > > > function) > > > > > > > > > > Notice that, even after this patch series, some places remain where > > > > > "drm_modeset_lock_all()" and "drm_modeset_lock_all_ctx()" are still present, > > > > > all inside drm core (which makes sense), except for two (in "amd" and "i915") > > > > > which cannot be replaced due to the way they are being used. > > > > > > > > > > Changes in v2: > > > > > > > > > > - Fix commit message typo > > > > > - Use the value returned by DRM_MODESET_LOCK_ALL_END when possible > > > > > - Split drm/i915 patch into two simpler ones > > > > > - Remove drm_modeset_(un)lock_all() > > > > > - Fix build problems in non-x86 platforms > > > > > > > > > > Fernando Ramos (17): > > > > > drm: cleanup: drm_modeset_lock_all_ctx() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/i915: cleanup: drm_modeset_lock_all_ctx() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/msm: cleanup: drm_modeset_lock_all_ctx() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() drm/vmwgfx: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/tegra: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/shmobile: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/radeon: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/omapdrm: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/nouveau: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/msm: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/i915: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/i915: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() part 2 > > > > > drm/gma500: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm/amd: cleanup: drm_modeset_lock_all() --> DRM_MODESET_LOCK_ALL_BEGIN() > > > > > drm: cleanup: remove drm_modeset_(un)lock_all() > > > > > doc: drm: remove TODO entry regarding DRM_MODSET_LOCK_ALL cleanup > > > > > > > > > > > > > Thank you for revising, Fernando! I've pushed the set to drm-misc-next (along > > > > with the necessary drm-tip conflict resolutions). > > > > > > Ugh. Did anyone actually review the locking changes this does? > > > I shot the previous i915 stuff down because the commit messages > > > did not address any of it. > > > > I reviewed the set on 9/17, I didn't see your feedback on that thread. > > It was much earlir than that. > https://lists.freedesktop.org/archives/dri-devel/2021-June/313193.html > > And I think I might have also shot down a similar thing earlier. > > I was actually half considering sending a patch to nuke that > misleading TODO item. I don't think anything which changes > which locks are taken should be considred a starter level task. > And the commit messages here don't seem to address any of it. And i915 is now broken :( https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/fi-bwr-2160/boot.html -- Ville Syrj?l? Intel