From: David Vrabel <david.vrabel@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xenproject.org>
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:07:02 +0100 [thread overview]
Message-ID: <552BB166.1060505@citrix.com> (raw)
In-Reply-To: <815939792.20150413132150@eikelenboom.it>
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
next prev parent reply other threads:[~2015-04-13 12:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:39 Dom0 linux 4.0 + devel/for-linus-4.1 branch: p2m.c:884:d0v0 gfn_to_mfn failed! gfn=ffffffff001ed type:4 Sander Eikelenboom
2015-04-13 9:50 ` David Vrabel
2015-04-13 11:21 ` Sander Eikelenboom
2015-04-13 12:07 ` David Vrabel [this message]
2015-04-13 12:14 ` Sander Eikelenboom
2015-04-13 12:21 ` David Vrabel
2015-04-13 12:27 ` Sander Eikelenboom
2015-04-13 15:11 ` Sander Eikelenboom
2015-04-14 9:44 ` David Vrabel
2015-04-14 20:42 ` Konrad Rzeszutek Wilk
2015-04-15 15:08 ` Sander Eikelenboom
2015-04-15 20:58 ` Konrad Rzeszutek Wilk
2015-04-15 21:14 ` Sander Eikelenboom
2015-06-10 1:02 ` Is: qemu-xen mishandling upper 64-bit BAR compared to qemu-tradWas:Re: " Konrad Rzeszutek Wilk
2015-06-10 8:44 ` Jan Beulich
2015-06-10 11:13 ` Stefano Stabellini
2015-06-10 12:02 ` Jan Beulich
2015-06-10 14:33 ` Konrad Rzeszutek Wilk
2015-06-10 20:53 ` [PATCH QEMU-XEN] xen/pt: Start with emulated PCI_COMMAND set to zero konrad
2015-06-11 7:47 ` Jan Beulich
2015-06-11 11:19 ` Sander Eikelenboom
2015-06-12 13:37 ` Konrad Rzeszutek Wilk
2015-06-15 16:19 ` Stefano Stabellini
2015-06-15 18:46 ` Konrad Rzeszutek Wilk
2015-06-16 7:33 ` Jan Beulich
2015-06-24 15:59 ` Konrad Rzeszutek Wilk
2015-06-25 7:34 ` Jan Beulich
2015-06-25 12:08 ` Stefano Stabellini
2015-06-25 17:23 ` Konrad Rzeszutek Wilk
2015-06-26 6:10 ` Jan Beulich
2015-06-15 16:15 ` Is: qemu-xen mishandling upper 64-bit BAR compared to qemu-tradWas:Re: Dom0 linux 4.0 + devel/for-linus-4.1 branch: p2m.c:884:d0v0 gfn_to_mfn failed! gfn=ffffffff001ed type:4 Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552BB166.1060505@citrix.com \
--to=david.vrabel@citrix.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.