All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-ppc: fix hugepage support when using memory-backend-file
Date: Mon, 06 Jul 2015 10:53:47 +0200	[thread overview]
Message-ID: <559A421B.3030707@suse.de> (raw)
In-Reply-To: <20150703071841.GC16378@voom.redhat.com>

On 07/03/15 09:18, David Gibson wrote:
> 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>
>

Thanks, applied to ppc-next.


Alex

  reply	other threads:[~2015-07-06  8:53 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
2015-07-06  8:53   ` Alexander Graf [this message]
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=559A421B.3030707@suse.de \
    --to=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --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 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.