From: Jes Sorensen <jes@sgi.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] [patch 0/2] QEMU maxcpus support v2
Date: Wed, 24 Jun 2009 10:35:12 +0200 [thread overview]
Message-ID: <20090624083512.766907560@sgi.com> (raw)
Hi,
Here is an updated version of the ,maxcpus patch, now adding it as a
sub-option to -smp, ie, -smp <n>,maxcpus=<y>. In addition it has the
QEMU BOCHS patches to make the BIOS use the value passed.
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.
Cheers,
Jes
next reply other threads:[~2009-06-24 8:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 8:35 Jes Sorensen [this message]
2009-06-24 8:35 ` [Qemu-devel] [patch 1/2] Introduce -smp , maxcpus= flag to specify maximum number of CPUS Jes Sorensen
2009-06-24 9:02 ` [Qemu-devel] " Avi Kivity
2009-06-24 9:02 ` Jes Sorensen
2009-06-24 9:15 ` Avi Kivity
2009-06-24 12:04 ` Jes Sorensen
2009-06-24 8:35 ` [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen
2009-07-09 21:57 ` Anthony Liguori
2009-07-12 9:39 ` Avi Kivity
2009-07-12 13:23 ` Anthony Liguori
2009-07-12 13:36 ` Avi Kivity
2009-07-14 8:38 ` Jes Sorensen
2009-07-14 9:21 ` Filip Navara
2009-07-14 9:32 ` Gleb Natapov
2009-07-14 10:16 ` Alexander Graf
2009-07-14 11:15 ` Filip Navara
2009-07-14 11:21 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2009-07-14 12:53 [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v2 Jes Sorensen
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=20090624083512.766907560@sgi.com \
--to=jes@sgi.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.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 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).