From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Jan Beulich <JBeulich@novell.com>, xen-devel@lists.xensource.com
Subject: RE: treatment grant frames during save/restore
Date: Thu, 27 May 2010 08:50:01 -0700 (PDT) [thread overview]
Message-ID: <23b54208-e368-43b0-95aa-3a87e66fa9c7@default> (raw)
In-Reply-To: <4BFEADDE0200007800004455@vpn.id2.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@novell.com]
> Sent: Thursday, May 27, 2010 9:38 AM
> To: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] treatment grant frames during save/restore
>
> >>> On 27.05.10 at 17:27, "Jan Beulich" <JBeulich@novell.com> wrote:
> > From what I can tell, grant frames get no special treatment by the
> tools
> > during save, and hence get treated as normal memory during restore.
> > If that's correct, it would seem that there's an accounting issue,
> since
> > during restore a normal RAM page will be allocated by the tools for
> each
> > grant frame, hence a domain that prior to save was below its limit
> > could now end up crossing that limit, and thus unexpectedly fail to
> > restore. If that's not a possibility, what am I missing?
>
> Ooops, just noticed that I didn't say explicitly that this is for HVM
> guests.
There was some discussion about this last September. Here's one link:
http://lists.xensource.com/archives/html/xen-devel/2009-09/msg00578.html
next prev parent reply other threads:[~2010-05-27 15:50 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 [this message]
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
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=23b54208-e368-43b0-95aa-3a87e66fa9c7@default \
--to=dan.magenheimer@oracle.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).