From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40014) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qy8qZ-0004T8-8K for qemu-devel@nongnu.org; Mon, 29 Aug 2011 16:54:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qy8qY-0006F8-1b for qemu-devel@nongnu.org; Mon, 29 Aug 2011 16:54:19 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:39913) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qy8qX-0006Ep-K6 for qemu-devel@nongnu.org; Mon, 29 Aug 2011 16:54:18 -0400 Message-ID: <4E5BFC6C.6010700@web.de> Date: Mon, 29 Aug 2011 22:54:04 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E5BE6DC.5030204@us.ibm.com> In-Reply-To: <4E5BE6DC.5030204@us.ibm.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD2F7DC2BDC2F28CE9DF1968D" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] [PATCH 0/6] Device state visualization reloaded List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Markus Armbruster , qemu-devel , Luiz Capitulino This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD2F7DC2BDC2F28CE9DF1968D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-08-29 21:22, Anthony Liguori wrote: > On 08/26/2011 09:48 AM, Jan Kiszka wrote: >> More than one year ago I posted some patches to add a monitor command >> callend device_show. The purpose of that command is to dump the state = of >> some qdev device based on its vmstate. >=20 > I have a series that does the same thing as this in a totally different= > way. Instead of a VMState interpreter, it converts all marshalling to > go through a Visitor interface. This makes it extensible to devices > that don't currently support VMState. For obtaining a raw picture of some device state, there is still gdb. What this feature is targeting at is a refined view, something VMState already represents as it (in the absence of bugs) contains the complete persistent state, and only that. Once we have QOM in place and also sorted out how VMState 2.0 may look like and how it can be extracted from or expressed within the device model, we will probably change the internals of this feature again. Jan --------------enigD2F7DC2BDC2F28CE9DF1968D 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.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5b/HAACgkQitSsb3rl5xR7xQCeOhElAtdKQ7v3Thh74yNi8JqJ y7kAoIEXA0Mf3Rf0jMtRUsvQ9VB/BjTZ =ZPHc -----END PGP SIGNATURE----- --------------enigD2F7DC2BDC2F28CE9DF1968D--