From: Andre Przywara <andre.przywara@amd.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC] allow multi-core guests: introduce cores= option to -cpu
Date: Sat, 4 Jul 2009 01:45:40 +0200 [thread overview]
Message-ID: <4A4E9824.9090200@amd.com> (raw)
In-Reply-To: <200907031646.36268.paul@codesourcery.com>
Paul Brook wrote:
>> currently SMP guests happen to see <n> vCPUs as <n> different sockets.
>> Some guests (Windows comes to mind) have license restrictions and refuse
>> to run on multi-socket machines.
>> So lets introduce a "cores=" parameter to the -cpu option to let the user
>> specify the number of _cores_ the guest should see.
>
> Sounds like this should be part of the -numa option.
Sound reasonable on the first glance, but would make it rather
complicated in real life. I suppose multi-core is far more interesting
to most of the people than multi-node, so I would opt for the easier:
-smp 2,cores=2 to specify a dual core guest.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 488-3567-12
next prev parent reply other threads:[~2009-07-03 23:45 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 [this message]
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
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=4A4E9824.9090200@amd.com \
--to=andre.przywara@amd.com \
--cc=kvm@vger.kernel.org \
--cc=paul@codesourcery.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).