From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=51226 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OPWNp-0005ub-KB
	for qemu-devel@nongnu.org; Fri, 18 Jun 2010 03:53:02 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <kraxel@redhat.com>) id 1OPWNo-0001qF-0v
	for qemu-devel@nongnu.org; Fri, 18 Jun 2010 03:53:01 -0400
Received: from mx1.redhat.com ([209.132.183.28]:48702)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <kraxel@redhat.com>) id 1OPWNn-0001pv-Qc
	for qemu-devel@nongnu.org; Fri, 18 Jun 2010 03:52:59 -0400
Message-ID: <4C1B25CE.5080003@redhat.com>
Date: Fri, 18 Jun 2010 09:52:46 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
References: <20100614054923.879.33717.stgit@localhost.localdomain>	
	<m3d3vr48f6.fsf@blackfin.pond.sub.org>
	<1276811010.3216.25.camel@x201>
In-Reply-To: <1276811010.3216.25.camel@x201>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: RFC qdev path semantics
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.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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: chrisw@redhat.com, kvm@vger.kernel.org, Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org, paul@codesourcery.com, avi@redhat.com

   Hi,

>> Bus names are chosen by the system as follows:
>>
>> * If the driver of the parent device model provides a name, use that.
>>
>> * Else, if the parent device has id ID, use ID.NUM, where NUM is the bus
>>    number, counting from zero in creation order.
>>
>> * Else, use TYPE.NUM, where TYPE is derived from the bus type, and NUM
>>    is the bus number, as above.
>>
>> ### Paul proposes to drop ID.NUM.
>>
>> ### Paul proposes to either drop TYPE.NUM (and require drivers to
>>      provide bus names), or make NUM count separately for each bus type.
>
> I agree, instance numbers are not stable.

NUM in the child bus name has *nothing* to do with the savevm instance 
number.

cheers,
   Gerd