1. 09 4月, 2013 1 次提交
    • P
      hw: move headers to include/ · 0d09e41a
      Paolo Bonzini 提交于
      Many of these should be cleaned up with proper qdev-/QOM-ification.
      Right now there are many catch-all headers in include/hw/ARCH depending
      on cpu.h, and this makes it necessary to compile these files per-target.
      However, fixing this does not belong in these patches.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      0d09e41a
  2. 19 3月, 2013 1 次提交
  3. 01 3月, 2013 3 次提交
  4. 08 2月, 2013 1 次提交
  5. 02 2月, 2013 2 次提交
  6. 22 1月, 2013 1 次提交
  7. 08 1月, 2013 2 次提交
  8. 20 12月, 2012 1 次提交
  9. 19 12月, 2012 3 次提交
  10. 30 11月, 2012 1 次提交
  11. 16 11月, 2012 1 次提交
  12. 23 10月, 2012 1 次提交
    • A
      Rename target_phys_addr_t to hwaddr · a8170e5e
      Avi Kivity 提交于
      target_phys_addr_t is unwieldly, violates the C standard (_t suffixes are
      reserved) and its purpose doesn't match the name (most target_phys_addr_t
      addresses are not target specific).  Replace it with a finger-friendly,
      standards conformant hwaddr.
      
      Outstanding patchsets can be fixed up with the command
      
        git rebase -i --exec 'find -name "*.[ch]"
                              | xargs s/target_phys_addr_t/hwaddr/g' origin
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      a8170e5e
  13. 28 9月, 2012 1 次提交
    • A
      virtio: Introduce virtqueue_get_avail_bytes() · 0d8d7690
      Amit Shah 提交于
      The current virtqueue_avail_bytes() is oddly named, and checks if a
      particular number of bytes are available in a vq.  A better API is to
      fetch the number of bytes available in the vq, and let the caller do
      what's interesting with the numbers.
      
      Introduce virtqueue_get_avail_bytes(), which returns the number of bytes
      for buffers marked for both, in as well as out.  virtqueue_avail_bytes()
      is made a wrapper over this new function.
      Signed-off-by: NAmit Shah <amit.shah@redhat.com>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      0d8d7690
  14. 07 8月, 2012 1 次提交
  15. 17 7月, 2012 1 次提交
  16. 12 7月, 2012 2 次提交
  17. 22 5月, 2012 1 次提交
  18. 19 4月, 2012 1 次提交
  19. 22 2月, 2012 1 次提交
  20. 29 11月, 2011 1 次提交
  21. 17 9月, 2011 1 次提交
  22. 12 9月, 2011 1 次提交
  23. 05 8月, 2011 1 次提交
  24. 05 7月, 2011 1 次提交
  25. 12 6月, 2011 1 次提交
  26. 29 3月, 2011 1 次提交
    • M
      virtio-pci: fix bus master work around on load · 89c473fd
      Michael S. Tsirkin 提交于
      Commit c81131db
      detects old guests by comparing virtio and
      PCI status. It attempts to do this on load,
      as well, but load_config callback in a binding
      is invoked too early and so the virtio status
      isn't set yet.
      
      We could add yet another callback to the
      binding, to invoke after load, but it
      seems easier to reuse the existing vmstate
      callback.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      Cc: Alexander Graf <agraf@suse.de>
      89c473fd
  27. 21 3月, 2011 1 次提交
  28. 02 2月, 2011 1 次提交
  29. 10 1月, 2011 2 次提交
    • S
      virtio-pci: Use ioeventfd for virtqueue notify · 25db9ebe
      Stefan Hajnoczi 提交于
      Virtqueue notify is currently handled synchronously in userspace virtio.  This
      prevents the vcpu from executing guest code while hardware emulation code
      handles the notify.
      
      On systems that support KVM, the ioeventfd mechanism can be used to make
      virtqueue notify a lightweight exit by deferring hardware emulation to the
      iothread and allowing the VM to continue execution.  This model is similar to
      how vhost receives virtqueue notifies.
      
      The result of this change is improved performance for userspace virtio devices.
      Virtio-blk throughput increases especially for multithreaded scenarios and
      virtio-net transmit throughput increases substantially.
      
      Some virtio devices are known to have guest drivers which expect a notify to be
      processed synchronously and spin waiting for completion.
      For virtio-net, this also seems to interact with the guest stack in strange
      ways so that TCP throughput for small message sizes (~200bytes)
      is harmed. Only enable ioeventfd for virtio-blk for now.
      
      Care must be taken not to interfere with vhost-net, which uses host
      notifiers.  If the set_host_notifier() API is used by a device
      virtio-pci will disable virtio-ioeventfd and let the device deal with
      host notifiers as it wishes.
      
      Finally, there used to be a limit of 6 KVM io bus devices inside the
      kernel.  On such a kernel, don't use ioeventfd for virtqueue host
      notification since the limit is reached too easily.  This ensures that
      existing vhost-net setups (which always use ioeventfd) have ioeventfds
      available so they can continue to work.
      
      After migration and on VM change state (running/paused) virtio-ioeventfd
      will enable/disable itself.
      
       * VIRTIO_CONFIG_S_DRIVER_OK -> enable virtio-ioeventfd
       * !VIRTIO_CONFIG_S_DRIVER_OK -> disable virtio-ioeventfd
       * virtio_pci_set_host_notifier() -> disable virtio-ioeventfd
       * vm_change_state(running=0) -> disable virtio-ioeventfd
       * vm_change_state(running=1) -> enable virtio-ioeventfd
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      25db9ebe
    • M
      virtio: move vmstate change tracking to core · 85cf2a8d
      Michael S. Tsirkin 提交于
      Move tracking vmstate change from virtio-net to virtio.c
      as it is going to be used by virito-blk and virtio-pci
      for the ioeventfd support.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      85cf2a8d
  30. 07 10月, 2010 1 次提交
  31. 08 9月, 2010 1 次提交
  32. 31 8月, 2010 1 次提交
新手
引导
客服 返回
顶部