From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neo Jia Subject: Re: [PATCH 0/2] KVM: MMU: support VMAs that got remap_pfn_range-ed Date: Tue, 5 Jul 2016 07:02:22 -0700 Message-ID: <20160705140222.GA31814@nvidia.com> References: <1467291711-3230-1-git-send-email-pbonzini@redhat.com> <20160705054147.GA27138@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: , , Kirti Wankhede , Xiao Guangrong , Andrea Arcangeli , Radim =?utf-8?B?S3LEjW3DocWZ?= To: Paolo Bonzini Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Tue, Jul 05, 2016 at 02:18:28PM +0200, Paolo Bonzini wrote: > > > On 05/07/2016 07:41, Neo Jia wrote: > > On Thu, Jun 30, 2016 at 03:01:49PM +0200, Paolo Bonzini wrote: > >> The vGPU folks would like to trap the first access to a BAR by setting > >> vm_ops on the VMAs produced by mmap-ing a VFIO device. The fault handler > >> then can use remap_pfn_range to place some non-reserved pages in the VMA. > >> > >> KVM lacks support for this kind of non-linear VM_PFNMAP mapping, and these > >> patches should fix this. > > > > Hi Paolo, > > > > I have tested your patches with the mediated passthru patchset that is being > > reviewed in KVM and QEMU mailing list. > > > > The fault handler gets called successfully and the previously mapped memory gets > > unmmaped correctly via unmap_mapping_range. > > Great, then I'll include them in 4.8. Thanks! > > Paolo >