From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57805)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1WzOoQ-0002eE-UU
	for qemu-devel@nongnu.org; Tue, 24 Jun 2014 07:23:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1WzOoH-0002C7-Vt
	for qemu-devel@nongnu.org; Tue, 24 Jun 2014 07:22:54 -0400
Received: from cantor2.suse.de ([195.135.220.15]:49114 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1WzOoH-0002Bf-Qc
	for qemu-devel@nongnu.org; Tue, 24 Jun 2014 07:22:45 -0400
Message-ID: <53A95F81.7070808@suse.de>
Date: Tue, 24 Jun 2014 13:22:41 +0200
From: =?ISO-8859-15?Q?Andreas_F=E4rber?= <afaerber@suse.de>
MIME-Version: 1.0
References: <53A8366B.1020301@ozlabs.ru>
	<53A840C8.8060607@redhat.com>	<53A89D98.3030708@ozlabs.ru>
	<53A9095B.3070803@redhat.com>	<53A90E9C.2020300@ozlabs.ru>
	<87bnti202c.fsf@blackfin.pond.sub.org>
In-Reply-To: <87bnti202c.fsf@blackfin.pond.sub.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] machines and versions - why so many?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>, Marcel Apfelbaum <marcel.a@redhat.com>, Alexey Kardashevskiy <aik@ozlabs.ru>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Paul Mackerras <paulus@samba.org>, Paolo Bonzini <pbonzini@redhat.com>, Alexander Graf <agraf@suse.com>

Am 24.06.2014 10:17, schrieb Markus Armbruster:
> Back then gerd created a way to do the compatibility stuff without
> getting into the other target's hair: compat_props.  They've served us
> well enough, but now that more targets get interested in migration,
> their shortcomings start to hurt.  Having to duplicate device
> compatibility gunk in multiple places, all far away from the device, is
> decidedly suboptimal.  Better ideas welcome.

Might it make sense to reconsider the proposed machine type hierarchy
and have machine-2.2 <- pc-i440fx-2.2, with global properties in
machine-x.y types and pc_compat_x_y() taking care of PC inheritence? We
can't inherit from both pc-x.y and machine-x.y though, so probably not,
just throwing thoughts around.

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg