From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MLnTL-0004Rn-6E for qemu-devel@nongnu.org; Tue, 30 Jun 2009 20:14:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MLnTG-0004RT-O4 for qemu-devel@nongnu.org; Tue, 30 Jun 2009 20:14:46 -0400 Received: from [199.232.76.173] (port=42805 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MLnTG-0004RQ-IZ for qemu-devel@nongnu.org; Tue, 30 Jun 2009 20:14:42 -0400 Received: from mx2.redhat.com ([66.187.237.31]:50109) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MLnTG-0005mL-5l for qemu-devel@nongnu.org; Tue, 30 Jun 2009 20:14:42 -0400 Subject: Re: [Qemu-devel] [PATCH 4/8] qdev/core: bus list References: <1246353962-32308-1-git-send-email-kraxel@redhat.com> <200906301218.35086.paul@codesourcery.com> <87k52t8xvk.fsf@pike.pond.sub.org> <200906301821.18245.paul@codesourcery.com> <87ab3p7cbh.fsf@pike.pond.sub.org> <4A4A6C48.3060101@codemonkey.ws> From: Markus Armbruster Date: Wed, 01 Jul 2009 02:12:35 +0200 In-Reply-To: <4A4A6C48.3060101@codemonkey.ws> (Anthony Liguori's message of "Tue\, 30 Jun 2009 14\:49\:28 -0500") Message-ID: <873a9hw9ak.fsf@pike.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Gerd Hoffmann , Paul Brook , qemu-devel@nongnu.org Anthony Liguori writes: > Markus Armbruster wrote: >> Paul Brook writes: >> >> >>> On Tuesday 30 June 2009, Markus Armbruster wrote: >>> >>>> Paul Brook writes: >>>> >>>>> On Tuesday 30 June 2009, Gerd Hoffmann wrote: >>>>> >>>>>> * maintain a list of busses. >>>>>> * maintain bus numbers. >>>>>> * add function to find busses by type / name / number. >>>>>> * add monitor command to list busses. >>>>>> >>>>> I still object to this patch. Busses should be identified by their >>>>> location in the tree, not by number. >>>>> >>>>> Paul >>>>> >>>> Location in the tree can be uniquely identified by a number. Handy when >>>> all you want is enumerate the buses, and you don't really care where >>>> they're hanging out in the tree. Why should something like that not be >>>> done? >>>> >>> The address of the BusState is also a locally unique >>> identifier. That doesn't mean it's a good thing to expose to the >>> user. >>> >>> Paul >>> >> >> Red herring. >> > > I don't think that's a very useful response. > > I think it's a perfectly valid suggestion that we should identify > buses based on the their location in the tree to users verses a number > generated based on some hashing algorithm. > > A tree location has meaning to a user. A random integer doesn't. Numbering nodes according to a well-defined tree traversal is not random. We can discuss whether using such a number in an interface is a good idea (nobody suggested to use it *instead* of tree paths). Rejecting the idea by comparing it to some internal address, however, is not a very useful contribution to such a discussion. But I figure I'm wasting my time and yours, so I'll shut up now.