From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Huth Subject: Re: [PATCH] KVM: PPC: Implement extension to report number of memslots Date: Tue, 27 Oct 2015 14:22:11 +0100 Message-ID: <562F7A83.1000304@redhat.com> References: <1444971473-26514-1-git-send-email-nikunj@linux.vnet.ibm.com> <56209C1B.2060903@redhat.com> <20151026051512.GB7687@iris.ozlabs.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: agraf@suse.de, Scott Wood To: Paul Mackerras , kvm-ppc@vger.kernel.org, kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50263 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932072AbbJ0NWO (ORCPT ); Tue, 27 Oct 2015 09:22:14 -0400 In-Reply-To: <20151026051512.GB7687@iris.ozlabs.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 26/10/15 06:15, Paul Mackerras wrote: > On Fri, Oct 16, 2015 at 08:41:31AM +0200, Thomas Huth wrote: >> Yes, we'll likely need this soon! 32 slots are not enough... > > Would anyone object if I raised the limit for PPC to 512 slots? In the long run we should really make this somehow dynamically instead. But as a first step, that should IMHO be fine. Question is whether we immediately need 512 on PPC, too? QEMU for x86 features 256 pluggable memory DIMM slots ("#define ACPI_MAX_RAM_SLOTS 256"), while PPC only has 32 ("#define SPAPR_MAX_RAM_SLOTS 32"). So maybe we are fine with less memory slots on PPC, e.g. 300 or so? Thomas