From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43583) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YRPf4-0006LY-7x for qemu-devel@nongnu.org; Fri, 27 Feb 2015 13:29:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YRPf0-0004gk-8Z for qemu-devel@nongnu.org; Fri, 27 Feb 2015 13:29:18 -0500 Received: from mx1.redhat.com ([209.132.183.28]:33571) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YRPf0-0004gQ-0m for qemu-devel@nongnu.org; Fri, 27 Feb 2015 13:29:14 -0500 Message-ID: <54F0B776.4090001@redhat.com> Date: Fri, 27 Feb 2015 11:29:10 -0700 From: Eric Blake MIME-Version: 1.0 References: <1425057891-29848-1-git-send-email-vsementsov@parallels.com> <1425057891-29848-7-git-send-email-vsementsov@parallels.com> In-Reply-To: <1425057891-29848-7-git-send-email-vsementsov@parallels.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="P4IpnH0PogFt5EwPuMAXcM7xg4ntDufcx" Subject: Re: [Qemu-devel] [PATCH RFC v4 06/13] qapi: add dirty-bitmaps migration capability List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladimir Sementsov-Ogievskiy , qemu-devel@nongnu.org Cc: kwolf@redhat.com, peter.maydell@linaro.org, quintela@redhat.com, dgilbert@redhat.com, stefanha@redhat.com, pbonzini@redhat.com, amit.shah@redhat.com, den@openvz.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --P4IpnH0PogFt5EwPuMAXcM7xg4ntDufcx Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 02/27/2015 10:24 AM, Vladimir Sementsov-Ogievskiy wrote: > Reviewed-by: John Snow > Signed-off-by: Vladimir Sementsov-Ogievskiy > --- > include/migration/migration.h | 1 + > migration/migration.c | 9 +++++++++ > qapi-schema.json | 5 ++++- > 3 files changed, 14 insertions(+), 1 deletion(-) Reviewed-by: Eric Blake > # > +# @dirty-bitmaps: If enabled, QEMU will migrate named dirty bitmaps. (= since 2.3) Just to make sure, this only affects the source side, and does not have to be set on the destination (that is, the destination will automatically handle incoming dirty bitmaps correctly without having to tweak the knob first)? Of course, libvirt will check that the destination advertises the feature before enabling the knob on the source (to avoid the case of the source sending something the destination won't understand). --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --P4IpnH0PogFt5EwPuMAXcM7xg4ntDufcx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJU8Ld2AAoJEKeha0olJ0NqDCIH/A0f5/l7qPrdzGd9nCTI3aL8 WBK18aQFImHwuX3/vQCZ92sW1oPL7xvNfpg2cxz4UvN2y4zKjQRyZg4Psj220kNI f/e0FprphUFjdG9InKUQUq7+lrS9pdQCuK5+0E6ttKWcESFWftsu99OV6UvvHeKD tp13rUQXYSFnFiUe7GlreIOvuLOh17eLr3n7A7cdmNdW8xUzkDR0PZPic4mdB98g uJw/zzpvsI8+kKhmR83b4jVNrNlQ8UfjP48SqYkR7lZJ3DSHR41r9G1KW6+ys/u7 FFQTIMjTycgFGJ9Zs2DsvIas6OiEOzayV69KqwvBwi7hDd4yN4oVNdrrUe0wIVE= =3jyC -----END PGP SIGNATURE----- --P4IpnH0PogFt5EwPuMAXcM7xg4ntDufcx--