From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755237AbcGEOC2 (ORCPT <rfc822;w@1wt.eu>);
	Tue, 5 Jul 2016 10:02:28 -0400
Received: from hqemgate14.nvidia.com ([216.228.121.143]:8257 "EHLO
	hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755204AbcGEOCY (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 5 Jul 2016 10:02:24 -0400
X-PGP-Universal: processed;
	by hqnvupgp08.nvidia.com on Tue, 05 Jul 2016 07:00:50 -0700
Date: Tue, 5 Jul 2016 07:02:22 -0700
From: Neo Jia <cjia@nvidia.com>
To: Paolo Bonzini <pbonzini@redhat.com>
CC: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
        Kirti Wankhede <kwankhede@nvidia.com>,
        Xiao Guangrong <guangrong.xiao@linux.intel.com>,
        Andrea Arcangeli <aarcange@redhat.com>,
        Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
Subject: Re: [PATCH 0/2] KVM: MMU: support VMAs that got remap_pfn_range-ed
Message-ID: <20160705140222.GA31814@nvidia.com>
References: <1467291711-3230-1-git-send-email-pbonzini@redhat.com>
 <20160705054147.GA27138@nvidia.com>
 <fc22ad5a-5f47-458c-63db-b80e8ce96d99@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <fc22ad5a-5f47-458c-63db-b80e8ce96d99@redhat.com>
X-NVConfidentiality: public
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Originating-IP: [172.20.13.39]
X-ClientProxiedBy: HQMAIL101.nvidia.com (172.20.187.10) To
 HQMAIL108.nvidia.com (172.18.146.13)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@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
>