Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 23 6月, 2015 1 次提交
    • G
      virtio-input: move properties, use virtio_instance_init_common · 6f2b9a5b
      由 Gerd Hoffmann 提交于 
      Move properties from virtio-*-pci to virtio-*-device.
Also make better use of QOM and attach common properties
to the abstract parent classes (virtio-input-device and
virtio-input-pci-device).

Switch the hid device instance init functions over to use
virtio_instance_init_common, so we get the properties of the
virtio device aliased properly to the virtio pci proxy.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      6f2b9a5b
  3. 19 6月, 2015 1 次提交
  5. 17 6月, 2015 1 次提交
  7. 11 6月, 2015 13 次提交
  9. 10 6月, 2015 1 次提交
  11. 04 6月, 2015 2 次提交
    • 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
    • G
      virtio: 64bit features fixups. · d5aaa1b0
      由 Gerd Hoffmann 提交于 
      Commit "019a3edb virtio: make features 64bit wide" missed a few changes,
as I've noticed while trying to rebase the virtio-1 branch to latest
master.  This patch adds them.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
Reviewed-by: NMichael S. Tsirkin <mst@redhat.com>
Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      d5aaa1b0
  13. 02 6月, 2015 2 次提交
  15. 01 6月, 2015 1 次提交
  17. 31 5月, 2015 6 次提交
  19. 29 5月, 2015 2 次提交
    • G
      virtio-input: emulated devices [device] · 55a1d80a
      由 Gerd Hoffmann 提交于 
      This patch adds the virtio-input-hid base class and
virtio-{keyboard,mouse,tablet} subclasses building on the base class.
They are hooked up to the qemu input core and deliver input events
to the guest like all other hid devices (ps/2 kbd, usb tablet, ...).

Using them is as simple as adding "-device virtio-tablet-device" to
your command line, for use all transports except pci.  virtio-pci
support comes as separate patch, once virtio-pci got virtio 1.0
support.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      55a1d80a
    • G
      virtio-input: core code & base class [device] · f73ddbad
      由 Gerd Hoffmann 提交于 
      This patch adds virtio-input support to qemu.  It brings a abstract
base class providing core support, other classes can build on it to
actually implement input devices.

virtio-input basically sends linux input layer events (evdev) over
virtio.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      f73ddbad
  21. 28 4月, 2015 4 次提交
  23. 08 4月, 2015 1 次提交
  25. 04 4月, 2015 1 次提交
  27. 19 3月, 2015 1 次提交
    • A
      virtio: serial: expose a 'guest_writable' callback for users · 4add73aa
      由 Amit Shah 提交于 
      Users of virtio-serial may want to know when a port becomes writable.  A
port can stop accepting writes if the guest port is open but not being
read from.  In this case, data gets queued up in the virtqueue, and
after the vq is full, writes to the port do not succeed.

When the guest reads off a vq element, and adds a new one for the host
to put data in, we can tell users the port is available for more writes,
via the new ->guest_writable() callback.
Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
Signed-off-by: NAmit Shah <amit.shah@redhat.com>
      4add73aa
  29. 12 3月, 2015 3 次提交