From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
qemu-devel@nongnu.org, Dorinda Bassey <dbassey@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Albert Esteve <aesteve@redhat.com>,
Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
vhost-user@lists.linux.dev
Subject: Re: [PATCH] vhost-user: add dedicated mailing list
Date: Fri, 23 Oct 2026 13:26:45 -0400 [thread overview]
Message-ID: <20261023132627-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <atuSO02ui1nOWKsQ@redhat.com>
On Fri, Oct 23, 2026 at 05:58:35PM +0100, Daniel P. Berrangé wrote:
> On Fri, Oct 23, 2026 at 06:24:40PM +0200, Stefano Garzarella wrote:
> > From: Stefano Garzarella <sgarzare@redhat.com>
> >
> > During the "Virtio and Vhost-User Ecosystem for Production and
> > Automotive Systems" BoF at LPC 2026 [1] we discussed and agreed on
> > creating a new vhost-user mailing list, mainly for changes to the
> > specification and discussions around the protocol.
>
> You say the list is for discussions around the spec / protocol, but...
>
> > The main reason is that the vhost-user specification is also used
> > by other VMMs and implemented by several back-ends outside the QEMU
> > repository, whose developers often do not follow qemu-devel.
> >
> > Add a paragraph in the specification about the new mailing list and
> > a dedicated MAINTAINERS entry for the vhost-user protocol, covering
> > the specification, the QEMU front-end and libvhost-user (back-end
> > library).
>
> ...this MAINTAINERS addition means the mailing list will be CC'd
> on all code patches sent to QEMU for those file patterns. Are you
> sure that's content that members of the list want to be sent
> unconditionally ?
>
>
Good point. Let's make it a separate section?
> >
> > [1] https://lpc.events/event/20/contributions/2365/
> >
> > Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
> > ---
> > MAINTAINERS | 12 ++++++++++--
> > docs/interop/vhost-user.rst | 6 ++++++
> > 2 files changed, 16 insertions(+), 2 deletions(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index d9209f043f..dcdb65d8cb 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -2532,19 +2532,27 @@ M: Michael S. Tsirkin <mst@redhat.com>
> > R: Stefano Garzarella <sgarzare@redhat.com>
> > S: Supported
> > F: hw/*/*vhost*
> > -F: docs/interop/vhost-user*
> > F: docs/system/devices/virtio/vhost-user*
> > F: contrib/vhost-user-*/
> > F: backends/*vhost*
> > F: include/system/vhost-user-backend.h
> > F: include/hw/virtio/vhost*
> > F: include/*/vhost*
> > -F: subprojects/libvhost-user/
> > F: block/export/vhost-user*
> > F: util/vhost-user-server.c
> > F: net/vhost*
> > F: tests/functional/x86_64/test_vhost_user_bridge.py
> >
> > +vhost-user protocol
> > +M: Michael S. Tsirkin <mst@redhat.com>
> > +R: Stefano Garzarella <sgarzare@redhat.com>
> > +L: vhost-user@lists.linux.dev
> > +S: Supported
> > +F: docs/interop/vhost-user*
> > +F: hw/virtio/vhost-user.c
> > +F: include/hw/virtio/vhost-user.h
> > +F: subprojects/libvhost-user/
> > +
> > vhost-shadow-virtqueue
> > R: Eugenio Pérez <eperezma@redhat.com>
> > F: hw/virtio/vhost-shadow-virtqueue.*
> > diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst
> > index c1e02ff7e9..198ad30f5c 100644
> > --- a/docs/interop/vhost-user.rst
> > +++ b/docs/interop/vhost-user.rst
> > @@ -38,6 +38,12 @@ conventions <backend_conventions>`.
> > The *front-end* and *back-end* can be either a client (i.e. connecting) or
> > server (listening) in the socket communication.
> >
> > +The protocol is developed and discussed on the `vhost-user mailing list
> > +<mailto:vhost-user@lists.linux.dev>`_, archived at
> > +https://lore.kernel.org/vhost-user/. Until October 2026, when this list
> > +was created, discussions took place on the qemu-devel mailing list,
> > +archived at https://lore.kernel.org/qemu-devel/.
> > +
> > Support for platforms other than Linux
> > --------------------------------------
> >
> > --
> > 2.56.0
> >
> >
>
> With regards,
> Daniel
> --
> |: https://berrange.com ~~ https://hachyderm.io/@berrange :|
> |: https://libvirt.org ~~ https://entangle-photo.org :|
> |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-10-23 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 16:24 [PATCH] vhost-user: add dedicated mailing list Stefano Garzarella
2026-10-23 16:58 ` Daniel P. Berrangé
2026-10-23 17:26 ` Michael S. Tsirkin [this message]
2026-10-23 17:50 ` Stefano Garzarella
2026-10-23 23:01 ` Michael S. Tsirkin
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=20261023132627-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aesteve@redhat.com \
--cc=berrange@redhat.com \
--cc=dbassey@redhat.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=vhost-user@lists.linux.dev \
/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.