From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Long Wang <longwang@crhc.illinois.edu>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: Re: how to enable shadow page table? Do I have to run HVM guest systems for shadow paging mode?
Date: Mon, 16 Mar 2009 10:06:26 -0700 [thread overview]
Message-ID: <49BE8712.40605@goop.org> (raw)
In-Reply-To: <20090316164824.9BE2A3400090@usps.crhc.uiuc.edu>
Long Wang wrote:
> I looked into the live migration code in Xen. I need more than the mechanism
> provided in live migration, as described below:
>
> 1. scan the states of all the memory pages of a domain, set dirty pages as
> read-only, and clear all dirty bits for all the memory pages (so read-only
> and dirty are two different bits). This procedure is done periodically.
>
> 2. When a readonly page is to be updated by the domain, the update is
> trapped into the hypervisor, when I copy the page content to another place,
> and set the page as writable (this page is not a page table page), makes the
> update.
>
> I find that the mechanism used in live migration cannot handle these. How
> can I enable shadow paging in PV? If not, do I have to find a machine with
> vmx-featured processor and run HVM for this machine?
>
Well, that's an option. But if you're going to be hacking Xen anyway,
then it sounds like log-dirty is close to what you want. But Tim is
probably the person to ask about that.
J
next parent reply other threads:[~2009-03-16 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090316164824.9BE2A3400090@usps.crhc.uiuc.edu>
2009-03-16 17:06 ` Jeremy Fitzhardinge [this message]
[not found] <20090316161757.EF9173400090@usps.crhc.uiuc.edu>
2009-03-16 16:30 ` how to enable shadow page table? Do I have to run HVM guest systems for shadow paging mode? Jeremy Fitzhardinge
2009-03-16 17:41 ` Tim Deegan
2009-03-16 17:57 ` Dan Magenheimer
2009-03-17 9:26 ` Tim Deegan
[not found] ` <9cf1a529733d7f0238e125e90fa7d3ee.squirrel@webmail.crhc.illinois.edu>
2009-03-17 9:34 ` Tim Deegan
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=49BE8712.40605@goop.org \
--to=jeremy@goop.org \
--cc=Tim.Deegan@citrix.com \
--cc=longwang@crhc.illinois.edu \
--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.