From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: KVM call minutes July 31th
Date: Tue, 31 Jul 2012 12:40:14 -0300
Message-ID: <20120731154014.GL24331@otherpad.lan.raisama.net>
References: <87haso6ly2.fsf@elfo.mitica>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
To: Juan Quintela <quintela@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:25186 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754326Ab2GaPje (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 31 Jul 2012 11:39:34 -0400
Content-Disposition: inline
In-Reply-To: <87haso6ly2.fsf@elfo.mitica>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Tue, Jul 31, 2012 at 04:32:05PM +0200, Juan Quintela wrote:
> - 1.2 plans for CPU model versioning/compatibility (eduardo)
>   (global properties vs QOM vs qdev)
>   how to do it ?  configuration file?  moving back to the code?
>   different external interface from internal one

Another question:

Anthony, you  mentioned that you had a series to convert the CPU to be
actual qdev device objects. Do you have a pointer for it? I couldn't
find it.

All I remember (from a call 2 or 3 weeks ago) was that the conversion
was difficult because it would make *-user pull qdev, and that was not a
trivial task.

-- 
Eduardo