From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZC29z-0008HD-OA for qemu-devel@nongnu.org; Mon, 06 Jul 2015 04:53:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZC29v-0005Zc-JA for qemu-devel@nongnu.org; Mon, 06 Jul 2015 04:53:55 -0400 Message-ID: <559A421B.3030707@suse.de> Date: Mon, 06 Jul 2015 10:53:47 +0200 From: Alexander Graf MIME-Version: 1.0 References: <1435869974-22848-1-git-send-email-mdroth@linux.vnet.ibm.com> <20150703071841.GC16378@voom.redhat.com> In-Reply-To: <20150703071841.GC16378@voom.redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] target-ppc: fix hugepage support when using memory-backend-file List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson , Michael Roth Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, qemu-stable@nongnu.org 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 > Reviewed-by: David Gibson > Thanks, applied to ppc-next. Alex