From: Igor Mammedov <imammedo@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] sysemu: support up to 1024 vCPUs
Date: Wed, 11 May 2016 16:20:08 +0200 [thread overview]
Message-ID: <20160511162008.72356f1c@nial.brq.redhat.com> (raw)
In-Reply-To: <146297487258.12455.11591484741503224557.stgit@bahia.huguette.org>
On Wed, 11 May 2016 16:00:04 +0200
Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> Some systems can already provide more than 255 hardware threads.
>
> Bumping the QEMU limit to 1024 seems reasonable:
> - it has no visible overhead in top
> - the limit itself has no effect on hot paths
>
> Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> ---
>
> This was tested with a pseries guest only. I'd like to know if it is okay
> for other platforms.
#git grep MAX_CPUMASK_BITS
...
hw/arm/virt.c: mc->max_cpus = MAX_CPUMASK_BITS;
hw/ppc/spapr.c: mc->max_cpus = MAX_CPUMASK_BITS;
...
you probably don't want to change all those to 1024,
see/review a similar patch where I bump it upto 288 bits
https://lists.gnu.org/archive/html/qemu-devel/2016-05/msg01101.html
in addition where does 1024 come from?
is pseries capable to provide that many CPUs?
>
> include/sysemu/sysemu.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
> index 38fb3cad35e1..89d742caa477 100644
> --- a/include/sysemu/sysemu.h
> +++ b/include/sysemu/sysemu.h
> @@ -185,7 +185,7 @@ extern int mem_prealloc;
> *
> * Note that cpu->get_arch_id() may be larger than MAX_CPUMASK_BITS.
> */
> -#define MAX_CPUMASK_BITS 255
> +#define MAX_CPUMASK_BITS 1024
>
> #define MAX_OPTION_ROMS 16
> typedef struct QEMUOptionRom {
>
next prev parent reply other threads:[~2016-05-11 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 14:00 [Qemu-devel] [PATCH] sysemu: support up to 1024 vCPUs Greg Kurz
2016-05-11 14:20 ` Igor Mammedov [this message]
2016-05-11 15:20 ` Greg Kurz
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=20160511162008.72356f1c@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=gkurz@linux.vnet.ibm.com \
--cc=pbonzini@redhat.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).