From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Eugenio Perez Martin <eperezma@redhat.com>,
German Maglione <gmaglione@redhat.com>,
Liu Jiang <gerry@linux.alibaba.com>,
Sergio Lopez Pascual <slp@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH 7/7] vhost-user: call VHOST_USER_SET_VRING_ENABLE synchronously
Date: Mon, 2 Oct 2023 02:57:03 -0400 [thread overview]
Message-ID: <20231002025001-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2d361bac-9f8b-0a3a-ddd0-f66cd1294159@redhat.com>
On Mon, Oct 02, 2023 at 03:56:03AM +0200, Laszlo Ersek wrote:
> On 10/1/23 21:25, Michael S. Tsirkin wrote:
> > Not this actually - v2 of this.
>
> Thank you, but:
>
> - Stefan's question should be answered still IMO (although if you pick
> up this series, then that could be interpreted as "QEMU bug, not spec bug")
>
> - I was supposed to update the commit message on 7/7 in v3; I didn't
> want to do it before Stefan's question was answered
>
> Thanks!
> Laszlo
OK I just answered. I am fine with the patch but I think
virtiofsd should be fixed too.
--
MST
next prev parent reply other threads:[~2023-10-02 6:57 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 18:29 [PATCH 0/7] vhost-user: call VHOST_USER_SET_VRING_ENABLE synchronously Laszlo Ersek
2023-08-27 18:29 ` [PATCH 1/7] vhost-user: strip superfluous whitespace Laszlo Ersek
2023-08-30 8:26 ` Stefano Garzarella
2023-08-30 15:04 ` Philippe Mathieu-Daudé
2023-08-27 18:29 ` [PATCH 2/7] vhost-user: tighten "reply_supported" scope in "set_vring_addr" Laszlo Ersek
2023-08-30 8:27 ` Stefano Garzarella
2023-08-30 15:04 ` Philippe Mathieu-Daudé
2023-08-27 18:29 ` [PATCH 3/7] vhost-user: factor out "vhost_user_write_msg" Laszlo Ersek
2023-08-28 22:46 ` Philippe Mathieu-Daudé
2023-08-30 8:31 ` Stefano Garzarella
2023-08-30 9:14 ` Laszlo Ersek
2023-08-30 9:54 ` Laszlo Ersek
2023-08-27 18:29 ` [PATCH 4/7] vhost-user: flatten "enforce_reply" into "vhost_user_write_msg" Laszlo Ersek
2023-08-28 22:47 ` Philippe Mathieu-Daudé
2023-08-30 8:31 ` Stefano Garzarella
2023-08-27 18:29 ` [PATCH 5/7] vhost-user: hoist "write_msg", "get_features", "get_u64" Laszlo Ersek
2023-08-30 8:32 ` Stefano Garzarella
2023-08-30 15:04 ` Philippe Mathieu-Daudé
2023-08-27 18:29 ` [PATCH 6/7] vhost-user: allow "vhost_set_vring" to wait for a reply Laszlo Ersek
2023-08-28 22:49 ` Philippe Mathieu-Daudé
2023-08-30 8:32 ` Stefano Garzarella
2023-08-27 18:29 ` [PATCH 7/7] vhost-user: call VHOST_USER_SET_VRING_ENABLE synchronously Laszlo Ersek
2023-08-30 8:39 ` Stefano Garzarella
2023-08-30 9:26 ` Laszlo Ersek
2023-08-30 14:24 ` Stefano Garzarella
2023-08-30 8:41 ` Laszlo Ersek
2023-08-30 8:59 ` Laszlo Ersek
2023-08-30 9:04 ` Laszlo Ersek
2023-08-30 12:10 ` Stefan Hajnoczi
2023-08-30 13:30 ` Laszlo Ersek
2023-08-30 15:37 ` Stefan Hajnoczi
2023-09-05 6:30 ` Laszlo Ersek
2023-09-25 15:31 ` Laszlo Ersek
2023-10-01 19:24 ` Michael S. Tsirkin
2023-10-01 19:25 ` Michael S. Tsirkin
2023-10-02 1:56 ` Laszlo Ersek
2023-10-02 6:57 ` Michael S. Tsirkin [this message]
2023-10-02 14:02 ` Laszlo Ersek
2023-10-02 6:49 ` Michael S. Tsirkin
2023-10-02 21:12 ` Stefan Hajnoczi
2023-10-02 21:13 ` Stefan Hajnoczi
2023-10-03 12:26 ` Michael S. Tsirkin
2023-10-03 13:08 ` Stefan Hajnoczi
2023-10-03 13:23 ` Laszlo Ersek
2023-10-03 14:25 ` Michael S. Tsirkin
2023-10-03 14:28 ` Laszlo Ersek
2023-10-03 14:40 ` Michael S. Tsirkin
2023-10-03 15:45 ` Stefan Hajnoczi
2023-10-02 22:36 ` Michael S. Tsirkin
2023-10-03 0:17 ` Stefan Hajnoczi
2023-10-03 14:28 ` Michael S. Tsirkin
2023-10-03 14:41 ` Michael S. Tsirkin
2023-10-03 15:55 ` Stefan Hajnoczi
2023-10-04 10:15 ` Laszlo Ersek
2023-10-04 16:30 ` Michael S. Tsirkin
2023-10-04 10:17 ` Laszlo Ersek
2023-08-30 8:48 ` [PATCH 0/7] " Stefano Garzarella
2023-08-30 9:32 ` Laszlo Ersek
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=20231002025001-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=gerry@linux.alibaba.com \
--cc=gmaglione@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.com \
--cc=stefanha@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.