qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 0/8] virtio, vhost: fixes, features
Date: Fri, 2 Jun 2017 19:34:28 +0300	[thread overview]
Message-ID: <1496421247-857-1-git-send-email-mst@redhat.com> (raw)

The following changes since commit d47a851caeda96d5979bf48d4bae6a87784ad91d:

  Merge remote-tracking branch 'remotes/juanquintela/tags/migration/20170601' into staging (2017-06-02 14:07:53 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream

for you to fetch changes up to 6dcdd06e3b0d0c5651219013ec975348e2050041:

  spec/vhost-user spec: Add IOMMU support (2017-06-02 18:57:17 +0300)

----------------------------------------------------------------
virtio, vhost: fixes, features

IOTLB support in vhost-user.
A bunch of fixes all over the place.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

----------------------------------------------------------------
Ladi Prosek (1):
      virtio-serial-bus: Unset hotplug handler when unrealize

Marc-André Lureau (2):
      vhost-user: add vhost_user to hold the chr
      vhost-user: add slave-req-fd support

Maxime Coquelin (3):
      vhost: propagate errors in vhost_device_iotlb_miss()
      vhost: rework IOTLB messaging
      spec/vhost-user spec: Add IOMMU support

Paolo Bonzini (1):
      virtio: add virtqueue_alloc_element tracepoint

Stefan Hajnoczi (1):
      virtio-serial: fix segfault on disconnect

 docs/specs/vhost-user.txt         | 116 ++++++++++++++++++++++-
 include/hw/virtio/vhost-backend.h |  23 +++--
 include/hw/virtio/vhost.h         |   2 +-
 hw/char/virtio-serial-bus.c       |   6 ++
 hw/net/vhost_net.c                |   1 +
 hw/virtio/vhost-backend.c         | 130 ++++++++++++++-----------
 hw/virtio/vhost-user.c            | 194 ++++++++++++++++++++++++++++++++++++--
 hw/virtio/vhost.c                 |  19 ++--
 hw/virtio/virtio.c                |   1 +
 hw/virtio/trace-events            |   1 +
 10 files changed, 412 insertions(+), 81 deletions(-)

             reply	other threads:[~2017-06-02 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 16:34 Michael S. Tsirkin [this message]
2017-06-02 16:34 ` [Qemu-devel] [PULL 1/8] virtio-serial-bus: Unset hotplug handler when unrealize Michael S. Tsirkin
2017-06-02 16:34 ` [Qemu-devel] [PULL 2/8] virtio: add virtqueue_alloc_element tracepoint Michael S. Tsirkin
2017-06-02 16:34 ` [Qemu-devel] [PULL 3/8] virtio-serial: fix segfault on disconnect Michael S. Tsirkin
2017-06-02 16:34 ` [Qemu-devel] [PULL 4/8] vhost: propagate errors in vhost_device_iotlb_miss() Michael S. Tsirkin
2017-06-02 16:34 ` [Qemu-devel] [PULL 5/8] vhost: rework IOTLB messaging Michael S. Tsirkin
2017-06-02 16:34 ` [Qemu-devel] [PULL 6/8] vhost-user: add vhost_user to hold the chr Michael S. Tsirkin
2017-06-02 16:34 ` [Qemu-devel] [PULL 7/8] vhost-user: add slave-req-fd support Michael S. Tsirkin
2017-06-02 16:34 ` [Qemu-devel] [PULL 8/8] spec/vhost-user spec: Add IOMMU support Michael S. Tsirkin
2017-06-02 17:36 ` [Qemu-devel] [PULL 0/8] virtio, vhost: fixes, features Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1496421247-857-1-git-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).