qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: Supsend/resume regression in c995b4 WAS: Re: [Qemu-devel] [PATCH] Fix migration uint8 arrys handled
Date: Wed, 23 Mar 2011 20:22:48 +0900	[thread overview]
Message-ID: <AANLkTinz+wj3VSP9zuARCis34V58CZfDLHR6BQY5ay7R@mail.gmail.com> (raw)
In-Reply-To: <4D89B915.80406@redhat.com>

2011/3/23 Avi Kivity <avi@redhat.com>:
> 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.

I agree :)

Yoshi

>
> --
> error compiling committee.c: too many arguments to function
>
>
>

  reply	other threads:[~2011-03-23 11:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 14:53 [Qemu-devel] [PATCH] Fix migration uint8 arrys handled Juan Quintela
2011-03-18 12:41 ` Yoshiaki Tamura
2011-03-22  0:25 ` Stefan Berger
2011-03-22  1:46   ` Anthony Liguori
2011-03-22  9:28     ` Avi Kivity
2011-03-22 10:23       ` Stefan Berger
2011-03-22 10:40         ` Avi Kivity
2011-03-22 11:50           ` Supsend/resume regression in c995b4 WAS: " Stefan Berger
2011-03-22 11:56             ` Stefan Berger
2011-03-22 12:00               ` Jan Kiszka
2011-03-22 12:21                 ` Avi Kivity
2011-03-22 12:30                   ` Jan Kiszka
2011-03-22 12:35                     ` Avi Kivity
2011-03-22 12:33                 ` [Qemu-devel] Re: Supsend/resume regression in c995b4 WAS: " Juan Quintela
2011-03-22 12:39                   ` Jan Kiszka
2011-03-22 13:26                 ` Supsend/resume regression in c995b4 WAS: Re: [Qemu-devel] " Anthony Liguori
2011-03-22 13:55                   ` [Qemu-devel] Re: Supsend/resume regression in c995b4 WAS: " Juan Quintela
2011-03-22 13:59                     ` Anthony Liguori
2011-03-23  9:10                   ` Supsend/resume regression in c995b4 WAS: Re: [Qemu-devel] " Avi Kivity
2011-03-23 11:22                     ` Yoshiaki Tamura [this message]
2011-03-23 12:15                     ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinz+wj3VSP9zuARCis34V58CZfDLHR6BQY5ay7R@mail.gmail.com \
    --to=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanb@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).