All of lore.kernel.org
 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: [PULL 0/5] virtio: regression fix
Date: Thu, 1 Dec 2022 02:38:01 -0500	[thread overview]
Message-ID: <20221201073725.44585-1-mst@redhat.com> (raw)

The following changes since commit b7c61789e653086618d1825858a97b3d9891e822:

  virtio: disable error for out of spec queue-enable (2022-11-22 05:19:00 -0500)

are available in the Git repository at:

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

for you to fetch changes up to 4987e5bf2e9262094fd89d2b8e4d5bd6c4c7312f:

  include/hw: VM state takes precedence in virtio_device_should_start (2022-12-01 02:30:18 -0500)

----------------------------------------------------------------
virtio: regression fix

Fixes regression with migration and vsock, as fixing that
exposes some known issues in vhost user cleanup, this attempts
to fix those as well. More work on vhost user is needed :)

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

----------------------------------------------------------------
Alex Bennée (4):
      tests/qtests: override "force-legacy" for gpio virtio-mmio tests
      hw/virtio: add started_vu status field to vhost-user-gpio
      hw/virtio: generalise CHR_EVENT_CLOSED handling
      include/hw: VM state takes precedence in virtio_device_should_start

Stefano Garzarella (1):
      vhost: enable vrings in vhost_dev_start() for vhost-user devices

 include/hw/virtio/vhost-user-gpio.h | 10 ++++++
 include/hw/virtio/vhost-user.h      | 18 ++++++++++
 include/hw/virtio/vhost.h           |  6 ++--
 include/hw/virtio/virtio.h          | 23 +++++++++---
 backends/cryptodev-vhost.c          |  4 +--
 backends/vhost-user.c               |  4 +--
 hw/block/vhost-user-blk.c           | 45 ++++-------------------
 hw/net/vhost_net.c                  |  8 ++---
 hw/scsi/vhost-scsi-common.c         |  4 +--
 hw/virtio/vhost-user-fs.c           |  4 +--
 hw/virtio/vhost-user-gpio.c         | 30 +++++++++-------
 hw/virtio/vhost-user-i2c.c          |  4 +--
 hw/virtio/vhost-user-rng.c          |  4 +--
 hw/virtio/vhost-user.c              | 71 +++++++++++++++++++++++++++++++++++++
 hw/virtio/vhost-vsock-common.c      |  4 +--
 hw/virtio/vhost.c                   | 44 ++++++++++++++++++++---
 tests/qtest/libqos/virtio-gpio.c    |  3 +-
 hw/virtio/trace-events              |  4 +--
 18 files changed, 207 insertions(+), 83 deletions(-)



             reply	other threads:[~2022-12-01  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  7:38 Michael S. Tsirkin [this message]
2022-12-01  7:38 ` [PULL 1/5] tests/qtests: override "force-legacy" for gpio virtio-mmio tests Michael S. Tsirkin
2022-12-01  7:38 ` [PULL 2/5] vhost: enable vrings in vhost_dev_start() for vhost-user devices Michael S. Tsirkin
2022-12-01  7:38   ` [Virtio-fs] " Michael S. Tsirkin
2022-12-01  7:38 ` [PULL 4/5] hw/virtio: generalise CHR_EVENT_CLOSED handling Michael S. Tsirkin
2022-12-01  7:38 ` [PULL 5/5] include/hw: VM state takes precedence in virtio_device_should_start Michael S. Tsirkin
2022-12-01  7:38 ` [PULL 3/5] hw/virtio: add started_vu status field to vhost-user-gpio Michael S. Tsirkin
2022-12-04 23:46 ` [PULL 0/5] virtio: regression fix Stefan Hajnoczi

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=20221201073725.44585-1-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.