1. 30 1月, 2013 3 次提交
  2. 08 1月, 2013 2 次提交
  3. 19 12月, 2012 2 次提交
  4. 30 10月, 2012 10 次提交
  5. 18 10月, 2012 1 次提交
  6. 08 10月, 2012 1 次提交
  7. 28 9月, 2012 1 次提交
  8. 14 9月, 2012 1 次提交
  9. 01 8月, 2012 2 次提交
  10. 23 7月, 2012 1 次提交
  11. 08 6月, 2012 1 次提交
    • M
      change iov_* function prototypes to be more appropriate · dcf6f5e1
      Michael Tokarev 提交于
      Reorder arguments to be more natural, readable and
      consistent with other iov_* functions, and change
      argument names, from:
       iov_from_buf(iov, iov_cnt, buf, iov_off, size)
      to
       iov_from_buf(iov, iov_cnt, offset, buf, bytes)
      
      The result becomes natural English:
      
       copy data to this `iov' vector with `iov_cnt'
       elements starting at byte offset `offset'
       from memory buffer `buf', processing `bytes'
       bytes max.
      
      (Try to read the original prototype this way).
      
      Also change iov_clear() to more general iov_memset()
      (it uses memset() internally anyway).
      
      While at it, add comments to the header file
      describing what the routines actually does.
      
      The patch only renames argumens in the header, but
      keeps old names in the implementation.  The next
      patch will touch actual code to match.
      
      Now, it might look wrong to pay so much attention
      to so small things.  But we've so many badly designed
      interfaces already so the whole thing becomes rather
      confusing or error prone.  One example of this is
      previous commit and small discussion which emerged
      from it, with an outcome that the utility functions
      like these aren't well-understdandable, leading to
      strange usage cases.  That's why I paid quite some
      attention to this set of functions and a few
      others in subsequent patches.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      dcf6f5e1
  12. 22 5月, 2012 1 次提交
  13. 28 1月, 2012 2 次提交
  14. 21 8月, 2011 1 次提交
  15. 28 7月, 2011 1 次提交
  16. 18 7月, 2011 1 次提交
  17. 21 3月, 2011 1 次提交
    • P
      change all other clock references to use nanosecond resolution accessors · 74475455
      Paolo Bonzini 提交于
      This was done with:
      
          sed -i 's/qemu_get_clock\>/qemu_get_clock_ns/' \
              $(git grep -l 'qemu_get_clock\>' )
          sed -i 's/qemu_new_timer\>/qemu_new_timer_ns/' \
              $(git grep -l 'qemu_new_timer\>' )
      
      after checking that get_clock and new_timer never occur twice
      on the same line.  There were no missed occurrences; however, even
      if there had been, they would have been caught by the compiler.
      
      There was exactly one false positive in qemu_run_timers:
      
           -    current_time = qemu_get_clock (clock);
           +    current_time = qemu_get_clock_ns (clock);
      
      which is of course not in this patch.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      74475455
  18. 04 3月, 2011 1 次提交
  19. 21 2月, 2011 1 次提交
  20. 02 2月, 2011 1 次提交
  21. 29 1月, 2011 1 次提交
    • A
      virtio-net: fix cross-endianness support · 44b15bc5
      Aurelien Jarno 提交于
      virtio-net used to work on cross-endianness configurations, but doesn't
      anymore with recent guest kernels, as the new features don't handle
      endianness correctly.
      
      This patch fixes wrong conversion, and add missing ones to make
      virtio-net working. Tested on the following configurations:
      - i386 guest on x86_64 host
      - ppc guest on x86_64 host
      - i386 guest on mips host
      - ppc guest on mips host
      
      Cc: Anthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      44b15bc5
  22. 10 1月, 2011 1 次提交
  23. 12 12月, 2010 1 次提交
  24. 09 12月, 2010 2 次提交