xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: treatment grant frames during save/restore
Date: Mon, 31 May 2010 16:29:25 +0100	[thread overview]
Message-ID: <C8299465.16556%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C03EAA80200007800004C6A@vpn.id2.novell.com>

On 31/05/2010 15:58, "Jan Beulich" <JBeulich@novell.com> wrote:

>> Yep that would probably work. And also potentially gets rid of one lot of
>> "if-hvm-else-pv" branched code in xc_domain_save.c. I'd take a patch to do
>> that if you want to pick this item up.
> 
> I'm afraid it won't: The live_p2m table gets created for pv guests only,
> but is needed as a prerequisite to calling XEN_DOMCTL_getpageframeinfo*
> (which wants MFNs as input). Hence while the hypervisor side patch is
> trivial, it doesn't get us any closer to a solution to the problem at hand.
> 
> Unless we (re-)define the meaning of the input array to this domctl to
> specify gmfn-s rather than mfn-s (at least for the hvm case; for
> auto-translate pv guests, quite obviously the save code wouldn't
> work anyway, but for those passing in gmfn-s would seem the
> natural thing here).

This is fine. We can (re-)define the domctl interface as we like, and anyway
I'm pretty sure noone uses that particular domctl on HVM guests (yet).

 -- Keir

> Or unless we want to add code to libxc to create a live_p2m for all
> guests (which I wouldn't want to take on).

      reply	other threads:[~2010-05-31 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 15:27 treatment grant frames during save/restore Jan Beulich
2010-05-27 15:37 ` Jan Beulich
2010-05-27 15:50   ` Dan Magenheimer
2010-05-27 16:02 ` Keir Fraser
2010-05-28  8:01   ` Jan Beulich
2010-05-28  8:22     ` Keir Fraser
2010-05-31 14:58       ` Jan Beulich
2010-05-31 15:29         ` Keir Fraser [this message]

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=C8299465.16556%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=JBeulich@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).