From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:48024) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QUm1a-0004S4-JO for qemu-devel@nongnu.org; Thu, 09 Jun 2011 16:40:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QUm1Z-00080D-E1 for qemu-devel@nongnu.org; Thu, 09 Jun 2011 16:40:18 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:43971) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QUm1Z-000809-1o for qemu-devel@nongnu.org; Thu, 09 Jun 2011 16:40:17 -0400 Message-ID: <4DF12F90.8000106@web.de> Date: Thu, 09 Jun 2011 22:39:44 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4DF0F86E.8040307@siemens.com> <4DF12642.1050707@codemonkey.ws> In-Reply-To: <4DF12642.1050707@codemonkey.ws> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9A7902D586255FF4D52D2A9B" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] [PATCH] vmstate: Add unmigratable flag List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Cam Macdonell , qemu-devel , Juan Quintela This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9A7902D586255FF4D52D2A9B Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable 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. >=20 > 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 pat= ch. Jan --------------enig9A7902D586255FF4D52D2A9B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3xL5AACgkQitSsb3rl5xTe3gCdFlK8q8p6Ho8Jiwxrmn7HaVQ0 bYUAn2BQB/C+S64YCXxG7fg2GB6oOiV/ =9yEm -----END PGP SIGNATURE----- --------------enig9A7902D586255FF4D52D2A9B--