From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Tim Deegan <Tim.Deegan@eu.citrix.com>,
Wei Huang <wei.huang2@amd.com>
Cc: "Xu, Dongxiao" <dongxiao.xu@intel.com>, xen-devel@lists.xensource.com
Subject: RE: [PATCH][2/4] Enable 1GB for Xen HVM host page
Date: Tue, 23 Feb 2010 12:09:33 -0800 (PST) [thread overview]
Message-ID: <35f7866d-91f5-404d-938b-b71355d2330e@default> (raw)
In-Reply-To: <C7A9CA5B.B030%keir.fraser@eu.citrix.com>
Not sure what your point is. I was just suggesting that if
save/restore/migration doesn't work anyway, setting no_migrate
should result in a nicer error message than otherwise, and serves
as a clear "TO DO" marker for developers looking for a
"fun" project.
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: Tuesday, February 23, 2010 11:10 AM
> To: Dan Magenheimer; Tim Deegan; Wei Huang
> Cc: Keir@acsinet12.oracle.com; Xu, Dongxiao; xen-
> devel@lists.xensource.com
> Subject: Re: [Xen-devel] [PATCH][2/4] Enable 1GB for Xen HVM host page
>
> The use of 1GB extents is just a (small-ish) performance win. If you
> can
> only back with 4kB or 2MB extents on the target host it doesn't matter
> that
> much.
>
> -- Keir
>
> On 23/02/2010 17:19, "Dan Magenheimer" <dan.magenheimer@oracle.com>
> wrote:
>
> > I'll bet save/restore/migration for 1GB pages will be a fun
> challenge.
> >
> > At least please set the "no_migrate" flag automatically for
> > any domain that uses 1GB pages unless/until live migration
> > is supported.
> >
> >> -----Original Message-----
> >> From: Tim Deegan [mailto:Tim.Deegan@citrix.com]
> >> Sent: Tuesday, February 23, 2010 6:01 AM
> >> To: Wei Huang
> >> Cc: Keir@acsinet12.oracle.com; Xu, Dongxiao; xen-
> >> devel@lists.xensource.com; Fraser
> >> Subject: Re: [Xen-devel] [PATCH][2/4] Enable 1GB for Xen HVM host
> page
> >>
> >> At 17:18 +0000 on 22 Feb (1266859100), Wei Huang wrote:
> >>> Change page allocation code in Xen tools. The allocation request
> now
> >>> starts with 1GB; if that fails, then falls back to 2MB and then
> 4KB.
> >>
> >> Can we have an equivalent patch for the save/restore path please?
> That
> >> took a while to catch up when 2MB superpages were introduced.
> >>
> >> Tim.
> >>
> >> --
> >> Tim Deegan <Tim.Deegan@citrix.com>
> >> Principal Software Engineer, XenServer Engineering
> >> Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2010-02-23 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 17:18 [PATCH][2/4] Enable 1GB for Xen HVM host page Wei Huang
2010-02-23 9:38 ` Tim Deegan
2010-02-23 16:22 ` Huang2, Wei
2010-02-23 13:00 ` Tim Deegan
2010-02-23 17:19 ` Dan Magenheimer
2010-02-23 18:09 ` Keir Fraser
2010-02-23 20:09 ` Dan Magenheimer [this message]
2010-02-23 20:54 ` 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=35f7866d-91f5-404d-938b-b71355d2330e@default \
--to=dan.magenheimer@oracle.com \
--cc=Tim.Deegan@eu.citrix.com \
--cc=dongxiao.xu@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=wei.huang2@amd.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).