Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 12 11月, 2015 1 次提交
  3. 22 10月, 2015 10 次提交
  5. 24 9月, 2015 2 次提交
  7. 10 9月, 2015 1 次提交
  9. 23 6月, 2015 1 次提交
  11. 19 6月, 2015 1 次提交
  13. 17 6月, 2015 1 次提交
  15. 11 6月, 2015 1 次提交
  17. 10 6月, 2015 1 次提交
  19. 05 6月, 2015 2 次提交
    • P
      memory: prepare for multiple bits in the dirty log mask · b2dfd71c
      由 Paolo Bonzini 提交于 
      When the dirty log mask will also cover other bits than DIRTY_MEMORY_VGA,
some listeners may be interested in the overall zero/non-zero value of
the dirty log mask; others may be interested in the value of single bits.

For this reason, always call log_start/log_stop if bits have respectively
appeared or disappeared, and pass the old and new values of the dirty log
mask so that listeners can distinguish the kinds of change.

For example, KVM checks if dirty logging used to be completely disabled
(in log_start) or is now completely disabled (in log_stop).  On the
other hand, Xen has to check manually if DIRTY_MEMORY_VGA changed,
since that is the only bit it cares about.
Reviewed-by: NFam Zheng <famz@redhat.com>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      b2dfd71c
    • P
      memory: differentiate memory_region_is_logging and memory_region_get_dirty_log_mask · 2d1a35be
      由 Paolo Bonzini 提交于 
      For now memory regions only track DIRTY_MEMORY_VGA individually, but
this will change soon.  To support this, split memory_region_is_logging
in two functions: one that returns a given bit from dirty_log_mask,
and one that returns the entire mask.  memory_region_is_logging gets an
extra parameter so that the compiler flags misuse.

While VGA-specific users (including the Xen listener!) will want to keep
checking that bit, KVM and vhost check for "any bit except migration"
(because migration is handled via the global start/stop listener
callbacks).
Reviewed-by: NFam Zheng <famz@redhat.com>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      2d1a35be
  21. 04 6月, 2015 1 次提交
    • J
      vhost: logs sharing · 309750fa
      由 Jason Wang 提交于 
      Currently we allocate one vhost log per vhost device. This is sub
optimal when:

- Guest has several device with vhost as backend
- Guest has multiqueue devices

In the above cases, we can avoid the memory allocation by sharing a
single vhost log among all the vhost devices. This is done through:

- Introducing a new vhost_log structure with refcnt inside.
- Using a global pointer to vhost_log structure that will be used. And
  introduce helper to get the log with expected log size and helper to
- drop the refcnt to the old log.
- Each vhost device still keep track of a pointer to the log that was
  used.

With above, if no resize happens, all vhost device will share a single
vhost log. During resize, a new vhost_log structure will be allocated
and made for the global pointer. And each vhost devices will drop the
refcnt to the old log.

Tested by doing scp during migration for a 2 queues virtio-net-pci.

Cc: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: NJason Wang <jasowang@redhat.com>
Reviewed-by: NMichael S. Tsirkin <mst@redhat.com>
Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      309750fa
  23. 20 4月, 2015 1 次提交
  25. 01 12月, 2014 1 次提交
  27. 04 9月, 2014 1 次提交
  29. 03 9月, 2014 1 次提交
  31. 02 9月, 2014 1 次提交
  33. 23 6月, 2014 2 次提交
  35. 19 6月, 2014 5 次提交
  37. 11 6月, 2014 1 次提交
  39. 12 8月, 2013 1 次提交
    • M
      vhost: clear signalled_used_valid on vhost stop · 3561ba14
      由 Michael S. Tsirkin 提交于 
      When vhost device stops, its implementation synchronizes kernel state
back to virtio.c so we can continue emulating the device
in userspace.

This patch ensures that virtio.c's signalled_used_valid flag is reset so
that userspace does not suppress guest notifications due to stale
signalled_used values.

Cc: qemu-stable@nongnu.org
Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      3561ba14
  41. 04 7月, 2013 2 次提交
  43. 20 6月, 2013 1 次提交
    • P
      memory: make section size a 128-bit integer · 052e87b0
      由 Paolo Bonzini 提交于 
      So far, the size of all regions passed to listeners could fit in 64 bits,
because artificial regions (containers and aliases) are eliminated by
the memory core, leaving only device regions which have reasonable sizes

An IOMMU however cannot be eliminated by the memory core, and may have
an artificial size, hence we may need 65 bits to represent its size.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      052e87b0
  45. 25 4月, 2013 1 次提交