From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [patch 0/2] QEMU maxcpus support
Date: Tue, 23 Jun 2009 14:37:52 +0300 [thread overview]
Message-ID: <4A40BE90.4040709@redhat.com> (raw)
In-Reply-To: <20090623100009.827553739@sgi.com>
On 06/23/2009 01:00 PM, Jes Sorensen wrote:
> Hi,
>
> This patch set adds the -maxcpus argument to QEMU and provides the
> needed patches to the BOCHS patch queue to make the BIOS use it.
>
> Specifying -maxcpus allows the user to cap the limit of possibly cpus
> of the system, as opposed to -smp which specifies the number of
> running cpus at startup. This allows us to build BIOS tables
> accordingly when trying to scale up in size, and it also allows for
> the BIOS to build smaller tables when not needed.
>
> I am going to submit a set of patches directly for BOCHS as well
> covering the BIOS part, but I am still waiting for my bochs-developers
> subscription to be enabled.
>
> Avi asked me to post this both for QEMU and the BIOS part for BOCHS.
>
I should have said this at your previous post, but it only occurred to
me now: we could have -smp 4,maxcpus=65536 instead of a new parameter.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-23 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 10:00 [Qemu-devel] [patch 0/2] QEMU maxcpus support Jes Sorensen
2009-06-23 10:00 ` [Qemu-devel] [patch 1/2] Introduce -maxcpus flag to QEMU and pass the value to the BIOS through FW_CFG Jes Sorensen
2009-06-23 10:00 ` [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
2009-06-23 11:37 ` Avi Kivity [this message]
2009-06-23 13:32 ` [Qemu-devel] Re: [patch 0/2] QEMU maxcpus support Jes Sorensen
2009-06-23 13:36 ` Avi Kivity
2009-06-23 15:07 ` Jes Sorensen
2009-06-23 15:47 ` Avi Kivity
2009-06-24 7:16 ` Jes Sorensen
2009-06-24 7:25 ` Filip Navara
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=4A40BE90.4040709@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jes@sgi.com \
--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 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.