From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752150AbcF3NCM (ORCPT ); Thu, 30 Jun 2016 09:02:12 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:35515 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751704AbcF3NCK (ORCPT ); Thu, 30 Jun 2016 09:02:10 -0400 From: Paolo Bonzini To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: Kirti Wankhede , Neo Jia , Xiao Guangrong , Andrea Arcangeli , =?UTF-8?q?Radim=20Kr=C4=8Dm=C3=A1=C5=99?= Subject: [PATCH 0/2] KVM: MMU: support VMAs that got remap_pfn_range-ed Date: Thu, 30 Jun 2016 15:01:49 +0200 Message-Id: <1467291711-3230-1-git-send-email-pbonzini@redhat.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks, Paolo Paolo Bonzini (2): KVM: MMU: prepare to support mapping of VM_IO and VM_PFNMAP frames KVM: MMU: try to fix up page faults before giving up mm/gup.c | 1 + virt/kvm/kvm_main.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++----- 2 files changed, 51 insertions(+), 5 deletions(-) -- 1.8.3.1