From: John Byrne <john.l.byrne@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Live migration leaves page tables read-only?
Date: Tue, 28 Nov 2006 16:22:52 -0800 [thread overview]
Message-ID: <456CD2DC.2020201@hp.com> (raw)
In-Reply-To: <456CD0A5.1060701@hp.com>
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.
John Byrne
John Byrne wrote:
>
> I have been trying to debug a problem live-migrating SAP on Xen-3.0.3
> x86-64 (I also tested Xen-unstable changeset 12548) without success.
>
> SAP seems to run fine on a given host; live-migrating it to another host
> causes the guest to almost immediately panic in the mprotect() call in
> the change_pte_range() routine in the set_pte_at() macro because the
> page table page it is trying to update is write-protected.
>
> My attempts at understanding where this is coming from have come to
> naught. Any help in running this down would be appreciated. I am
> perfectly willing/able to write some debugging code if I am given a few
> clues what to look for.
>
> Thanks,
>
> John Byrne
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2006-11-29 0:22 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 [this message]
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
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=456CD2DC.2020201@hp.com \
--to=john.l.byrne@hp.com \
--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.