From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bharata B Rao Subject: Re: ensure device private pages have an owner v2 Date: Tue, 17 Mar 2020 11:01:21 +0530 Message-ID: <20200317053121.GA22538@in.ibm.com> References: <20200316193216.920734-1-hch@lst.de> Reply-To: bharata@linux.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20200316193216.920734-1-hch@lst.de> Sender: kvm-ppc-owner@vger.kernel.org To: Christoph Hellwig Cc: Jason Gunthorpe , Dan Williams , Christian =?iso-8859-1?Q?K=F6nig?= , Ben Skeggs , Jerome Glisse , kvm-ppc@vger.kernel.org, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org, linux-mm@kvack.org List-Id: nouveau.vger.kernel.org On Mon, Mar 16, 2020 at 08:32:12PM +0100, Christoph Hellwig wrote: > When acting on device private mappings a driver needs to know if the > device (or other entity in case of kvmppc) actually owns this private > mapping. This series adds an owner field and converts the migrate_vma > code over to check it. I looked into doing the same for > hmm_range_fault, but as far as I can tell that code has never been > wired up to actually work for device private memory, so instead of > trying to fix some unused code the second patch just remove the code. > We can add it back once we have a working and fully tested code, and > then should pass the expected owner in the hmm_range structure. Boot-tested a pseries secure guest with this change (1/4 and 2/4 only) So Tested-by: Bharata B Rao for the above two patches. Regards, Bharata.