From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
hreitz@redhat.com,
Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
gmaglione@redhat.com, Jorge Moreira <jemoreira@google.com>
Subject: Re: [PATCH v2 1/3] vhost-user.rst: clarify when rings are started
Date: Thu, 4 Jun 2026 15:49:11 -0400 [thread overview]
Message-ID: <20260604194911.GB149856@fedora> (raw)
In-Reply-To: <ah_t8NHf4pYDPO9c@sgarzare-redhat>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Wed, Jun 03, 2026 at 11:04:42AM +0200, Stefano Garzarella wrote:
> On Tue, May 19, 2026 at 03:15:46PM -0400, Stefan Hajnoczi wrote:
> > Jorge Moreira <jemoreira@google.com> pointed out that the ring state
> > machine is underspecified. In the discussion that followed, we
> > discovered that the spec says one thing and implementations do something
> > else. This patch updates the spec to reflect how things are actually
> > implemented across widely-used front-ends and back-ends including QEMU,
> > crosvm, rust-vmm, and DPDK. Do this while taking care not to make any
> > other existing implementations non-compliant by changing the sepc.
>
> s/sepc/spec
Will fix.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-04 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 19:15 [PATCH v2 0/3] vhost-user.rst: clarify when rings are started Stefan Hajnoczi
2026-05-19 19:15 ` [PATCH v2 1/3] " Stefan Hajnoczi
2026-06-03 9:04 ` Stefano Garzarella
2026-06-04 19:49 ` Stefan Hajnoczi [this message]
2026-05-19 19:15 ` [PATCH v2 2/3] libvhost-user: look for available vq buffers upon SET_VRING_KICK Stefan Hajnoczi
2026-06-03 9:03 ` Stefano Garzarella
2026-06-04 19:47 ` Stefan Hajnoczi
2026-05-19 19:15 ` [PATCH v2 3/3] vhost-user: inject kick after SET_VRING_KICK Stefan Hajnoczi
2026-06-03 9:13 ` 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=20260604194911.GB149856@fedora \
--to=stefanha@redhat.com \
--cc=gmaglione@redhat.com \
--cc=hreitz@redhat.com \
--cc=jemoreira@google.com \
--cc=mst@redhat.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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 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.