From: David Gibson <david@gibson.dropbear.id.au>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-stable@nongnu.org, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH] target-ppc: fix hugepage support when using memory-backend-file
Date: Fri, 3 Jul 2015 17:18:41 +1000 [thread overview]
Message-ID: <20150703071841.GC16378@voom.redhat.com> (raw)
In-Reply-To: <1435869974-22848-1-git-send-email-mdroth@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Thu, Jul 02, 2015 at 03:46:14PM -0500, Michael Roth wrote:
> Current PPC code relies on -mem-path being used in order for
> hugepage support to be detected. With the introduction of
> MemoryBackendFile we can now handle this via:
> -object memory-file-backend,mem-path=...,id=hugemem0 \
> -numa node,id=mem0,memdev=hugemem0
>
> Management tools like libvirt treat the 2 approaches as
> interchangeable in some cases, which can lead to user-visible
> regressions even for previously supported guest configurations.
>
> Fix these by also iterating through any configured memory
> backends that may be backed by hugepages.
>
> Since the old code assumed hugepages always backed the entirety
> of guest memory, play it safe an pick the minimum across the
> max pages sizes for all backends, even ones that aren't backed
> by hugepages.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-03 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 20:46 [Qemu-devel] [PATCH] target-ppc: fix hugepage support when using memory-backend-file Michael Roth
2015-07-03 7:18 ` David Gibson [this message]
2015-07-06 8:53 ` Alexander Graf
2015-07-06 11:09 ` David Gibson
2015-07-06 11:50 ` Alexander Graf
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=20150703071841.GC16378@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-stable@nongnu.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).