From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 96DA0C433F5 for ; Sat, 2 Oct 2021 22:32:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7D5D761452 for ; Sat, 2 Oct 2021 22:32:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234131AbhJBWe0 (ORCPT ); Sat, 2 Oct 2021 18:34:26 -0400 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:60607 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234111AbhJBWeZ (ORCPT ); Sat, 2 Oct 2021 18:34:25 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id BEC3D580812; Sat, 2 Oct 2021 18:32:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sat, 02 Oct 2021 18:32:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=u92.eu; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=feVIX2W/iu7IBNGFg1YLLfvKn4A Iy1omyC/w57V7Wug=; b=ovzWw3hIbQCcGYWWfpO5bqetBoj8fYi4cU/uzea2qvO Os2rrnreQKdvey22GdkFqYmTqVwHJlz6/KQlAp2Z8mQbRrcVVGS0RhHbrp1axmS1 T4FNGBRIC6VRRFUJMyPMA1yIs4iwF9On1Bqrg0StKz63ldd8P4gi0modAY16sbNX WOnmsvjUWgOf1EVFXdUONhdRS4d570TW/OoyrKXXmebjiEw+1j8fLm+ljv907z9t CIOzD86mMLeHbUi80OMHKQWQ8a2BTeJqaaCtNR9LBUJzmUq7awJMWepSCUordAjM ngdvij4dTKC2HxgnXfPCiotEibBAe0PNcQega9F7pqA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=feVIX2 W/iu7IBNGFg1YLLfvKn4AIy1omyC/w57V7Wug=; b=YMRGtjh8b6/uHXJHbSLqIN XkvnsOT7+fKkqo5MsyQdt9QElTwpFnNH7NZDiZLXzSXOS6FBDZrF/soSknUPTps7 cSX/90+DSQd2xC8HCoXyBNUteJevzWwv9zGF6tVIfUiERM5LrxOfobmziR9FM4T0 mLSPpj+5dA82NtTLbKYT3qLKVZAaZg0+5PRAHUA/IWgXUESWEo1fpoaeLWYr8All JpIncHLyYWJxtXR3Pqqqab9/qf/YQ861tur8Ji253I3WZ1vgqVr7s70Rik3/dyCs ITXmHAKFXd63QFz77+qvRhy+dIxMO6LWM6al1XMqrbbo7nzjVZHNbj/Kf3X0AxUg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudekledgudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttdejnecuhfhrohhmpefhvghrnhgr nhguohcutfgrmhhoshcuoehgrhgvvghnfhhoohesuhelvddrvghuqeenucggtffrrghtth gvrhhnpedvjeeifeelhfetiefhhfdthfefkefhhfeutdetvdfgvefgveefheffgfekjeef heenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrh gvvghnfhhoohesuhelvddrvghu X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 2 Oct 2021 18:32:32 -0400 (EDT) Date: Sun, 3 Oct 2021 00:32:14 +0200 From: Fernando Ramos To: Ville =?utf-8?B?U3lyasOkbMOk?= Cc: Sean Paul , 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=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 21/10/02 09:13AM, Fernando Ramos wrote: > > Sean, could you revert the whole patch series? I'll have a deeper look into the > patch set and come up with a v3 where all these issues will be addressed. > Hi Sean, I now understand the nature of the issue that caused the problem with i915 and have proceed to remove the global context structure (which revealed a similar issue in the amdgpu driver). I have prepared a V3 version of the patch set where these issues should hopefully be fixed for both the i915 and amdgpu drivers. In order to prevent causing more disruption, could you tell me what the proper way to proceed would be? In particular: 1. Is there any place where I can push my changes so that they are tested on a i915 machine? (Some type of automated pool) 2. I can test the amdgpu driver on my machine but, what about all the other architectures? What is the standard procedure? Should I simply publish V3 and wait for feedback from the different vendors? (I would hate to cause a simular situation again) 3. Should I post V3 on top of drm-next or drm-misc-next? Thanks for your patience :)