From: Stefano Garzarella <sgarzare@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Jiang Wang" <jiang.wang@bytedance.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Arseny Krasnov" <arseny.krasnov@kaspersky.com>
Subject: [PATCH v2 0/2] vhost-vsock: fixes for seqpacket support
Date: Tue, 21 Sep 2021 18:16:40 +0200 [thread overview]
Message-ID: <20210921161642.206461-1-sgarzare@redhat.com> (raw)
This series includes 2 patches: the first is similar of v1, but using
OnOffAuto property.
The second patch moves the `seqpacket` handling in the vhost-vsock-common
class to reuse the same code/properties also in vhost-user-vsock devices.
Perhaps the patches can be merged into a single one, but to simplify the
backport I left them separate.
v1: https://lore.kernel.org/qemu-devel/20210907124935.147164-1-sgarzare@redhat.com/
v2:
- used OnOffAuto `seqpacket` property instead of boolean `features` [stefanha]
- moved `seqpacket` property to vhost-vsock-common class
Stefano Garzarella (2):
vhost-vsock: fix migration issue when seqpacket is supported
vhost-vsock: handle common features in vhost-vsock-common
include/hw/virtio/vhost-vsock-common.h | 5 +++++
hw/core/machine.c | 5 ++++-
hw/virtio/vhost-user-vsock.c | 4 +++-
hw/virtio/vhost-vsock-common.c | 31 ++++++++++++++++++++++++++
hw/virtio/vhost-vsock.c | 11 +--------
5 files changed, 44 insertions(+), 12 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-21 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 16:16 Stefano Garzarella [this message]
2021-09-21 16:16 ` [PATCH v2 1/2] vhost-vsock: fix migration issue when seqpacket is supported Stefano Garzarella
2021-09-21 16:16 ` [PATCH v2 2/2] vhost-vsock: handle common features in vhost-vsock-common Stefano Garzarella
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=20210921161642.206461-1-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=arseny.krasnov@kaspersky.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jiang.wang@bytedance.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).