From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56062) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c44E8-0003Hw-3L for qemu-devel@nongnu.org; Tue, 08 Nov 2016 06:06:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c44E4-0004Kt-7O for qemu-devel@nongnu.org; Tue, 08 Nov 2016 06:06:04 -0500 Date: Tue, 8 Nov 2016 12:05:50 +0100 From: Kevin Wolf Message-ID: <20161108110550.GC5088@noname.str.redhat.com> References: <9e317525-b862-220f-258c-da59428d19d4@virtuozzo.com> <5dd4ca77-5cc8-2bce-fffa-564503c30280@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <5dd4ca77-5cc8-2bce-fffa-564503c30280@redhat.com> Subject: Re: [Qemu-devel] BdrvDirtyBitmap and bdrv_snapshot_goto List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: Vladimir Sementsov-Ogievskiy , qemu-devel , qemu block , Fam Zheng , "Denis V. Lunev" , John Snow --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am 07.11.2016 um 17:10 hat Max Reitz geschrieben: > On 07.11.2016 16:24, Vladimir Sementsov-Ogievskiy wrote: > > Hi all! > >=20 > > As I can see, in bdrv_snapshot_goto, existing dirty bitmaps are not > > handled.. Is it ok? Should not they be filled with ones or something > > like this? >=20 > Filling them with ones makes sense to me. I guess nobody noticed because > nobody was crazy enough to use block jobs alongside loadvm... What's the use case in which ones make sense? It rather seems to me that an active dirty bitmap and snapshot switching should exclude each other because the bitmap becomes meaningless by the switch. And chances are that after switching a snapshot you don't want to "incrementally" backup everything, but that you should access a different backup. Kevin --9amGYk9869ThD9tj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJYIbGOAAoJEH8JsnLIjy/WeaAP/1rQqlWBQ4anl5uDlXKsAGNw 21JJlC9wD73Pd+DtpJrgGSzmCAyLxkoikzNvGhpKlLx8fkyHxad62DSS3f3bbh4R hZ2X/KhING43ds6hv5b5GUOvvfJEIVgY6pz2o9heZS5aPabRtt6Xf4gsTqBi8BZl 9ussGBeYxBXULbr3yz+xqIMG1TVgttiz4CKUPa8wR65xW/OWVeOpCbjz0hO8zBSg GNYephIy+XLOUU9KufZpa4qBaQidRRRTYTYCRVvcPDjShYBqA+XG3t2QbbX2Hi82 kALwoJldxDH40OsZd75fxU0vkDqW8tX6cySsRNoc7jbOeC5HcYWZBqjDTa1hDLu8 pHZDA20ghYb0CqZPSsPHIK8S0posS/dPfBmX/RYJIzxoyP/mb+SkS+4fCnzgxNxf HagNNIH3dOy+RkWHjAHHs9g6iVWuoZ0uujvXa3TmBuhhW4m3FikQJdnL/IAD6Cuf Tf5xj6phVKq5oIQndTLIyIp3R/SAOAd7/DaXlAUxrFtplblHf10QDtDniM8PMO5z 9Zri/inWEhmCqZo6vsnlZs8B2xuL318BqDLH3oBxWYMGmIeIDlV7ZShda8a11qyO pCeSUnVLQwy5l2W5xhVImiiGUqpDHdwpPtXn8B8mKek3k691MBbhxW2A5ScQn3ak PJmgOnLl6caF+rBlb8eO =a3kG -----END PGP SIGNATURE----- --9amGYk9869ThD9tj--