From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Andre Przywara <andre.przywara@amd.com>,
kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC] allow multi-core guests: introduce cores= option to -cpu
Date: Sun, 05 Jul 2009 18:17:13 +0300 [thread overview]
Message-ID: <4A50C3F9.3000908@redhat.com> (raw)
In-Reply-To: <319A05B3-654C-478B-994F-12A56294CEFE@suse.de>
On 07/05/2009 06:11 PM, Alexander Graf wrote:
>
> On 05.07.2009, at 17:11, Avi Kivity wrote:
>
>> On 07/05/2009 06:04 PM, Gleb Natapov wrote:
>>> core2duo does not imply 2 cores. OSes use cpuid to discover this
>>> information.
>>>
>>
>> It does. "Core 2" is the name of the core. "Core 2 Duo" is a 2-core
>> package containing (a pair) this core. "Core 2 Solo" is a
>> single-core package containing the core.
>
> Well, then let's better make it -cpu core2, no?
Maybe have all three. But I agree -cpu core2 is better than -cpu core2duo.
> The only problem I see is how to generate the description string.
> Model number and the likes should be identical to a Core2Solo, right?
I think so.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-07-05 15:15 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
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 [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=4A50C3F9.3000908@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=andre.przywara@amd.com \
--cc=gleb@redhat.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).