From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N8NKj-0003Ay-B6 for qemu-devel@nongnu.org; Wed, 11 Nov 2009 19:14:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N8NKd-0002zf-3Q for qemu-devel@nongnu.org; Wed, 11 Nov 2009 19:14:39 -0500 Received: from [199.232.76.173] (port=55080 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N8NKc-0002z3-TU for qemu-devel@nongnu.org; Wed, 11 Nov 2009 19:14:34 -0500 Received: from mail-qy0-f194.google.com ([209.85.221.194]:53685) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N8NKc-0006Mj-F6 for qemu-devel@nongnu.org; Wed, 11 Nov 2009 19:14:34 -0500 Received: by qyk32 with SMTP id 32so794502qyk.4 for ; Wed, 11 Nov 2009 16:14:33 -0800 (PST) Message-ID: <4AFB5364.5030206@codemonkey.ws> Date: Wed, 11 Nov 2009 18:14:28 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1257962966-22902-1-git-send-email-agraf@suse.de> <1257962966-22902-2-git-send-email-agraf@suse.de> <4AFB324E.7020607@codemonkey.ws> <4AFB376D.2020106@suse.de> <4AFB393B.4020200@codemonkey.ws> <6B4FEE86-6534-483F-BBA5-08A7C79B8F41@suse.de> In-Reply-To: <6B4FEE86-6534-483F-BBA5-08A7C79B8F41@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 1/6] Make fw_cfg interface 32-bit aware List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: glommer@redhat.com, Juan Quintela , qemu-devel@nongnu.org, avi@redhat.com Alexander Graf wrote: > Juan, I'd really love to learn some new voodoo :-). > This whole new qdev whatever based save format was supposed to make > things like this easy, right? I would've known what to do with the old > code ... I think Juan's mentioned something about writing a doc explaining how to use VMState correctly. I think it would certainly be helpful for situations like this. But the most important part of VMState is that it converts something that was previously open coded and opaque to something that is data-driven and introspectable. I think it's done an extremely good job of achieving those goals. As we get everything converted, we can potentially figure out some ways to make this all a bit easier to understand. Right now, I think how we support backwards compatibility is admittedly awkward. Regards, Anthony Liguori > Alex