From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] non-migratable devices
Date: Fri, 08 Jul 2011 11:54:32 +0200 [thread overview]
Message-ID: <4E16D3D8.60908@redhat.com> (raw)
In-Reply-To: <1310115239-19288-1-git-send-email-kraxel@redhat.com>
On 07/08/2011 10:53 AM, Gerd Hoffmann wrote:
> Hi,
>
> This patch series adds an easy way to tag devices as non-migratable
> puts it into use for ahci and ehci.
>
> Gerd Hoffmann (3):
> vmstate: add no_migrate flag to VMStateDescription
> ahci doesn't support migration
> ehci doesn't support migration
>
> hw/hw.h | 1 +
> hw/ide/ich.c | 6 ++++++
> hw/usb-ehci.c | 6 ++++++
> savevm.c | 1 +
> 4 files changed, 14 insertions(+), 0 deletions(-)
>
>
>
ACK series
For scsi-cd and other empty-but-generally-migratable devices we should
probably add an empty vmstate, so that any further addition can be done
as subsections.
Paolo
next prev parent reply other threads:[~2011-07-08 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 8:53 [Qemu-devel] [PATCH 0/3] non-migratable devices Gerd Hoffmann
2011-07-08 8:53 ` [Qemu-devel] [PATCH 1/3] vmstate: add no_migrate flag to VMStateDescription Gerd Hoffmann
2011-07-08 14:26 ` Anthony Liguori
2011-07-08 15:44 ` Gerd Hoffmann
2011-07-08 16:04 ` Gerd Hoffmann
2011-07-08 17:07 ` Anthony Liguori
2011-07-11 6:29 ` Gerd Hoffmann
2011-07-08 8:53 ` [Qemu-devel] [PATCH 2/3] ahci doesn't support migration Gerd Hoffmann
2011-07-08 8:53 ` [Qemu-devel] [PATCH 3/3] ehci " Gerd Hoffmann
2011-07-08 9:54 ` Paolo Bonzini [this message]
2011-07-08 9:59 ` [Qemu-devel] [PATCH 0/3] non-migratable devices Gerd Hoffmann
2011-07-08 10:17 ` Paolo Bonzini
2011-07-08 11:47 ` Gerd Hoffmann
2011-07-08 12:05 ` Paolo Bonzini
2011-07-08 12:47 ` Gerd Hoffmann
2011-07-08 12:59 ` Paolo Bonzini
2011-07-08 13:21 ` Gerd Hoffmann
2011-07-08 11:45 ` Markus Armbruster
2011-07-08 13:43 ` [Qemu-devel] [PATCH 4/3] vmstate: complain about devices without vmstate Gerd Hoffmann
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=4E16D3D8.60908@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--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).