Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp4547879ioo; Tue, 31 May 2022 06:52:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzSMVWa1t7UJh4Ct3gYEntTd/i0UdHL9KrrlN/AUGAs/820OEQe1edGqth66tMdYBZqz6pl X-Received: by 2002:a17:907:7284:b0:6ff:16b8:3073 with SMTP id dt4-20020a170907728400b006ff16b83073mr26431304ejc.196.1654005178269; Tue, 31 May 2022 06:52:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654005178; cv=none; d=google.com; s=arc-20160816; b=Vgdu/P71AdvDAlpFfMWyc7/UugHml2uvv9Qqez7YTYU/Oxmh9bUtsM4TAx8AR7u0NR J/Oz1nmtpzPMVAy2zZQSS9bJJ7rwyfLIy9leRbKbn8/d3QTHkVOe1pJRM2KxAurk0KAm WbQu6jevwVM4UrXe+C5Xx9e2wygp9pJvi2Y+pDQdAa09fVY83LssOPM7xXI/9hUwXkWb K0oc7EA52/WpOHE1Qd+RrZsSz1WEE9Fw5pOppa5AB513KZm4sZx60oeMp+V1o+Yv8XQb LiWKod2H7sVAK5ZN1chGtcTPld32c/zrYVBMhe/Pfqrm0d0EFG1Tyaqgn76j55ZE7ijt 6gsA== 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:dkim-signature; bh=xcpbx9Lt9Owdlm64rePa6qexHLWiyypbRMgxN1JLv/M=; b=pnrcALez9zXw3lW1kqHM71muPr7/pu9I+nLPNYS0sRe0D3a3kZXSswuA18Deea67Cr G/B5jYJ57JrJF/cBWjqbTVl3/KDTtHqZpQKbiEBNy5KAzw5/E3ZuV3m8wXVUvcfOQ9RE f2gz3FRsr2ErRmfcLGk3Yo0L4FxdyHytdeBMQZC10fSp9DpZliqkEK++93zBrG3DBW68 LFE3ck53SIIrxDFbFC2SPh6OMtT8CmlrKg7oYe4X3LSwFDMP1fJXp2wFbUqIBNQKvY5S 8T/YXMSiuDjhDSClhD96O3F3sbSmqw6xPY8UQi+4/ka1rqb2BBzyxlYjIWdV2BxiTu1I eSug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=CyYXFkxh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hq21-20020a1709073f1500b006f44899d7cesi14400266ejc.622.2022.05.31.06.52.30; Tue, 31 May 2022 06:52:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=CyYXFkxh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232597AbiEaCvx (ORCPT + 99 others); Mon, 30 May 2022 22:51:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45882 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232746AbiEaCvu (ORCPT ); Mon, 30 May 2022 22:51:50 -0400 Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D2E0512AC8 for ; Mon, 30 May 2022 19:51:48 -0700 (PDT) Received: by mail-pj1-x1030.google.com with SMTP id hv24-20020a17090ae41800b001e33eebdb5dso175429pjb.0 for ; Mon, 30 May 2022 19:51:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=xcpbx9Lt9Owdlm64rePa6qexHLWiyypbRMgxN1JLv/M=; b=CyYXFkxhZiXQiu14RxVExNHuXRW0mFlO3k3+vtcoaKX56jC5Ba1StMa8qKRpw1gBRQ m2pdXOpOXP5yoNapy24x4BR7MDFAg/xRghRxTbuu49cw3iyj+gWoa8iNtf8UAns32Wob fQmMqbHWuHhV5B4vVeGxYjmDjsojaHhPcIBeQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=xcpbx9Lt9Owdlm64rePa6qexHLWiyypbRMgxN1JLv/M=; b=qPzCoqNvIJLHJXD1BMBPXrQYUN5/HLRpJBFYNtSJNhnk3wAjyHRCtNAYDonKQqBcJh LXJxrEUUEMcyo3XCqxJlzJbYwPJcXBMrCRRtgGjVzpdIKEWmQsJdey8tg5k4VzIBozT4 Rv6DWxW7OpKg/ya76pFRxI9DDhSOfMtBEtztxYBM/Y7a9ZPobGQH/R79pklqFTdna5X/ Z/6GLbOKpleCyff92KDl0mHdXHfXcwF8xtTpQyR+Du5Wr/lEaeQKK6jzK2Aeaihc5i6z cBUB5/loMkcenxUgMpTBf/KfA+5zPJYvd3LKR83EaR8qWtGO0THNzsFBW8tIT6Ox5BAV nE7A== X-Gm-Message-State: AOAM530C3HuC7tgMzGCJGwXf03iWERxHitKab2fUfMAo+y04CZS1G30b JKJxLihd/LFHGOkCqVxgQHHJEw== X-Received: by 2002:a17:90a:de01:b0:1df:cda5:8332 with SMTP id m1-20020a17090ade0100b001dfcda58332mr26157122pjv.123.1653965508382; Mon, 30 May 2022 19:51:48 -0700 (PDT) Received: from google.com ([240f:75:7537:3187:7d2a:ad1f:afa1:7770]) by smtp.gmail.com with ESMTPSA id i16-20020a056a00005000b00518382bceaesm9479310pfk.57.2022.05.30.19.51.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 May 2022 19:51:47 -0700 (PDT) Date: Tue, 31 May 2022 11:51:42 +0900 From: Sergey Senozhatsky To: Christian =?iso-8859-1?Q?K=F6nig?= Cc: Sergey Senozhatsky , Sumit Semwal , Gustavo Padovan , Tomasz Figa , Ricardo Ribalda , Christoph Hellwig , linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] dma-fence: allow dma fence to have their own lock Message-ID: References: <20220530142232.2871634-1-senozhatsky@chromium.org> <7eee4274-bd69-df8d-9067-771366217804@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7eee4274-bd69-df8d-9067-771366217804@amd.com> X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (22/05/30 16:55), Christian K?nig wrote: > Am 30.05.22 um 16:22 schrieb Sergey Senozhatsky: > > [SNIP] > > So the `lock` should have at least same lifespan as the DMA fence > > that borrows it, which is impossible to guarantee in our case. > > Nope, that's not correct. The lock should have at least same lifespan as the > context of the DMA fence. How does one know when it's safe to release the context? DMA fence objects are still transparently refcount-ed and "live their own lives", how does one synchronize lifespans?