Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1601587pxb; Thu, 4 Mar 2021 16:02:20 -0800 (PST) X-Google-Smtp-Source: ABdhPJyuP6pj6e4kFT24F7XwJcKXf7/AMWaFEkKiMFVcDLSfDr/rNGpDvug+qnmw4jUeUZEMYlng X-Received: by 2002:a92:ce4e:: with SMTP id a14mr6371884ilr.219.1614902539882; Thu, 04 Mar 2021 16:02:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614902539; cv=none; d=google.com; s=arc-20160816; b=VNhjt4XcAev9PKSuKBCQdgOofzbsz8GoZ/kni139gLhigVz66p8x1+IBh17JjdUZhZ 6oIyQxoJ0xB0tTaE8hksDL490+6RN+SBRSiNNRBSZE/yVFS3VCF9kt+SVpqJc9+eJYVa i5C9c2MQ6qyzJxi/ZWGMHM/nMiRLtWr9GW2vzWnzzPrG0txoNOo6VDCHtBAno6auqnMP gdxtnLh5WZSV7KZ7W1burzhskK1xaeYFk1XJwgWLRjoQYkVG32WBI78FHabbDlv/xy07 hQj10KbKYcm28kv2m9U+DcDhBqqDhjcs/XqCnsaWUvBvFg7mMwIZECXehvszFlboXAon ffLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:dkim-signature:content-transfer-encoding :mime-version:references:in-reply-to:message-id:date:subject:cc:to :from; bh=9xq8FfvlXkYAk6gs2678CTOmYbDE3Qd9No1oNQX9mU8=; b=Ii/mrxwfkfgL080Cy6yWg5i1tvSwCewHQF96RqxgltEkPEGC5Y9SgKcQCrGPidOj+E Ru+GtVfro1sv8H7b4TrZa/neoJvvchIlNIfpdpfc8Au7Ii3o+FXlthR79HyPHZHbxd8F j5Jf1gH59ygXkSTfXHKUmXWBUH6ZJRzpEkUz9tuNemUzF3/QMEcOpNPGNH0iYcU2VYQz 1klL0ZyDTCCPJHkXeZ2LjIrBacXOMB0zaGt6yOTupQSW7oBL/64NOFGkfrM6JwvvArVY NVAbcAzprd7iG2orcC+Yv3kQXjsPnlFfZ02kndyaD/G0z0wkP8e/1fynG2Bkvfh3dTrC OeQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=pdZOZqSt; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z23si786816iod.32.2021.03.04.16.02.05; Thu, 04 Mar 2021 16:02:19 -0800 (PST) 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=@nvidia.com header.s=n1 header.b=pdZOZqSt; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234120AbhCDFV7 (ORCPT + 99 others); Thu, 4 Mar 2021 00:21:59 -0500 Received: from hqnvemgate26.nvidia.com ([216.228.121.65]:13814 "EHLO hqnvemgate26.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234013AbhCDFVi (ORCPT ); Thu, 4 Mar 2021 00:21:38 -0500 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate26.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Wed, 03 Mar 2021 21:20:58 -0800 Received: from DRHQMAIL107.nvidia.com (10.27.9.16) by HQMAIL109.nvidia.com (172.20.187.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 4 Mar 2021 05:20:56 +0000 Received: from nvdebian.localnet (172.20.145.6) by DRHQMAIL107.nvidia.com (10.27.9.16) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 4 Mar 2021 05:20:54 +0000 From: Alistair Popple To: Jason Gunthorpe CC: , , , , , , , , , , , Subject: Re: [PATCH v3 5/8] mm: Device exclusive memory access Date: Thu, 4 Mar 2021 16:20:52 +1100 Message-ID: <2083651.v4LkQjjfQp@nvdebian> In-Reply-To: <20210302124152.GF4247@nvidia.com> References: <20210226071832.31547-1-apopple@nvidia.com> <2758096.Z30Q8iEM0t@nvdebian> <20210302124152.GF4247@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To DRHQMAIL107.nvidia.com (10.27.9.16) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1614835258; bh=9xq8FfvlXkYAk6gs2678CTOmYbDE3Qd9No1oNQX9mU8=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type: X-Originating-IP:X-ClientProxiedBy; b=pdZOZqStw2k9kfUFThuG08SuNOI+mxN+x8dJw3XY+pM3XOS0KNusvlx7Jc8OmFDTP 1yLQwxTNBqHauziGi82t9z4NolEGpl064lNuH+GMljlF7shSZzhkX0cOxfFgsigt6T xTZCkHQHNCzFRImpRR2ildShmJcGlzmD9S2WSCmPGvQz1AuZIgLx2/B/LWMWl3Uygq 22c/GzkFoGtVRvbdCQ/ffN0LnSmAmIJ4CxK9n7vAY+aaqagzn/7jl6GH6UwXw4Y54x fg7uzjwBKZt6NGVv2TKGuIXUv2P0JIZsIRJkaFC//mQiZr15JDiQyleyVMMn4J8u0M pFKBKhvcVbdbQ== Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, 2 March 2021 11:41:52 PM AEDT Jason Gunthorpe wrote: > > However try_to_protect() scans the PTEs again under the PTL so checking the > > mapping of interest actually gets replaced during the rmap walk seems like a > > reasonable solution. Thanks for the comments. > > It does seem cleaner if you can manage it, the notifier will still be > needd to program the HW though Checking during the rmap walk wasn't hard but ultimately pointless. As you say a range notifier and lock is required to program the hardware, which requires checking the mappings with a mmu notifier sequence anyway. - Alistair