All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Ewan Mellor <ewan@xensource.com>,
	"Zhai, Edwin" <edwin.zhai@intel.com>
Subject: Re: memsize for HVM save/restore
Date: Mon, 26 Mar 2007 11:13:18 +0800	[thread overview]
Message-ID: <20070326031318.GZ21485@edwin-srv.sh.intel.com> (raw)
In-Reply-To: <C22AE3C4.C2D9%Keir.Fraser@cl.cam.ac.uk>

On Sat, Mar 24, 2007 at 02:18:44PM +0000, Keir Fraser wrote:
> On 24/3/07 11:37, "Zhai, Edwin" <edwin.zhai@intel.com> wrote:
> 
> > But then qemu broke, because it also require the memsize to locate the share
> > page. We can't use the previous method, as it requires a lot of changes in
> > qemu.
> 
> Doesn't your new 'general layout' patch put the PFNs of xenstore, ioreq,
> buffered_ioreq in the saved image, and restore in xc_hvm_restore? Qemu-dm

yes,

> should obtain the addresses via HVMOP_get_param.
> 
> You do not need the memsize parameter.

I don't think so.
Besides locating PFNs, memsize is also used in QEMU for other purpose, such as 
bitmap allocation, dev init and map_foreign*. So memsize is a must for qemu 
init.

See following code in xc_hvm_build:
if ( v_end > HVM_BELOW_4G_RAM_END )
    shared_page_nr = (HVM_BELOW_4G_RAM_END >> PAGE_SHIFT) - 1;
else
    shared_page_nr = (v_end >> PAGE_SHIFT) - 1;

So it's impossible to get memsize by saved PFNs when restore a big memory guest.

 
> 
>  -- Keir
> 

-- 
best rgds,
edwin

  reply	other threads:[~2007-03-26  3:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24 11:37 memsize for HVM save/restore Zhai, Edwin
2007-03-24 14:18 ` Keir Fraser
2007-03-26  3:13   ` Zhai, Edwin [this message]
2007-03-26 18:31     ` Keir Fraser
2007-03-27 15:42       ` Zhai, Edwin
2007-03-27 15:52         ` 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=20070326031318.GZ21485@edwin-srv.sh.intel.com \
    --to=edwin.zhai@intel.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=ewan@xensource.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.