From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47641) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBjKT-0001m0-Fn for qemu-devel@nongnu.org; Fri, 07 Feb 2014 06:10:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WBjKO-000641-Fr for qemu-devel@nongnu.org; Fri, 07 Feb 2014 06:10:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:18255) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBjKN-00063w-LM for qemu-devel@nongnu.org; Fri, 07 Feb 2014 06:10:35 -0500 Message-ID: <52F4BF25.7020804@redhat.com> Date: Fri, 07 Feb 2014 12:10:29 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1391621709-15620-1-git-send-email-afaerber@suse.de> <52F2795D.10708@redhat.com> <52F27A1D.2040504@suse.de> <52F27B5E.2030403@suse.de> <52F27BA9.5070000@redhat.com> <52F27E24.1060104@suse.de> <52F4B84D.9040901@redhat.com> <52F4BCD8.5020400@suse.de> In-Reply-To: <52F4BCD8.5020400@suse.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] scripts: Add qom-tree script as modern equivalent of info qtree List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, armbru@redhat.com, aliguori@amazon.com, lcapitulino@redhat.com Il 07/02/2014 12:00, Andreas F=C3=A4rber ha scritto: > Am 07.02.2014 11:41, schrieb Paolo Bonzini: >> Il 05/02/2014 19:08, Andreas F=C3=A4rber ha scritto: >>> http://wiki.qemu.org/Features/QOM#TODO >>> >>> Anthony wants buses to go away completely. So that seems a legacy >>> concept to me even though they do not seem to be gone tomorrow. >> >> The way I read that, buses would be replaced by controller devices. >> >> This is unrelated to showing the devices according to the bus topology >> (which still exists in either approach), which is what "info qtree" >> device. I guess if controller devices existed, you'd add interfaces >> like BusProvider and BusChildEnumerator, or equivalently some "magic" >> properties to do the same, and use that in "info qtree". > > Actually my point was that in Anthony's model you get devices on their > controller device simply by looking at link properties on > the foo controller device. No special bus code is required any more! Kind of... There may still be other links (e.g. to the hotplug handler=20 in Igor's series), and you may still want to organize your dump so that=20 the bus hierarchy is emphasized. You cannot unconditionally "expand"=20 all links, since they can be recursive. Paolo