All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] vmstate: add no_migrate flag to	VMStateDescription
Date: Fri, 08 Jul 2011 17:44:46 +0200	[thread overview]
Message-ID: <4E1725EE.4080603@redhat.com> (raw)
In-Reply-To: <4E17137A.1010308@codemonkey.ws>

On 07/08/11 16:26, Anthony Liguori wrote:
> On 07/08/2011 03:53 AM, Gerd Hoffmann wrote:
>> This allows to easily tag devices as non-migratable,
>> so any attempt to migrate a virtual machine with the
>> device in question active will make migration fail.
>>
>> Signed-off-by: Gerd Hoffmann<kraxel@redhat.com>
>
> register_device_unmigratable()?

That is just a more complicated way to do the same ;)
Wanna have a patch to zap it?

cheers,
   Gerd

  reply	other threads:[~2011-07-08 15:44 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 [this message]
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 ` [Qemu-devel] [PATCH 0/3] non-migratable devices Paolo Bonzini
2011-07-08  9:59   ` 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=4E1725EE.4080603@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.