Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2509654ybt; Tue, 16 Jun 2020 07:55:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxUArFVd5QvOLK+jlzTreuJboIFeCciydIh8Mva0bOWpAjDnNeb89/pl7s+r8mWJNvydE5K X-Received: by 2002:a17:906:8244:: with SMTP id f4mr3213726ejx.257.1592319335402; Tue, 16 Jun 2020 07:55:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592319335; cv=none; d=google.com; s=arc-20160816; b=NETNQd4o9HbRd0/OlRh0Z4STwy1LGaXM19flgfHJzrFW5ohngPybX0JOXP60Iag8LS 631ZTaw6Mi1Ri2Y3wBwwlDLw/8XAOIe80Gkb17n81R34xEXKOIbuXk18qVBW6em7T0lM +65UginYRvn/m+0wLg2tzYwu06UX6YshKJJCpEqnwCQJNZ+DNuVrRDdUiYHMeS/pQ0yH BJnM2C0aBInlzil4f0wKpLUHZbJfSzYW9lQ6+7Fsh86qlExhtzu81GyQu6gRjVlCjedh 4fNY0Y2eyFM++O6+Fpw1DGftFKWtv+a/cFp+635pe9sY9fIGpQKmoup792u/6uy9IGeG YYLw== 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-disposition :mime-version:references:message-id:subject:to:from:date :dkim-signature; bh=H9Q21GJcnralnv81ky+DYZCuyhzGkXe+xlvLrhcRUVI=; b=Obk5yqWYcZuUNkTXDrp9otAJ2t8zaiw9ZwdpFlOmB1ND8PgrtJTL3SfRXpqRcGBu4J qhlMaNdWz4ICBpYkxu0vuiaNmuVfL7PqnFQxW8r1R6XUnIlDMLekrvXKQblnvOzmEizo S/UbiJjMJunZg1x74S/R5eXkqF+r52UMlqoOp15nictVE7KjBEyuq0DtFaxchPZyT6G+ Sq6lDQ1UbBsI4HIt/i53Q2orj9OpPX1ziKFFhr7D4u26f/ntACj9vjRHtmmRO976/2Yj Ako7u36QS2nfLTGSBoecdp+lcOLZruo5BBNAs+iPKLh11YahcI2EAiExykxyGMiiHjJC PAsw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=cDN3DzBN; 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 u9si10425883edl.529.2020.06.16.07.55.12; Tue, 16 Jun 2020 07:55:35 -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=@ziepe.ca header.s=google header.b=cDN3DzBN; 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 S1729227AbgFPOxQ (ORCPT + 99 others); Tue, 16 Jun 2020 10:53:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38074 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729005AbgFPOxO (ORCPT ); Tue, 16 Jun 2020 10:53:14 -0400 Received: from mail-qv1-xf41.google.com (mail-qv1-xf41.google.com [IPv6:2607:f8b0:4864:20::f41]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A88B7C061755 for ; Tue, 16 Jun 2020 07:53:14 -0700 (PDT) Received: by mail-qv1-xf41.google.com with SMTP id cv17so9576641qvb.13 for ; Tue, 16 Jun 2020 07:53:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=H9Q21GJcnralnv81ky+DYZCuyhzGkXe+xlvLrhcRUVI=; b=cDN3DzBNq5d3CrdALYsiOTFh73YRcI8lQ7uTSznJPv8dAJPnHjJPQR57lcTVwcL/Fu tV3NTbV5GNoBVgT5Y9FK7M+PwBjksAzlKvZZnxf+Qkd/PqTbrIdNSIbQI4xY6GgG5IkN 2i29pdJFycDxjY2QVTv0QiEB95VIbTnGIGt0UTkJ1Csd3R+WgZXFN5sle6nrM8u0InPD 03ylAeGN5+aJZmvaChOTyf6V/AGcN+wyw9nUErW3py9ORSzNIR2Kd+m+VbjIZ7U5Y8CF +bk0T6Aw1wPbeMExKzclzBgPz36VephSSjSjX1HFVeLmX9lSoGuhN4yVL+U6sHPpHMa8 lzug== 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:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=H9Q21GJcnralnv81ky+DYZCuyhzGkXe+xlvLrhcRUVI=; b=DeQArmK/f7+N2KOizcQz+a12f7Dw2+G8ohdzzh9OWfUkyismNK3ZUqjDIzxwb3N1uB Xin41MKDrq8mkOv67lBLDMS7M2I4yCIct58R0j+0g0gltfCwdYSNK1y2ifsmi/g1yrWM bX3FOmJ4sMr2HaII1yB+oTmlYkxTzvNh2ID++uakZ82LRGR0kviF8aTN/KTk+Nh1ywGw zBrIBGKlHbKfL3FrA7WUNFv6V8xBSVEcOpccNgzCBZWq0SExRCvSnuziXwNh+mXXWZC2 aMv3cQLk+E0mmcQVdynMmSEcwThtGdWByT3qXxDYrzjqa+m3AsVgjF9jcxFzw12HVbZq 9VQA== X-Gm-Message-State: AOAM531XSCs6d+k/E88+s9tex/7fRF8x7ArhBMNvW1+67OGmCBXbUZSR LscdDu1rMsdsyUqY3Beo1sobLw== X-Received: by 2002:a0c:e9cd:: with SMTP id q13mr2731630qvo.23.1592319193724; Tue, 16 Jun 2020 07:53:13 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-156-34-48-30.dhcp-dynamic.fibreop.ns.bellaliant.net. [156.34.48.30]) by smtp.gmail.com with ESMTPSA id g9sm14433034qtq.66.2020.06.16.07.53.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jun 2020 07:53:13 -0700 (PDT) Received: from jgg by mlx with local (Exim 4.93) (envelope-from ) id 1jlCxc-0096j7-MB; Tue, 16 Jun 2020 11:53:12 -0300 Date: Tue, 16 Jun 2020 11:53:12 -0300 From: Jason Gunthorpe To: Thomas =?utf-8?B?SGVsbHN0csO2bSAoSW50ZWwp?= , DRI Development , linux-rdma@vger.kernel.org, Intel Graphics Development , Maarten Lankhorst , LKML , amd-gfx@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, Thomas Hellstrom , Daniel Vetter , linux-media@vger.kernel.org, Christian =?utf-8?B?S8O2bmln?= , Mika Kuoppala Subject: Re: [Linaro-mm-sig] [PATCH 04/18] dma-fence: prime lockdep annotations Message-ID: <20200616145312.GC6578@ziepe.ca> References: <20200604081224.863494-1-daniel.vetter@ffwll.ch> <20200604081224.863494-5-daniel.vetter@ffwll.ch> <20200611083430.GD20149@phenom.ffwll.local> <20200611141515.GW6578@ziepe.ca> <20200616120719.GL20149@phenom.ffwll.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200616120719.GL20149@phenom.ffwll.local> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 16, 2020 at 02:07:19PM +0200, Daniel Vetter wrote: > > > I've pinged a bunch of armsoc gpu driver people and ask them how much this > > > hurts, so that we have a clear answer. On x86 I don't think we have much > > > of a choice on this, with userptr in amd and i915 and hmm work in nouveau > > > (but nouveau I think doesn't use dma_fence in there). > > > > Right, nor will RDMA ODP. > > Hm, what's the context here? I thought RDMA side you really don't want > dma_fence in mmu_notifiers, so not clear to me what you're agreeing on > here. rdma does not use dma_fence at all, and though it is hard to tell, I didn't notice a dma_fence in the nouveau invalidation call path. At the very least I think there should be some big warning that dma_fence in notifiers should be avoided. Ie it is strange that the new totally-not-a-gpu drivers use dma_fence, they surely don't have the same constraints as the existing GPU world, and it would be annoying to see dma_fence notifiers spring up in them Jason