Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: virtio-comment@lists.oasis-open.org
Cc: mst@redhat.com, arseny.krasnov@kaspersky.com,
	stefanha@redhat.com, cohuck@redhat.com, jasowang@redhat.com
Subject: Re: [PATCH v11 0/3] virtio-vsock: SOCK_SEQPACKET description
Date: Thu, 13 Jan 2022 14:52:28 +0100	[thread overview]
Message-ID: <20220113135228.w2pmabjmxlt3sq34@steredhat> (raw)
In-Reply-To: <20220112170936.245410-1-sgarzare@redhat.com>

On Wed, Jan 12, 2022 at 06:09:33PM +0100, Stefano Garzarella wrote:
>v11:
>- reworked "Message and record boundaries" paragraph [stefanha]
>
>v10: https://markmail.org/message/aebu4zqp4kxdm4ej
>
>Linux kernel and QEMU already merged SOCK_SEQPACKET support,
>so I'm resending Arseny's patches to have consistent virtio-spec
>and implementation.
>
>I added patch 2, following the discussion about F_STREAM feature bit:
>https://markmail.org/message/aoaspjy2jhidwbuo#query:+page:1+mid:obw54zzikgqimhjk+state:results
>
>About patch 2, the vhost-vsock device in the Linux kernel doesn't set bit 0
>(F_STREAM), so at this point I don't know if it's better to use a negative
>feature flag (e.g. F_NO_STREAM) or we go for F_STREAM and send a patch to
>linux-stable (and QEMU?) to solve this issue.
>
>Thanks,
>Stefano

Fixes: https://github.com/oasis-tcs/virtio-spec/issues/132

>
>Arseny Krasnov (2):
>  virtio-vsock: use C style defines for constants
>  virtio-vsock: SOCK_SEQPACKET description
>
>Stefano Garzarella (1):
>  virtio-vsock: add VIRTIO_VSOCK_F_STREAM feature bit
>
> virtio-vsock.tex | 86 ++++++++++++++++++++++++++++++++----------------
> 1 file changed, 58 insertions(+), 28 deletions(-)
>
>-- 
>2.31.1
>


      parent reply	other threads:[~2022-01-13 13:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 17:09 [PATCH v11 0/3] virtio-vsock: SOCK_SEQPACKET description Stefano Garzarella
2022-01-12 17:09 ` [PATCH v11 1/3] virtio-vsock: use C style defines for constants Stefano Garzarella
2022-01-12 17:09 ` [PATCH v11 2/3] virtio-vsock: add VIRTIO_VSOCK_F_STREAM feature bit Stefano Garzarella
2022-01-12 17:09 ` [PATCH v11 3/3] virtio-vsock: SOCK_SEQPACKET description Stefano Garzarella
2022-01-13 10:50 ` [virtio-comment] Re: [PATCH v11 0/3] " Cornelia Huck
2022-01-13 11:22   ` Stefano Garzarella
2022-01-13 11:34     ` [virtio-comment] " Cornelia Huck
2022-01-13 13:57       ` Stefano Garzarella
2022-01-13 14:06         ` [virtio-comment] " Cornelia Huck
2022-01-13 14:16           ` Stefano Garzarella
2022-01-13 15:11           ` Michael S. Tsirkin
2022-01-13 16:33             ` Stefano Garzarella
2022-01-13 13:19   ` Michael S. Tsirkin
2022-01-13 13:52 ` Stefano Garzarella [this message]

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=20220113135228.w2pmabjmxlt3sq34@steredhat \
    --to=sgarzare@redhat.com \
    --cc=arseny.krasnov@kaspersky.com \
    --cc=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@lists.oasis-open.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