From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models.. Date: Thu, 24 Dec 2009 15:45:38 +0200 Message-ID: <4B337082.2050904@redhat.com> References: <4B2F19CC.5020808@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list , qemu-devel@nongnu.org To: john cooper Return-path: Received: from mx1.redhat.com ([209.132.183.28]:54963 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751583AbZLXNpl (ORCPT ); Thu, 24 Dec 2009 08:45:41 -0500 In-Reply-To: <4B2F19CC.5020808@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/21/2009 08:46 AM, john cooper wrote: > This adds definitions for contemporary processors > which may be selected via -cpu, as an > alternative to the existing use of -cpu qemu64 > augmented with a series of feature flags. > > The primary motivation was determination of a > least common denominator within a given processor > class for simplification of guest migration. It > is still possible to modify an arbitrary model via > additional feature flags however the goal here was > to make doing so unnecessary in typical usage. The > other consideration was providing models names > reflective of current processors. Both AMD and > Intel have reviewed the models in terms of balancing > generality of migration vs. excessive feature > downgrade relative to released silicon. > > A cpu feature 'check' option is also added which > warns when feature flags (either implicit in a cpu > model or explicit on the command line) would have > otherwise been quietly disabled for a guest. > > This patch was tested relative to qemu-kvm.git. > Nothing kvm-specific in there, yes? If so, it should go though qemu.git. -- error compiling committee.c: too many arguments to function