From: John Byrne <john.l.byrne@hp.com>
To: ian.pratt@cl.cam.ac.uk
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Live migration leaves page tables read-only?
Date: Thu, 30 Nov 2006 15:36:21 -0800 [thread overview]
Message-ID: <456F6AF5.2090005@hp.com> (raw)
In-Reply-To: <456CF5F9.7070009@hp.com>
John Byrne wrote:
> Ian Pratt wrote:
>>> I forgot to mention that a very simple test case I wrote using shared
>>> memory and the mprotect call didn't fail. So, the only test case I
>> have
>>> at the moment is to run SAP.
>>
>> What happens if you use non-live relo?
>
> I thought I had tested that way back at the beginning without seeing the
> problem, but I must not have, because I just retested it to be sure and
> it died the same way. (Now I am truly confused and I need to go back and
> re-examine some of my earlier experiments.)
>
After redoing some of my tests and understanding more about how Xen
handles page tables, I started looking at ptwr_do_page_fault() and put
debugging code into it. (On Xen 3.0.3 x86-64.) The fixup is failing in
x86_emulate_memop(). Building a debug version of Xen provided some
additional information (the final line is from my debugging, after the
":" is domid, addr, pte, pte flags, type_info, page owner, domain):
(XEN) DOM1: (file=mm.c, line=1682) Bad type (saw 0000000028000001 != exp
00000000e0000000) for mfn c8de3 (pfn 12491)
(XEN) DOM1: (file=mm.c, line=606) Error getting mfn c8de3 (pfn 12491)
from L1 entry 00000000c8de3167 for dom1
(XEN) DOM1: (file=mm.c, line=1682) Bad type (saw 0000000028000001 != exp
00000000e0000000) for mfn c8de3 (pfn 12491)
(XEN) DOM1: (file=mm.c, line=606) Error getting mfn c8de3 (pfn 12491)
from L1 entry 00000000c8de3067 for dom1
(XEN) DOM1: (file=mm.c, line=3120) ptwr_emulate: could not
get_page_from_l1e()
(XEN) ptwr_do_page_fault,3253:1 ffff880011065bc0 80100000ca20f065 801065
28000001 ffff830000fe7080 ffff830000fe7080
I'll keep following this down, but any help would be appreciated.
Thanks,
John Byrne
next prev parent reply other threads:[~2006-11-30 23:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 0:13 Live migration leaves page tables read-only? John Byrne
2006-11-29 0:22 ` John Byrne
2006-11-29 1:36 ` Ian Pratt
2006-11-29 2:52 ` John Byrne
2006-11-29 7:42 ` Keir Fraser
2006-11-29 16:49 ` John Byrne
2006-11-30 23:36 ` John Byrne [this message]
2006-12-01 1:13 ` Ian Pratt
2006-12-09 5:40 ` John Byrne
2006-12-09 5:44 ` John Byrne
2006-12-09 8:33 ` Ian Pratt
2006-12-09 9:22 ` Keir Fraser
2006-12-09 9:34 ` Keir Fraser
2006-12-09 9:48 ` Keir Fraser
2006-12-11 17:00 ` Joe Bonasera
2006-12-11 18:29 ` Ian Pratt
2006-12-11 19:55 ` John Byrne
2006-12-11 21:30 ` Joe Bonasera
2007-01-14 4:11 ` John Byrne
2007-01-14 8:21 ` Ian Pratt
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=456F6AF5.2090005@hp.com \
--to=john.l.byrne@hp.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.