Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

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

切换分支/标签
  1. 15 3月, 2013 4 次提交
  3. 04 3月, 2013 1 次提交
  5. 23 2月, 2013 4 次提交
  7. 01 2月, 2013 1 次提交
  9. 26 1月, 2013 4 次提交
  11. 15 1月, 2013 2 次提交
    • P
      block: clear dirty bitmap when discarding · df702c9b
      由 Paolo Bonzini 提交于 
      Note that resetting bits in the dirty bitmap is done _before_ actually
processing the request.  Writes, instead, set bits after the request
is completed.

This way, when there are concurrent write and discard requests, the
outcome will always be that the blocks are marked dirty.  This scenario
should never happen, but it is safer to do it this way.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      df702c9b
    • P
      block: fix initialization in bdrv_io_limits_enable() · 029d091e
      由 Peter Lieven 提交于 
      bdrv_io_limits_enable() starts a new slice, but does not set io_base
correctly for that slice.

Here is how io_base is used:

    bytes_base  = bs->nr_bytes[is_write] - bs->io_base.bytes[is_write];
    bytes_res   = (unsigned) nb_sectors * BDRV_SECTOR_SIZE;

    if (bytes_base + bytes_res <= bytes_limit) {
        /* no wait */
    } else {
        /* operation needs to be throttled */
    }

As a result, any I/O operations that are triggered between now and
bs->slice_end are incorrectly limited.  If 10 MB of data has been
written since the VM was started, QEMU thinks that 10 MB of data has
been written in this slice. This leads to a I/O lockup in the guest.

We fix this by delaying the start of a new slice to the next
call of bdrv_exceed_io_limits().
Signed-off-by: NPeter Lieven <pl@kamp.de>
Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      029d091e
  13. 14 1月, 2013 2 次提交
  15. 11 1月, 2013 1 次提交
  17. 19 12月, 2012 5 次提交
  19. 12 12月, 2012 1 次提交
    • K
      qemu-io: Add AIO debugging commands · 41c695c7
      由 Kevin Wolf 提交于 
      This makes the blkdebug suspend/resume functionality available in
qemu-io. Use it like this:

  $ ./qemu-io blkdebug::/tmp/test.qcow2
  qemu-io> break write_aio req_a
  qemu-io> aio_write 0 4k
  qemu-io> blkdebug: Suspended request 'req_a'
  qemu-io> resume req_a
  blkdebug: Resuming request 'req_a'
  qemu-io> wrote 4096/4096 bytes at offset 0
  4 KiB, 1 ops; 0:00:30.71 (133.359788 bytes/sec and 0.0326 ops/sec)
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      41c695c7
  21. 11 12月, 2012 5 次提交
  23. 25 11月, 2012 1 次提交
  25. 15 11月, 2012 2 次提交
  27. 24 10月, 2012 7 次提交