qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Igor Mammedov <imammedo@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Anthony Liguori <aliguori@amazon.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] vl.c: Check max_cpus limit instead of smp_cpus
Date: Thu, 08 May 2014 17:10:47 +0200	[thread overview]
Message-ID: <536B9E77.3000403@suse.de> (raw)
In-Reply-To: <CAFEAcA-iW=8PR-D5_BBxJrH-7=keipWE1zeUScM3+KP9_=1n7A@mail.gmail.com>

Am 08.05.2014 10:26, schrieb Peter Maydell:
> On 7 May 2014 23:20, Andreas Färber <afaerber@suse.de> wrote:
>> Am 07.05.2014 23:48, schrieb Peter Maydell:
>>> This is confusing. What is max_cpus
>>
>> Specified via -smp, defaults to actual CPUs.
> 
> I thought that was smp_cpus ...

smp_cpus determines how many CPUs are cold-added in a loop in the
machine init functions.

max_cpus - smp_cpus is the amount of CPUs that may be hot-added later.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      parent reply	other threads:[~2014-05-08 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 20:19 [Qemu-devel] [PATCH] vl.c: Check max_cpus limit instead of smp_cpus Eduardo Habkost
2014-05-07 21:48 ` Peter Maydell
2014-05-07 22:20   ` Andreas Färber
2014-05-08  8:26     ` Peter Maydell
2014-05-08 15:00       ` Eduardo Habkost
2014-05-08 15:07         ` Peter Maydell
2014-05-08 18:46           ` Eduardo Habkost
2014-05-08 15:10       ` Andreas Färber [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=536B9E77.3000403@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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).