All of lore.kernel.org
 help / color / mirror / Atom feed
From: tgh <wwwwww4187@sina.com.cn>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
	xen-devel@lists.xensource.com,
	John Levon <levon@movementarian.org>
Subject: Re: [PATCH] (resent) NUMA node migration
Date: Sat, 22 Dec 2007 17:42:01 +0800	[thread overview]
Message-ID: <476CDBE9.8000507@sina.com.cn> (raw)
In-Reply-To: <DD74FBB8EE28D441903D56487861CD9D25CA8F09@lonpexch01.citrite.net>

hi
for PV, is there a fast checkpoint mechanism available ? how does it 
work , that is ,what paremeters in the common line"xm migration ",or how 
to invoke it? and how does it work ,say ,fast checkpoint for PV in an 
incremental way such as live migration, or how to fast checkpoint ?

Thanks in advance


Ian Pratt 写道:
>
> Doing page migration for HVM guests is easy as you can just stop the
> guest, copy a bunch of pages and update the p2m table, flush the shadow
> page table cache and all VCPU's TLBs, then resume. Doing it live is a
> little tricky as you have to go from MFN's to PTE's which currently
> requires a full shadow page table scan. [Though some of the experimental
> page sharing patches maintain linked lists of backpointers, and we could
> switch to a shadow mode that supports this while doing page migration] 
>
> PV guests are a little more challenging as all references in the
> direct-mode page tables need to be updated. We also need to make sure
> that the guest isn't holding MFNs outside of pagetables, so we need to
> get all the VCPUs into a known state. The best way of handling this is
> to use the PV fast checkpoint support to freeze the guest, copy the
>   

> badly located pages, scan and update all pagetables, resume from
> checkpoint. This would make a nice little project for someone...
>
> Ian
>
>  
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>   

  reply	other threads:[~2007-12-22  9:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 22:39 [PATCH] (resent) NUMA node migration Andre Przywara
2007-12-21 22:45 ` Daniel P. Berrange
2007-12-22  0:53 ` John Levon
2007-12-22  1:15   ` Ian Pratt
2007-12-22  9:42     ` tgh [this message]
2007-12-23 21:12       ` Mark Williamson
2008-01-09 14:35   ` Andre Przywara

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=476CDBE9.8000507@sina.com.cn \
    --to=wwwwww4187@sina.com.cn \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=andre.przywara@amd.com \
    --cc=levon@movementarian.org \
    --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.