From: Dave McCracken <dcm@mccr.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH 1/2] PV hugepages - Xen patch
Date: Wed, 8 Oct 2008 13:28:46 -0500 [thread overview]
Message-ID: <200810081328.46262.dcm@mccr.org> (raw)
In-Reply-To: <C512B667.1DFE2%keir.fraser@eu.citrix.com>
On Wednesday 08 October 2008, Keir Fraser wrote:
> On 8/10/08 18:05, "Dave McCracken" <dcm@mccr.org> wrote:
> > On Friday 03 October 2008, Keir Fraser wrote:
> >> * This surely breaks save/restore, since the restore code is not
> >> superpage-aware.
> >
> > I don't have this one solved yet. I'm working on it.
>
> Actually this is an interesting one. For a PV guest it may be in general
> unsolvable, since the target machine may not have allocatable 2MB extents.
> It may also screw live migration since 2MB is a very coarse granularity to
> do dirty-page tracking. One option: perhaps the PV kernel could shatter and
> then reconstruct (as best it can) superpage mappings across save/restore?
> I'm actually not sure what's for the best here. Perhaps just make 2MB
> mappings and save/restore mutually exclusive for now?
Yeah, that's what I'm finding. I think it's a good idea to document for now
that hugepages don't work with save/restore. I'll continue to dig into it
and try to figure out a scheme to make it work as a future enhancement.
Dave McCracken
next prev parent reply other threads:[~2008-10-08 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 23:26 [PATCH 1/2] PV hugepages - Xen patch Dave McCracken
2008-10-03 8:58 ` Keir Fraser
2008-10-08 17:05 ` Dave McCracken
2008-10-08 18:11 ` Keir Fraser
2008-10-08 18:28 ` Dave McCracken [this message]
2008-10-08 18:50 ` Keir Fraser
2008-10-08 22:07 ` Dave McCracken
2008-10-09 6:45 ` Keir Fraser
2008-10-09 10:21 ` Keir Fraser
2008-10-08 22:50 ` Jeremy Fitzhardinge
2008-10-09 8:38 ` Daniel P. Berrange
2008-10-10 0:05 ` Jeremy Fitzhardinge
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=200810081328.46262.dcm@mccr.org \
--to=dcm@mccr.org \
--cc=Ian.Pratt@eu.citrix.com \
--cc=keir.fraser@eu.citrix.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.