1. 21 11月, 2012 1 次提交
  2. 15 11月, 2012 1 次提交
  3. 24 9月, 2012 1 次提交
  4. 15 6月, 2012 1 次提交
  5. 12 6月, 2012 2 次提交
    • M
      change qemu_iovec_to_buf() to match other to,from_buf functions · d5e6b161
      Michael Tokarev 提交于
      It now allows specifying offset within qiov to start from and
      amount of bytes to copy.  Actual implementation is just a call
      to iov_to_buf().
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      d5e6b161
    • M
      allow qemu_iovec_from_buffer() to specify offset from which to start copying · 03396148
      Michael Tokarev 提交于
      Similar to
       qemu_iovec_memset(QEMUIOVector *qiov, size_t offset,
                         int c, size_t bytes);
      the new prototype is:
       qemu_iovec_from_buf(QEMUIOVector *qiov, size_t offset,
                           const void *buf, size_t bytes);
      
      The processing starts at offset bytes within qiov.
      
      This way, we may copy a bounce buffer directly to
      a middle of qiov.
      
      This is exactly the same function as iov_from_buf() from
      iov.c, so use the existing implementation and rename it
      to qemu_iovec_from_buf() to be shorter and to match the
      utility function.
      
      As with utility implementation, we now assert that the
      offset is inside actual iovec.  Nothing changed for
      current callers, because `offset' parameter is new.
      
      While at it, stop using "bounce-qiov" in block/qcow2.c
      and copy decrypted data directly from cluster_data
      instead of recreating a temp qiov for doing that.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      03396148
  6. 03 5月, 2012 1 次提交
  7. 19 4月, 2012 1 次提交
  8. 26 1月, 2012 1 次提交
  9. 14 1月, 2012 1 次提交
  10. 15 12月, 2011 2 次提交
  11. 11 11月, 2011 1 次提交
  12. 21 10月, 2011 1 次提交
  13. 20 9月, 2011 4 次提交
  14. 12 9月, 2011 3 次提交
  15. 21 8月, 2011 1 次提交
  16. 14 6月, 2011 1 次提交
  17. 08 6月, 2011 4 次提交
  18. 14 12月, 2010 1 次提交