aboutsummaryrefslogtreecommitdiff
path: root/tests/qemu-iotests/154
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2017-05-06 19:05:49 -0500
committerMax Reitz <mreitz@redhat.com>2017-05-11 14:28:07 +0200
commite249d5195279cfadb7f15e2ad55dd4fe1d67c105 (patch)
tree53c85c4676418ad50873a7f9b6c40c0248e8b2dc /tests/qemu-iotests/154
parentd9ca2214bd058cfb4371b8373123c0444e4a5ac8 (diff)
downloadqemu-e249d5195279cfadb7f15e2ad55dd4fe1d67c105.zip
qemu-e249d5195279cfadb7f15e2ad55dd4fe1d67c105.tar.gz
qemu-e249d5195279cfadb7f15e2ad55dd4fe1d67c105.tar.bz2
iotests: Add test 179 to cover write zeroes with unmap
No tests were covering write zeroes with unmap. Additionally, I needed to prove that my previous patches for correct status reporting and write zeroes optimizations actually had an impact. The test works for cluster_size between 8k and 2M (for smaller sizes, it fails because our allocation patterns are not contiguous with small clusters - in part, the largest consecutive allocation we tend to get is often bounded by the size covered by one L2 table). Note that testing for zero clusters is tricky: 'qemu-io map' reports whether data comes from the current layer of the image (useful for sniffing out which regions of the file have QCOW_OFLAG_ZERO) - but doesn't show which clusters have mappings; while 'qemu-img map' sees "zero":true for both unallocated and zero clusters for any qcow2 with no backing layer (so less useful at detecting true zero clusters), but reliably shows mappings. So we have to rely on both queries side-by-side at each point of the test. Signed-off-by: Eric Blake <eblake@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com> Message-id: 20170507000552.20847-10-eblake@redhat.com Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/154')
0 files changed, 0 insertions, 0 deletions