Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 26 3月, 2018 4 次提交
  3. 19 3月, 2018 1 次提交
  5. 14 3月, 2018 4 次提交
  7. 09 3月, 2018 2 次提交
  9. 26 1月, 2018 1 次提交
  11. 23 1月, 2018 2 次提交
  13. 19 12月, 2017 2 次提交
  15. 22 11月, 2017 1 次提交
  17. 18 11月, 2017 1 次提交
  19. 17 11月, 2017 1 次提交
  21. 26 10月, 2017 1 次提交
  23. 06 10月, 2017 2 次提交
    • E
      iotests: Add test 197 for covering copy-on-read · 46174339
      由 Eric Blake 提交于 
      Add a test for qcow2 copy-on-read behavior, including exposure
for the just-fixed bugs.

The copy-on-read behavior is always to a qcow2 image, but the
test is careful to allow running with most image protocol/format
combos as the backing file being copied from (luks being the
exception, as it is harder to pass the right secret to all the
right places).  In fact, for './check nbd', this appears to be
the first time we've had a qcow2 image wrapping NBD, requiring
an additional line in _filter_img_create to match the similar
line in _filter_img_info.

Invoking blkdebug to prove we don't write too much took some
effort to get working; and it requires that $TEST_WRAP (based
on $TEST_DIR) not be subject to word splitting.  We may decide
later to have the entire iotests suite use relative rather than
absolute names, to avoid problems inherited by the absolute
name of $PWD or $TEST_DIR, at which point the sanity check in
this commit could be simplified.

This test requires at least 2G of consecutive memory to succeed;
as such, it is prone to spurious failures, particularly on
32-bit machines under load.  This situation is detected and
triggers an early exit to skip the test, rather than a failure.
To manually provoke this setup on a beefier machine, I used:
  $ (ulimit -S -v 1000000; ./check -qcow2 197)
Signed-off-by: NEric Blake <eblake@redhat.com>
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      46174339
    • K
      qemu-iotests: Test commit block job where top has two parents · 7c61a4a3
      由 Kevin Wolf 提交于 
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      7c61a4a3
  25. 26 9月, 2017 2 次提交
  27. 06 9月, 2017 1 次提交
  29. 23 8月, 2017 1 次提交
  31. 15 8月, 2017 1 次提交
  33. 08 8月, 2017 1 次提交
  35. 02 8月, 2017 1 次提交
  37. 24 7月, 2017 1 次提交
  39. 18 7月, 2017 1 次提交
  41. 11 7月, 2017 6 次提交
  43. 26 6月, 2017 1 次提交
  45. 09 6月, 2017 1 次提交
  47. 11 5月, 2017 1 次提交
    • E
      iotests: Add test 179 to cover write zeroes with unmap · e249d519
      由 Eric Blake 提交于 
      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: NEric Blake <eblake@redhat.com>
Reviewed-by: NMax Reitz <mreitz@redhat.com>
Message-id: 20170507000552.20847-10-eblake@redhat.com
Signed-off-by: NMax Reitz <mreitz@redhat.com>
      e249d519