All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Kieran Mansley <kmansley@solarflare.com>,
	Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Live migration with MMIO pages
Date: Fri, 02 Nov 2007 10:42:07 +0000	[thread overview]
Message-ID: <C350AF7F.17D36%keir@xensource.com> (raw)
In-Reply-To: <1193995893.4327.55.camel@moonstone.uk.level5networks.com>

On 2/11/07 09:31, "Kieran Mansley" <kmansley@solarflare.com> wrote:

>> You could do that.  I think the correct test is shadow_mode_refcounts();
>> as Keir pointed out, guests whose refcounting isn't done by the shadow
>> code will have had their pagetables validated bby the PV MMU interface.
>> 
>> The test around the log-dirty code can just be on mfn_valid().
> 
> Attached is a new patch with those changes.  Seems much more sensible to
> me that way too, and it works just as well.

I changed the final chunk test from !shadow_mode_translate() to
shadow_mode_refcounts(). I think refcounts is a better test than translate
here, and also I think your test was the wrong way round!

I also note that guarding the mark-dirty-or-zap-writable-bit with
mfn_valid() is not really correct. mfn_valid() only checks whether the mfn <
max_page. I bet this would not work if you migrate on a machine with 4GB of
RAM, as the MMIO hole will be below max_page. Really mfn_valid needs to
handle such MMIO holes, or the shadow code needs to be using a test other
than mfn_valid in many places (e.g., the function iomem_page_test() that you
added before).

 -- Keir

  reply	other threads:[~2007-11-02 10:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 12:19 Live migration with MMIO pages Kieran Mansley
2007-10-31 13:32 ` Keir Fraser
2007-10-31 14:03   ` Kieran Mansley
2007-10-31 14:08     ` Keir Fraser
2007-10-31 16:34       ` Kieran Mansley
2007-10-31 16:44         ` Keir Fraser
2007-10-31 17:14           ` Kieran Mansley
2007-10-31 17:31           ` Tim Deegan
2007-10-31 18:23             ` Keir Fraser
2007-11-01 11:18             ` Kieran Mansley
2007-11-01 11:34               ` Tim Deegan
2007-11-01 16:36                 ` Kieran Mansley
2007-11-01 16:43                   ` Tim Deegan
2007-11-02  9:31                     ` Kieran Mansley
2007-11-02 10:42                       ` Keir Fraser [this message]
2007-11-02 10:51                         ` Keir Fraser

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=C350AF7F.17D36%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=kmansley@solarflare.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.