From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Vrabel <david.vrabel@citrix.com>
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 13:21:21 +0100
Message-ID: <552BB4C1.4020105@citrix.com>
References: <1436836007.20150413113902@eikelenboom.it>
	<552B917B.9040603@citrix.com>	<815939792.20150413132150@eikelenboom.it>
	<552BB166.1060505@citrix.com>
	<1863723878.20150413141421@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <david.vrabel@citrix.com>) id 1YhdMp-0004y1-AG
	for xen-devel@lists.xenproject.org; Mon, 13 Apr 2015 12:21:31 +0000
In-Reply-To: <1863723878.20150413141421@eikelenboom.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sander Eikelenboom <linux@eikelenboom.it>, David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
List-Id: xen-devel@lists.xenproject.org

On 13/04/15 13:14, Sander Eikelenboom wrote:
> 
> Monday, April 13, 2015, 2:07:02 PM, you wrote:
> 
>> On 13/04/15 12:21, Sander Eikelenboom wrote:
>>>
>>> Monday, April 13, 2015, 11:50:51 AM, you wrote:
>>>
>>>> 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
>>>
>>> Reverted that specific one, but still get those messages.
> 
>> You'll have to bisect it then.  Because I don't see any other relevant
>> commits in devel/for-linus-4.1
> 
>> David
> 
> Ok .. hmm first candidate of the bisect also looks interessting:
> [628c28eefd6f2cef03b212081b466ae43fd093a3] xen: unify foreign GFN map/unmap for auto-xlated physmap guests

Unless your dom0 is PVH, no.

David