qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 11/11] test-vmstate: add test case to verify we don't change VMState
Date: Wed, 23 Mar 2011 16:13:02 +0100	[thread overview]
Message-ID: <m3sjudq39d.fsf@neno.mitica> (raw)
In-Reply-To: <AANLkTi=82NX5cqrKx2bYDe3YUBcPaM03GN4owxQZRrp3@mail.gmail.com> (Peter Maydell's message of "Wed, 23 Mar 2011 14:36:41 +0000")

Peter Maydell <peter.maydell@linaro.org> wrote:
> On 23 March 2011 14:19, Juan Quintela <quintela@redhat.com> wrote:
>> Peter Maydell <peter.maydell@linaro.org> wrote:
>> ARM people are sending lots of vmstate changes, I guess/hope that
>> somebody is trying to get it working.
>>
>> /me looks at Peter O:-), hint, hint, ...
>
> Well, the main thing I care about currently (or did back before
> Christmas which is when I sent a patchset to add save/restore
> to a pile of ARM devices) is simple save-and-restore for debugging
> use. The rest is just that patches don't get through code review
> unless they get the vmstate stuff right, and I care about not
> being rejected :-)
>
> I think it's still the case that there are devices in
> some of the ARM devboards with no save/restore support
> at all. I would really prefer it if the default for a
> device was "I do not support this" with the things like
> USB where somebody has audited them as genuinely needing
> no save/restore code explicitly marked as "this is OK";
> then we could easily determine what needed fixing and
> not offer a broken facility to users.

I agree, but that means (again), review of all devices to change the
defaults.  It is on my ToDo list (but my ToDo list is huge :-(

>> Any idea if there are images for testing ARM?
>
> There are prebuilt images on Aurelien's website for
> ARM and others, which is the simplest thing:
> http://www.aurel32.net/info/debian_arm_qemu.php

That images don't migrate for me at all.  Guest got hung after
migration, at least some state (probably irq's) are not passed
correctly.

Later, Juan.

  reply	other threads:[~2011-03-23 15:14 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  0:16 [Qemu-devel] [PATCH 00/11] Add live migration unit tests Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 01/11] Add hard build dependency on glib Anthony Liguori
2011-03-23  8:13   ` Stefan Hajnoczi
2011-03-23  8:19     ` Roy Tam
2011-03-23  8:41       ` Stefan Hajnoczi
2011-03-23  8:58         ` Roy Tam
2011-03-23  9:19           ` [Qemu-devel] " Paolo Bonzini
2011-03-23  9:22           ` [Qemu-devel] " Stefan Hajnoczi
2011-03-23  0:16 ` [Qemu-devel] [PATCH 02/11] vmstate: register all VMStateDescriptions Anthony Liguori
2011-03-23  9:00   ` Alon Levy
2011-03-23 12:30   ` Peter Maydell
2011-03-23 12:37     ` Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 03/11] vmstate: for vmstate types that reuse the same field, make sure name is unique Anthony Liguori
2011-03-23  2:29   ` Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 04/11] sb16: fix migration quirk Anthony Liguori
2011-03-23  9:51   ` [Qemu-devel] " Juan Quintela
2011-03-23 12:16     ` Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 05/11] vga-isa: fix migration by breaking it Anthony Liguori
2011-03-23  9:54   ` [Qemu-devel] " Juan Quintela
2011-03-23  0:16 ` [Qemu-devel] [PATCH 06/11] fdc: fix migration of non-ISA fdc devices Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 07/11] eeprom93xx: Use the new hack macro to avoid duplicate field names Anthony Liguori
2011-03-23  9:58   ` [Qemu-devel] " Juan Quintela
2011-03-23 12:34     ` Anthony Liguori
2011-03-23 14:14       ` Juan Quintela
2011-03-23 14:33         ` Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 08/11] fw_cfg: make sure all VMState fields are unique Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 09/11] pckbd: make non-ISA pckbd use a unique name Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 10/11] vl: add a new -vmstate-dump option to write a VMState JSON schema Anthony Liguori
2011-03-23  0:16 ` [Qemu-devel] [PATCH 11/11] test-vmstate: add test case to verify we don't change VMState Anthony Liguori
2011-03-23  2:31   ` Anthony Liguori
2011-03-23  8:37   ` Stefan Hajnoczi
2011-03-23 10:22   ` Peter Maydell
2011-03-23 12:42     ` Anthony Liguori
2011-03-23 14:17       ` [Qemu-devel] " Juan Quintela
2011-03-23 14:52         ` Anthony Liguori
2011-03-23 15:00           ` Peter Maydell
2011-03-23 15:06             ` Jan Kiszka
2011-03-23 16:27             ` Anthony Liguori
2011-03-23 16:36               ` Jan Kiszka
2011-03-23 18:42                 ` Anthony Liguori
2011-03-23 16:45               ` Peter Maydell
2011-03-23 17:01                 ` Anthony Liguori
2011-03-23 15:26           ` Juan Quintela
2011-03-23 16:14             ` Anthony Liguori
2011-03-23 16:44               ` Juan Quintela
2011-03-23 14:19     ` Juan Quintela
2011-03-23 14:36       ` Peter Maydell
2011-03-23 15:13         ` Juan Quintela [this message]
2011-03-23 15:24           ` Peter Maydell

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=m3sjudq39d.fsf@neno.mitica \
    --to=quintela@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).