From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Andre Przywara <andre.przywara@amd.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [RFC] allow multi-core guests: introduce cores= option to -cpu
Date: Sun, 05 Jul 2009 17:53:17 +0300 [thread overview]
Message-ID: <4A50BE5D.5010005@redhat.com> (raw)
In-Reply-To: <DB13E24C-654D-4752-884E-D951A42D4CB5@suse.de>
On 07/05/2009 04:23 PM, Alexander Graf wrote:
>> I thought of using -smp [processors=]2,cores=4,threads=2 (for a total
>> of 16 threads), but I think it makes more sense with -cpu.
>
>
> I actually think putting this in -smp makes more sense. -cpu really
> shouldn't need to be touched by normal users and as long as you can
> either -cpu host or -cpu safe that should be enough.
Maybe. But in that case -cpu core2duo should imply cores=2 and -smp 2
-cpu core2duo will bring up 4 cores spread across two sockets.
> But then again maybe we should replace -smp with something more useful
> like -numa where you'd then specify #CPUs, #cores, mem-cpu connection,
> etc.
I'd prefer -numa to specify the memory topology (and connections of
sockets to memory nodes), and -smp or -cpu to specify the intra-socket
topology.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-05 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 14:41 [Qemu-devel] [RFC] allow multi-core guests: introduce cores= option to -cpu Andre Przywara
2009-07-03 14:52 ` Samuel Thibault
2009-07-03 23:28 ` Andre Przywara
2009-07-03 23:53 ` Samuel Thibault
2009-07-03 15:16 ` [Qemu-devel] " Brian Jackson
2009-07-03 22:52 ` Andre Przywara
2009-07-04 0:04 ` Jamie Lokier
2009-07-04 7:18 ` Gleb Natapov
2009-07-03 15:46 ` [Qemu-devel] " Paul Brook
2009-07-03 23:45 ` Andre Przywara
2009-07-04 5:58 ` Paul Brook
2009-07-04 15:25 ` [Qemu-devel] " Avi Kivity
2009-07-05 13:23 ` Alexander Graf
2009-07-05 14:53 ` Avi Kivity [this message]
2009-07-05 15:04 ` Gleb Natapov
2009-07-05 15:11 ` Avi Kivity
2009-07-05 15:11 ` Alexander Graf
2009-07-05 15:17 ` Avi Kivity
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=4A50BE5D.5010005@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=andre.przywara@amd.com \
--cc=kvm@vger.kernel.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).