From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-ppc@nongnu.org, Anton Blanchard <anton@samba.org>,
Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH qemu] spapr: Use QEMU limit for maximum CPUs number
Date: Wed, 12 Aug 2015 10:57:42 +1000 [thread overview]
Message-ID: <20150812005742.GB19634@voom.fritz.box> (raw)
In-Reply-To: <1438832244-481-1-git-send-email-aik@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
On Thu, Aug 06, 2015 at 01:37:24PM +1000, Alexey Kardashevskiy wrote:
> sPAPR uses hard coded limit of maximum 255 supported CPUs which is
> exactly the same as QEMU-wide limit which is MAX_CPUMASK_BITS and also
> defined as 255.
>
> This makes use of a global CPU number limit for the "pseries" machine.
>
> In order to anticipate future increase of the MAX_CPUMASK_BITS
> (or to help debugging large systems), this also bumps the FDT_MAX_SIZE
> limit from 256K to 1M assuming that 1 CPU core needs roughly 512 bytes
> in the device tree so the new limit can cover up to 2048 CPU cores.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Applied to spapr-next, thanks.
--
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 --]
prev parent reply other threads:[~2015-08-12 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 3:37 [Qemu-devel] [PATCH qemu] spapr: Use QEMU limit for maximum CPUs number Alexey Kardashevskiy
2015-08-12 0:57 ` David Gibson [this message]
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=20150812005742.GB19634@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=anton@samba.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).