From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=34982 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OCWaE-0006zh-1Y
	for qemu-devel@nongnu.org; Thu, 13 May 2010 07:28:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <jan.kiszka@web.de>) id 1OCThK-0002KN-UP
	for qemu-devel@nongnu.org; Thu, 13 May 2010 04:23:16 -0400
Received: from fmmailgate01.web.de ([217.72.192.221]:47694)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <jan.kiszka@web.de>) id 1OCT1t-0003sx-FF
	for qemu-devel@nongnu.org; Thu, 13 May 2010 03:40:25 -0400
Message-ID: <4BEBACE5.4010306@web.de>
Date: Thu, 13 May 2010 09:40:21 +0200
From: Jan Kiszka <jan.kiszka@web.de>
MIME-Version: 1.0
References: <AANLkTil-VFu1P4q_4athK2r1XkBgZh47NGjj2wtZw3G9@mail.gmail.com>
In-Reply-To: <AANLkTil-VFu1P4q_4athK2r1XkBgZh47NGjj2wtZw3G9@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig47CAA8E29DE74F30CED711F7"
Sender: jan.kiszka@web.de
Subject: [Qemu-devel]
	Re: [PATCH, RFC 0/4] monitor device info infrastructure
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig47CAA8E29DE74F30CED711F7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Blue Swirl wrote:
> Hi all,
>=20
> I finally refreshed some of my monitor patches. PCI and HPET patches
> (attached, they don't apply anymore) need more work because of the new
> monitor design.
>=20
> The patches provide a method for devices to register new monitor
> commands. This fixes some design problems, like useless
> pic_info/irq_info functions for most architectures.
>=20
> I think automation via qdev field was requested the last time. I added
> something like this, though it doesn't fit the cases where several
> functions need to be registered.
>=20
> Comments?

I'll soon send out a series that adds "device_show <qdev-path>" to
visualize the full state, something that will at least obsolete "info
pic" and "info hpet" sooner or later, maybe even more. Also, I would
like to qdev'ify CPUs in order to make them reachable for device_show
(which evaluates qdev->info.vmstate).

I'm not sure: How many use cases for a "dev_info" would remain?
Moreover, to dump statistics, we should rather add some "device_stats
<qdev-path>" command instead of mixing both usages under an info command.=


Jan


--------------enig47CAA8E29DE74F30CED711F7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkvrrOUACgkQitSsb3rl5xRTmwCg7Ygcs06eYMOYeT6fBMI+uj3C
qwkAoNg2BQsm8cGQuyLNLxeZoV8mH0D7
=4DG6
-----END PGP SIGNATURE-----

--------------enig47CAA8E29DE74F30CED711F7--