From: "Michael S. Tsirkin" <mst@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
virtio-comment@lists.linux.dev, dev@lists.cloudhypervisor.org,
rust-vmm@lists.opendev.org,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Demi Marie Obenour" <demi@invisiblethingslab.com>,
"Alyssa Ross" <hi@alyssa.is>,
"Mark Burton" <MBURTON@qti.qualcomm.com>,
"Matti Moell" <matti@qti.qualcomm.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Dorinda Bassey" <dbassey@redhat.com>,
"Sergio Lopez" <slp@redhat.com>,
"Vishwanath Seshagiri" <vishs@meta.com>,
"Rob Bradford" <rbradford@meta.com>,
"Zhengyu Zhao" <zhaozhengyu@bytedance.com>,
"Jorge E. Moreira" <jemoreira@google.com>
Subject: Re: Where should the vhost-user specification live?
Date: Mon, 1 Jun 2026 08:39:35 -0400 [thread overview]
Message-ID: <20260601083628-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CADSE00+RdBUhFVBDSXtVd1J5SaccqWy+RBxqnxuLKUYcitFMPw@mail.gmail.com>
On Mon, Jun 01, 2026 at 02:32:11PM +0200, Albert Esteve wrote:
> But also because, in my opinion, separating
> the specification would improve development agility by decoupling
> specification development from QEMU's review and release cycles.
Generally for QEMU this will be less agility, unless I misunderstand
what is proposed)
Because presumably there will need to be spec releases then?
So
new feature -> spec tree -> spec release -> qemu implementation -> qemu release
is surely longer that what we have now.
Whether there will be more agility for non qemu users will depend on
how often spec releases are cut.
--
MST
next prev parent reply other threads:[~2026-06-01 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 9:13 Where should the vhost-user specification live? Alex Bennée
2026-05-27 12:55 ` Michael S. Tsirkin
2026-05-27 13:58 ` Alex Bennée
2026-06-01 12:32 ` Albert Esteve
2026-06-01 12:39 ` Michael S. Tsirkin [this message]
2026-06-01 13:05 ` Albert Esteve
2026-06-01 13:11 ` Michael S. Tsirkin
[not found] ` <CAJSP0QV4W=5MJsSGggACv-tqxDtiieKc0YzEn8t-R=RD94KJaQ@mail.gmail.com>
2026-06-01 14:22 ` Michael S. Tsirkin
2026-06-01 16:58 ` Stefan Hajnoczi
2026-06-01 14:27 ` Albert Esteve
2026-06-01 14:37 ` Michael S. Tsirkin
2026-06-01 15:18 ` Stefan Hajnoczi
2026-06-01 20:04 ` Michael S. Tsirkin
[not found] ` <CACzuRyxedVMHNGkRf7AVyPWUTMgBMa6_DBnSHn+V6H7wN7XzWw@mail.gmail.com>
2026-06-04 16:28 ` 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=20260601083628-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=MBURTON@qti.qualcomm.com \
--cc=aesteve@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=dbassey@redhat.com \
--cc=demi@invisiblethingslab.com \
--cc=dev@lists.cloudhypervisor.org \
--cc=hi@alyssa.is \
--cc=jemoreira@google.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=matti@qti.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=rbradford@meta.com \
--cc=rust-vmm@lists.opendev.org \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.com \
--cc=stefanha@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-comment@lists.linux.dev \
--cc=vishs@meta.com \
--cc=zhaozhengyu@bytedance.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