From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MFB13-0006Q4-Hz
	for qemu-devel@nongnu.org; Fri, 12 Jun 2009 13:58:13 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MFB0y-0006Mw-5J
	for qemu-devel@nongnu.org; Fri, 12 Jun 2009 13:58:12 -0400
Received: from [199.232.76.173] (port=33470 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MFB0y-0006Mn-1i
	for qemu-devel@nongnu.org; Fri, 12 Jun 2009 13:58:08 -0400
Received: from mx2.redhat.com ([66.187.237.31]:42655)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <markmc@redhat.com>) id 1MFB0x-0007KF-H9
	for qemu-devel@nongnu.org; Fri, 12 Jun 2009 13:58:07 -0400
Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3
	03/13] qemu: add routines to manage PCI capabilities]
From: Mark McLoughlin <markmc@redhat.com>
In-Reply-To: <f43fc5580906121044q6be5cb92vbbe407a83bbc10c7@mail.gmail.com>
References: <cover.1244192535.git.mst@redhat.com>
	<20090610182227.GN28601@redhat.com>
	<20090610192702.GH7416@shareable.org>
	<1244796209.16425.20.camel@blaa> <4A326B5C.5010501@codemonkey.ws>
	<1244821292.30522.56.camel@blaa> <4A327E4A.7010300@codemonkey.ws>
	<1244825303.26769.19.camel@blaa> <4A328991.3040006@codemonkey.ws>
	<1244827883.26769.44.camel@blaa>
	<f43fc5580906121044q6be5cb92vbbe407a83bbc10c7@mail.gmail.com>
Content-Type: text/plain
Date: Fri, 12 Jun 2009 18:55:23 +0100
Message-Id: <1244829323.26769.45.camel@blaa>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: Mark McLoughlin <markmc@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Carsten Otte <cotte@de.ibm.com>, kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, Glauber Costa <glommer@redhat.com>, Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Christian Borntraeger <borntraeger@de.ibm.com>, Paul Brook <paul@codesourcery.com>, Avi Kivity <avi@redhat.com>

On Fri, 2009-06-12 at 20:44 +0300, Blue Swirl wrote:

> If the device has different behavior or different properties from
> guest perspective compared to the old device, it should get a new
> device type so that you could specify in the device tree either the
> old device or the new one.

Yes, that works - it's analogous to a device (type, version) pair.

Cheers,
Mark.