From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=58100 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q2Myy-0004cW-0a for qemu-devel@nongnu.org; Wed, 23 Mar 2011 08:16:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q2Myw-0005DN-Hn for qemu-devel@nongnu.org; Wed, 23 Mar 2011 08:16:11 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:57965) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q2Myw-0005DD-DZ for qemu-devel@nongnu.org; Wed, 23 Mar 2011 08:16:10 -0400 Received: by ywl41 with SMTP id 41so3993372ywl.4 for ; Wed, 23 Mar 2011 05:16:09 -0700 (PDT) Message-ID: <4D89E47F.300@codemonkey.ws> Date: Wed, 23 Mar 2011 07:15:59 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: Supsend/resume regression in c995b4 WAS: Re: [Qemu-devel] [PATCH] Fix migration uint8 arrys handled References: <1300200805-13928-1-git-send-email-quintela@redhat.com> <4D87EC8A.3010309@linux.vnet.ibm.com> <4D87FF80.6060300@us.ibm.com> <4D886BB6.80906@redhat.com> <4D8878BE.5070102@linux.vnet.ibm.com> <4D887CB3.6010505@redhat.com> <4D888CFF.5050204@linux.vnet.ibm.com> <4D888E7F.8040700@linux.vnet.ibm.com> <4D888F6A.1000009@siemens.com> <4D88A372.9040808@us.ibm.com> <4D89B915.80406@redhat.com> In-Reply-To: <4D89B915.80406@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Jan Kiszka , Anthony Liguori , Stefan Berger , "qemu-devel@nongnu.org" , Juan Quintela On 03/23/2011 04:10 AM, Avi Kivity wrote: > On 03/22/2011 03:26 PM, Anthony Liguori wrote: >> >> Here's how I propose we tackle this. This patch adds a -dump-savevm >> option that takes a version. It spits out all of the fields we save >> for a particular version (well, not really, but it should). We also >> can add type information. The idea is that we'd write a simple test >> case (using gtester) that ran through and dumped the schema for each >> version. We'd store the schema's in the tree and the test can >> compare old schema's to the current schema to check for failure. >> > > Instead of generating the schema and comparing, what about the other > way round? Write vmstate in a formal schema, and generate the code at > runtime. This is exactly where I want to go in the future. Regards, Anthony Liguori