All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Jorge Moreira <jemoreira@google.com>,
	hreitz@redhat.com, gmaglione@redhat.com,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Hanna Czenczek <xanclic@gmail.com>,
	Pierrick Bouvier <pierrick.bouvier@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] vhost-user.rst: Explicitly allow front-end to write to kick FDs
Date: Tue, 21 Apr 2026 15:57:22 -0400	[thread overview]
Message-ID: <20260421195722.GA466778@fedora> (raw)
In-Reply-To: <CAGxU2F5y5omgvSUV+JQCAsUQVSQVkdzXhsS5QYysETerDjVkdA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

On Tue, Apr 21, 2026 at 06:49:32PM +0200, Stefano Garzarella wrote:
> On Tue, 21 Apr 2026 at 18:06, Jorge Moreira <jemoreira@google.com> wrote:
> >
> > > Do you know other backends we should check?
> >
> > CrosVm's: https://github.com/google/crosvm/tree/main/devices/src/virtio/vhost_user_backend
> 
> Which do exactly the same
> https://github.com/google/crosvm/blob/b49e336de56d6353ae06245de0c7fabec3db2d5e/devices/src/virtio/vhost_user_backend/handler.rs#L596
> 
> No?

To round this out, I looked at DPDK, one of the most popular vhost-user
back-end implementations.

The DPDK back-end starts/stops the rings in the vhost-user message
handler rather than upon reading the kick fd:
https://github.com/DPDK/dpdk/blob/main/lib/vhost/vhost_user.c#L3274

I think it would be nice to update the spec since it seems
implementations aren't actually waiting for the kick fd. However, it is
not central to the original discussion, so feel free to skip it if you
want.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-04-21 19:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11  2:12 [PATCH] vhost-user.rst: Explicitly allow front-end to write to kick FDs Jorge E. Moreira
2026-04-20 14:49 ` Stefano Garzarella
2026-04-20 15:57   ` Stefano Garzarella
2026-04-21 20:51     ` Stefan Hajnoczi
2026-04-22  8:25       ` Stefano Garzarella
2026-04-20 18:18   ` Stefan Hajnoczi
2026-04-21  0:48     ` Jorge Moreira
2026-04-21  7:55       ` Stefano Garzarella
2026-04-21 16:06         ` Jorge Moreira
2026-04-21 16:49           ` Stefano Garzarella
2026-04-21 19:57             ` Stefan Hajnoczi [this message]
2026-04-21 21:12       ` Stefan Hajnoczi
2026-04-22  1:16         ` Jorge Moreira
2026-04-22  8:32           ` Stefano Garzarella
2026-04-22 19:20             ` Jorge Moreira
2026-04-27 22:45               ` Stefan Hajnoczi
2026-04-27 22:48                 ` Jorge Moreira
2026-04-28 14:33                   ` Stefano Garzarella
2026-04-28 17:19                     ` Jorge Moreira
2026-04-29 14:26                       ` Stefano Garzarella
2026-04-29 16:00                       ` Stefan Hajnoczi
2026-04-29 15:55                     ` Stefan Hajnoczi
2026-04-28  6:59                 ` Michael S. Tsirkin
2026-04-29 15:50                   ` 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=20260421195722.GA466778@fedora \
    --to=stefanha@redhat.com \
    --cc=gmaglione@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=jemoreira@google.com \
    --cc=mst@redhat.com \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=xanclic@gmail.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 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.