qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Cam Macdonell <cam@cs.ualberta.ca>,
	qemu-devel <qemu-devel@nongnu.org>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vmstate: Add unmigratable flag
Date: Thu, 09 Jun 2011 22:39:44 +0200	[thread overview]
Message-ID: <4DF12F90.8000106@web.de> (raw)
In-Reply-To: <4DF12642.1050707@codemonkey.ws>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

On 2011-06-09 22:00, Anthony Liguori wrote:
> On 06/09/2011 11:44 AM, Jan Kiszka wrote:
>> A first step towards getting rid of register_device_unmigratable
>> (ivshmem and lacking vmstate support in virtio are blocking this):
>>
>> Allow to register an unmigratable vmstate via qdev, i.e. tag a device
>> declaratively.
> 
> I thought part of the problem with this was that for some devices (like
> ivshmem), whether it can be migrated was dynamic.  It depends on
> configuration, state, etc.

That only applies to ivshmem (the other user is device assignment which
is unconditionally unmigratable). And the ivshmem issue could easily be
solved by defining two devices, ivshmem-peer (or just ivshmem) and
ivshmem-master, eliminating the need for the role property.

I don't think there will ever be a use case for a "transformer" device
that becomes unmigratable during runtime (would be a nightmare for
management apps anyway).

If breaking the user interface of ivshmem for this is OK, I'll post a patch.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-06-09 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 16:44 [Qemu-devel] [PATCH] vmstate: Add unmigratable flag Jan Kiszka
2011-06-09 18:27 ` Markus Armbruster
2011-06-09 20:00 ` Anthony Liguori
2011-06-09 20:39   ` Jan Kiszka [this message]
2011-06-19 20:46     ` Cam Macdonell
2011-06-20  9:05       ` Jan Kiszka
2011-06-21 20:25         ` Cam Macdonell
2011-06-21 20:29           ` Jan Kiszka

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=4DF12F90.8000106@web.de \
    --to=jan.kiszka@web.de \
    --cc=anthony@codemonkey.ws \
    --cc=cam@cs.ualberta.ca \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).