| commit | 6c98c57af3f4fab85bdf5f01616c91322bd4312a | |
| author | Eric Blake <eblake@redhat.com> | |
| Fri, 21 Jul 2017 18:32:42 +0000 (21 13:32 -0500) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Mon, 24 Jul 2017 13:06:04 +0000 (24 15:06 +0200) | ||
| tree | b2b6304d43d43afc327a4570097e760fa657c8e4 | treesnapshot (tar.gz zip) |
| parent | 88e1f9274522929fc5f9b553df9e68e135d1ef2e | commitdiff |
dirty-bitmap: Report BlockDirtyInfo.count in bytes, as documented
We've been documenting the value in bytes since its introduction
in commit b9a9b3a4 (v1.3), where it was actually reported in bytes.
Commit e4654d2 (v2.0) then removed things from block/qapi.c, in
preparation for a rewrite to a list of dirty sectors in the next
commit 21b5683 in block.c, but the new code mistakenly started
reporting in sectors.
Fixes: https://bugzilla.redhat.com/1441460
CC: qemu-stable@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
We've been documenting the value in bytes since its introduction
in commit b9a9b3a4 (v1.3), where it was actually reported in bytes.
Commit e4654d2 (v2.0) then removed things from block/qapi.c, in
preparation for a rewrite to a list of dirty sectors in the next
commit 21b5683 in block.c, but the new code mistakenly started
reporting in sectors.
Fixes: https://bugzilla.redhat.com/1441460
CC: qemu-stable@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| block/dirty-bitmap.c | diffblobblamehistory |