From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34997) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuBEq-0006zr-As for qemu-devel@nongnu.org; Wed, 25 Jul 2012 19:43:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SuBEp-0007xL-CB for qemu-devel@nongnu.org; Wed, 25 Jul 2012 19:43:32 -0400 Received: from mail-gg0-f173.google.com ([209.85.161.173]:47918) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuBEp-0007x1-8P for qemu-devel@nongnu.org; Wed, 25 Jul 2012 19:43:31 -0400 Received: by ggnp1 with SMTP id p1so1328544ggn.4 for ; Wed, 25 Jul 2012 16:43:30 -0700 (PDT) From: Anthony Liguori In-Reply-To: <1343240323-7402-1-git-send-email-ehabkost@redhat.com> References: <1343240323-7402-1-git-send-email-ehabkost@redhat.com> Date: Wed, 25 Jul 2012 18:43:25 -0500 Message-ID: <87boj3v23m.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [QEMU PATCH 0/3] versioned CPU models / per-machine-type aliases List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost , qemu-devel@nongnu.org Cc: libvir-list@redhat.com, Jiri Denemark , Gleb Natapov Eduardo Habkost writes: > Hi, > > This is the first try at a simple system to make the CPU model definitions > versioned (to allow them to get bug fixes while allowing migration from older > versions and keeping command-line compatibility), and per- machine-type aliases > for compatibility. > > The lack of CPU model versioning is blocking multiple bug fixes that are > necessary on CPU model definitions, but can't be included today because they > would break migration. > > Later, after this gets in (or at least gets some feedback), I plan to send a > proposal for a machine-friendly CPU feature / CPU model probing interface that > libvirt could use. This isn't the right approach. The CPU properties should be exposed as QOM properties which then allows the machine type globals to be used to control stuff like this. Is there a specific set of properties you want to control? As long as it's a small number, we can start with that and get something in shape for 1.2. Regards, Anthony Liguori > > Eduardo Habkost (3): > vl.c: extract qemu_machine_init() function > per-machine-type CPU model alias system > x86: pc: versioned CPU model names & compatibility aliases > > hw/boards.h | 13 +++++++++ > hw/pc_piix.c | 56 ++++++++++++++++++++++++++++++++++++ > sysconfigs/target/cpus-x86_64.conf | 18 ++++++------ > vl.c | 28 +++++++++++++++++- > 4 files changed, 105 insertions(+), 10 deletions(-) > > -- > 1.7.10.4