From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MGdSW-00075a-5I
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:32:36 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MGdSR-00074y-4S
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:32:35 -0400
Received: from [199.232.76.173] (port=36449 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MGdSQ-00074v-Q2
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:32:30 -0400
Received: from mail2.shareable.org ([80.68.89.115]:44546)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1MGdSP-00019N-Mf
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:32:30 -0400
Date: Tue, 16 Jun 2009 19:32:22 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3
	03/13] qemu: add routines to manage PCI capabilities]
Message-ID: <20090616183222.GH11893@shareable.org>
References: <4A364B53.9080007@codemonkey.ws> <4A364FE0.40204@redhat.com>
	<4A3651EB.3070204@codemonkey.ws> <4A36555A.4090303@redhat.com>
	<4A3659A0.3050108@codemonkey.ws>
	<20090615143737.GB14405@redhat.com>
	<4A3662BA.6030304@codemonkey.ws>
	<20090615150804.GH7233@redhat.com> <4A3664EE.30207@redhat.com>
	<4A3665A0.7000702@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A3665A0.7000702@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: Avi Kivity <avi@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>, Rusty Russell <rusty@rustcorp.com.au>, kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, Glauber Costa <glommer@redhat.com>, dlaor@redhat.com, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl <blauwirbel@gmail.com>, Christian Borntraeger <borntraeger@de.ibm.com>, Paul Brook <paul@codesourcery.com>, Mark McLoughlin <markmc@redhat.com>

Avi Kivity wrote:
> Another issue is enumeration.  Guests will present their devices in the 
> order they find them on the pci bus (of course enumeration is guest 
> specific).  So if I have 2 virtio controllers the only way I can 
> distinguish between them is using their pci slots.

virtio controllers really should have a user-suppliable string or UUID
to identify them to the guest.  Don't they?

-- Jamie