From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f197.google.com (mail-pf1-f197.google.com [209.85.210.197]) by kanga.kvack.org (Postfix) with ESMTP id 6DC318E00E5 for ; Wed, 12 Dec 2018 17:12:05 -0500 (EST) Received: by mail-pf1-f197.google.com with SMTP id s14so16423880pfk.16 for ; Wed, 12 Dec 2018 14:12:05 -0800 (PST) Received: from bombadil.infradead.org (bombadil.infradead.org. [2607:7c80:54:e::133]) by mx.google.com with ESMTPS id p4si15219772pga.514.2018.12.12.14.12.04 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 12 Dec 2018 14:12:04 -0800 (PST) Date: Wed, 12 Dec 2018 14:11:57 -0800 From: Matthew Wilcox Subject: Re: [PATCH 1/2] mm: introduce put_user_page*(), placeholder versions Message-ID: <20181212221157.GL6830@bombadil.infradead.org> References: <7b4733be-13d3-c790-ff1b-ac51b505e9a6@nvidia.com> <20181207191620.GD3293@redhat.com> <3c4d46c0-aced-f96f-1bf3-725d02f11b60@nvidia.com> <20181208022445.GA7024@redhat.com> <20181210102846.GC29289@quack2.suse.cz> <20181212150319.GA3432@redhat.com> <20181212213005.GE5037@redhat.com> <20181212215348.GF5037@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181212215348.GF5037@redhat.com> Sender: owner-linux-mm@kvack.org List-ID: To: Jerome Glisse Cc: Dan Williams , Jan Kara , John Hubbard , John Hubbard , Andrew Morton , Linux MM , tom@talpey.com, Al Viro , benve@cisco.com, Christoph Hellwig , Christopher Lameter , "Dalessandro, Dennis" , Doug Ledford , Jason Gunthorpe , Michal Hocko , Mike Marciniszyn , rcampbell@nvidia.com, Linux Kernel Mailing List , linux-fsdevel , "Weiny, Ira" On Wed, Dec 12, 2018 at 04:53:49PM -0500, Jerome Glisse wrote: > The mmu notifier i put forward is the emergency revoke ie last > resort after driver have done everything it could to inform user- > space and release the pages. So doing thing brutaly in it like > reprogramming driver page table (which AFAIK is something you > can do on any hardware wether the hardware will like it or not > is a different question). You can't do it to an NVMe device. You submit the DMA addresses in the command, and the device reads the command at submission time. There's no way to change the DMA addresses for an in-flight command.