From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: RFC qdev path semantics Date: Fri, 18 Jun 2010 09:52:46 +0200 Message-ID: <4C1B25CE.5080003@redhat.com> References: <20100614054923.879.33717.stgit@localhost.localdomain> <1276811010.3216.25.camel@x201> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Markus Armbruster , qemu-devel@nongnu.org, chrisw@redhat.com, kvm@vger.kernel.org, paul@codesourcery.com, avi@redhat.com To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:18835 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753314Ab0FRHxA (ORCPT ); Fri, 18 Jun 2010 03:53:00 -0400 In-Reply-To: <1276811010.3216.25.camel@x201> Sender: kvm-owner@vger.kernel.org List-ID: 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