From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: Dom0 linux 4.0 + devel/for-linus-4.1 branch: p2m.c:884:d0v0 gfn_to_mfn failed! gfn=ffffffff001ed type:4 Date: Mon, 13 Apr 2015 10:50:51 +0100 Message-ID: <552B917B.9040603@citrix.com> References: <1436836007.20150413113902@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yhb16-0001ea-4O for xen-devel@lists.xenproject.org; Mon, 13 Apr 2015 09:50:56 +0000 In-Reply-To: <1436836007.20150413113902@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sander Eikelenboom Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 13/04/15 10:39, Sander Eikelenboom wrote: > Hi David, > > I seem to have spotted some trouble with a 4.0 dom0 kernel with the > devel/for-linus-4.1 branch pulled on top. > > Does this remind you of any specific commits in the devel/for-linus-4.1 branch that could > likely be involved that i could try to revert ? Yes. This will probably be 4e8c0c8c4bf3a (xen/privcmd: improve performance of MMAPBATCH_V2) which makes the kernel try harder to map all GFNs instead of failing on the first one. I think this is qemu incorrectly trying to map GFNs. David > I now get a very large number of these at guest with passthrough start: > (XEN) [2015-04-12 14:55:20.226] p2m.c:884:d0v0 gfn_to_mfn failed! gfn=ffffffff001ed type:4