From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45120)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1WB6hY-0001Wl-Eq
	for qemu-devel@nongnu.org; Wed, 05 Feb 2014 12:56:02 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1WB6hS-0007l9-BX
	for qemu-devel@nongnu.org; Wed, 05 Feb 2014 12:55:56 -0500
Received: from mx1.redhat.com ([209.132.183.28]:21147)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1WB6hR-0007kr-J9
	for qemu-devel@nongnu.org; Wed, 05 Feb 2014 12:55:49 -0500
Message-ID: <52F27B1C.6010307@redhat.com>
Date: Wed, 05 Feb 2014 18:55:40 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1391621709-15620-1-git-send-email-afaerber@suse.de>
	<52F2795D.10708@redhat.com> <52F27A1D.2040504@suse.de>
In-Reply-To: <52F27A1D.2040504@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: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, armbru@redhat.com, aliguori@amazon.com, lcapitulino@redhat.com

Il 05/02/2014 18:51, Andreas F=C3=A4rber ha scritto:
>> > So, even though I think this script is a very welcome addition, I do=
n't
>> > think it helps settling the question of what to do with "info qtree".
>> > IMO there's no good reason to exclude busless devices from "info qtr=
ee",
>> > and it's a bug (of course less severe than crashing, but still a bug=
)
>> > that the busless nand device doesn't appear there.
> Don't you see that that is unfixable? We may be able to replace info
> qtree by an info qom-tree, which does the equivalent of this QMP-based
> script, but qtree ues a completely different display hierarchy than QOM.

Yes, that's why it's useful. :)

Busless devices can still be listed, either under their parent or as=20
siblings of the system bus.

Paolo