From: Thomas Huth <thuth@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Cc: agraf@suse.de, Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCH] KVM: PPC: Implement extension to report number of memslots
Date: Tue, 27 Oct 2015 13:22:11 +0000 [thread overview]
Message-ID: <562F7A83.1000304@redhat.com> (raw)
In-Reply-To: <20151026051512.GB7687@iris.ozlabs.ibm.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Huth <thuth@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Cc: agraf@suse.de, Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCH] KVM: PPC: Implement extension to report number of memslots
Date: Tue, 27 Oct 2015 14:22:11 +0100 [thread overview]
Message-ID: <562F7A83.1000304@redhat.com> (raw)
In-Reply-To: <20151026051512.GB7687@iris.ozlabs.ibm.com>
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
next prev parent reply other threads:[~2015-10-27 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 4:57 [PATCH] KVM: PPC: Implement extension to report number of memslots Nikunj A Dadhania
2015-10-16 4:59 ` Nikunj A Dadhania
2015-10-16 6:41 ` Thomas Huth
2015-10-16 6:41 ` Thomas Huth
2015-10-26 5:15 ` Paul Mackerras
2015-10-26 5:15 ` Paul Mackerras
2015-10-26 23:47 ` Scott Wood
2015-10-26 23:47 ` Scott Wood
2015-10-27 13:22 ` Thomas Huth [this message]
2015-10-27 13:22 ` Thomas Huth
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=562F7A83.1000304@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@ozlabs.org \
--cc=scottwood@freescale.com \
/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.