From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: thread/core siblings info for guests
Date: Mon, 06 Oct 2008 12:23:16 +0200
Message-ID: <48E9E714.1030601@redhat.com>
References: <8EA2C2C4116BF44AB370468FBF85A7779B418DEF@orsmsx504.amr.corp.intel.com> <48E88C62.9030103@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Kamble, Nitin A" <nitin.a.kamble@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:48791 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751724AbYJFKXV (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 6 Oct 2008 06:23:21 -0400
In-Reply-To: <48E88C62.9030103@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Avi Kivity wrote:
> 
> Not that I know of.  Indeed finer control over cpuid is needed.  We need
> to support at least three modes:
> 
> - default: expose some machine that is likely to be widely supported
> - host: expose as much of the host cpu as we can
> - managed: management application controls everything

qemu has an array with predefined cpu types, selectable via -cpu <name>.
 IMHO it would be a good idea to reuse that, especially with the
upstream merge in mind ...

cheers,
  Gerd