From: George Dunlap <george.dunlap@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] libxc: fix claim mode when creating HVM guest
Date: Mon, 27 Jan 2014 19:09:45 +0000 [thread overview]
Message-ID: <52E6AEF9.9050406@eu.citrix.com> (raw)
In-Reply-To: <1390845218-823-1-git-send-email-wei.liu2@citrix.com>
On 01/27/2014 05:53 PM, Wei Liu wrote:
> The original code is wrong because:
> * claim mode wants to know the total number of pages needed while
> original code provides the additional number of pages needed.
> * if pod is enabled memory will already be allocated by the time we try
> to claim memory.
>
> So the fix would be:
> * move claim mode before actual memory allocation.
> * pass the right number of pages to hypervisor.
>
> The "right number of pages" should be number of pages of target memory
> minus VGA_HOLE_SIZE, regardless of whether PoD is enabled.
>
> This fixes bug #32.
>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Cc: Konrad Wilk <konrad.wilk@oracle.com>
> Cc: George Dunlap <george.dunlap@eu.citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Reviewed-by: George Dunlap <george.dunlap@eu.citrix.com>
> ---
> WRT 4.4 release: this patch should be accpeted, otherwise PoD + claim
> mode is complete broken. If this patch is deemed too complicated, we
> should flip the switch to disable claim mode by default for 4.4.
I think a more reasonable mitigation strategy would simply be to ignore
claim mode when constructing a domain that uses PoD.
I'm inclined to take this one. Since claim mode is on by default, the
currently-working path should get exercised well before the release to
shake out any bugs. The other path doesn't work at all currently
(AFAICT) unless you disable claim mode -- which is still available as a
work-around, even if there is a bug in this patch.
I'll wait a day or two for others to speak up before giving it a formal
ack, just in case.
-George
next prev parent reply other threads:[~2014-01-27 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 17:53 [PATCH] libxc: fix claim mode when creating HVM guest Wei Liu
2014-01-27 19:09 ` George Dunlap [this message]
2014-01-27 19:15 ` Konrad Rzeszutek Wilk
2014-01-28 11:28 ` Ian Campbell
2014-01-29 18:33 ` Konrad Rzeszutek Wilk
2014-01-30 14:38 ` George Dunlap
2014-02-04 15:50 ` Ian Campbell
2014-02-04 15:52 ` Ian Campbell
2014-02-04 16:00 ` Processed: " xen
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=52E6AEF9.9050406@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).