From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Armbruster Subject: Re: RFC qdev path semantics Date: Wed, 16 Jun 2010 15:05:31 +0200 Message-ID: References: <20100614054923.879.33717.stgit@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: qemu-devel@nongnu.org, chrisw@redhat.com, kvm@vger.kernel.org, paul@codesourcery.com, kraxel@redhat.com, avi@redhat.com To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:63383 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753069Ab0FPNFl (ORCPT ); Wed, 16 Jun 2010 09:05:41 -0400 In-Reply-To: (Markus Armbruster's message of "Wed, 16 Jun 2010 11:46:05 +0200") Sender: kvm-owner@vger.kernel.org List-ID: Markus Armbruster writes: [...] > 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. ABI change: "-device lsi,id=my-scsi -device scsi-disk,bus=my-scsi.0" no longer works. > ### Paul proposes to either drop TYPE.NUM (and require drivers to > provide bus names), or make NUM count separately for each bus type. Likewise. I'm not saying we can't do this, just that we need to consider backward compatibility. [...] From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51669 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OOsJL-0006WX-9Z for qemu-devel@nongnu.org; Wed, 16 Jun 2010 09:05:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OOsJJ-0008KR-Sf for qemu-devel@nongnu.org; Wed, 16 Jun 2010 09:05:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:3096) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OOsJJ-0008KF-Hk for qemu-devel@nongnu.org; Wed, 16 Jun 2010 09:05:41 -0400 From: Markus Armbruster References: <20100614054923.879.33717.stgit@localhost.localdomain> Date: Wed, 16 Jun 2010 15:05:31 +0200 In-Reply-To: (Markus Armbruster's message of "Wed, 16 Jun 2010 11:46:05 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Qemu-devel] Re: RFC qdev path semantics List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Williamson Cc: chrisw@redhat.com, kvm@vger.kernel.org, paul@codesourcery.com, qemu-devel@nongnu.org, avi@redhat.com, kraxel@redhat.com Markus Armbruster writes: [...] > 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. ABI change: "-device lsi,id=my-scsi -device scsi-disk,bus=my-scsi.0" no longer works. > ### Paul proposes to either drop TYPE.NUM (and require drivers to > provide bus names), or make NUM count separately for each bus type. Likewise. I'm not saying we can't do this, just that we need to consider backward compatibility. [...]