From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MMsRB-0004wo-4b
	for qemu-devel@nongnu.org; Fri, 03 Jul 2009 19:45:01 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MMsR5-0004rR-Nk
	for qemu-devel@nongnu.org; Fri, 03 Jul 2009 19:45:00 -0400
Received: from [199.232.76.173] (port=53171 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MMsR5-0004rM-HO
	for qemu-devel@nongnu.org; Fri, 03 Jul 2009 19:44:55 -0400
Received: from wa4ehsobe005.messaging.microsoft.com ([216.32.181.15]:54522
	helo=WA4EHSOBE006.bigfish.com)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16)
	(Exim 4.60) (envelope-from <Andre.Przywara@amd.com>)
	id 1MMsR5-0006XK-5D
	for qemu-devel@nongnu.org; Fri, 03 Jul 2009 19:44:55 -0400
Message-ID: <4A4E9824.9090200@amd.com>
Date: Sat, 4 Jul 2009 01:45:40 +0200
From: Andre Przywara <andre.przywara@amd.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [RFC] allow multi-core guests: introduce cores=
	option to -cpu
References: <1246632116-31366-1-git-send-email-andre.przywara@amd.com>
	<200907031646.36268.paul@codesourcery.com>
In-Reply-To: <200907031646.36268.paul@codesourcery.com>
Content-Type: text/plain; charset="ISO-8859-15"; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org

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