From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"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>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2 5/7] vhost-user: hoist "write_sync", "get_features", "get_u64"
Date: Thu, 31 Aug 2023 09:20:02 +0200 [thread overview]
Message-ID: <406fe376-b432-db47-9642-04d6254faf37@redhat.com> (raw)
In-Reply-To: <20230830134055.106812-6-lersek@redhat.com>
On 8/30/23 15:40, Laszlo Ersek wrote:
> In order to avoid a forward-declaration for "vhost_user_write_sync" in a
> subsequent patch, hoist "vhost_user_write_sync" ->
> "vhost_user_get_features" -> "vhost_user_get_u64" just above
> "vhost_set_vring".
>
> This is purely code movement -- no observable change.
>
> Cc: "Michael S. Tsirkin" <mst@redhat.com> (supporter:vhost)
> Cc: Eugenio Perez Martin <eperezma@redhat.com>
> Cc: German Maglione <gmaglione@redhat.com>
> Cc: Liu Jiang <gerry@linux.alibaba.com>
> Cc: Sergio Lopez Pascual <slp@redhat.com>
> Cc: Stefano Garzarella <sgarzare@redhat.com>
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
>
> Notes:
> v2:
>
> - pick up R-b from Stefano
>
> - rename "vhost_user_write_msg" to "vhost_user_write_sync" (in code and
> commit message) [Stefano]
>
> hw/virtio/vhost-user.c | 170 ++++++++++----------
> 1 file changed, 85 insertions(+), 85 deletions(-)
Phil reviewed v1:
http://mid.mail-archive.com/98150923-39ef-7581-6144-8d0ad8d4dd52@linaro.org
and I would've kept his R-b (similar to Stefano's) across the
vhost_user_write_msg->vhost_user_write_sync rename in v2; so I'm copying
it here:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Hope that's OK.
Laszlo
>
> diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
> index 4129ba72e408..c79b6f77cdca 100644
> --- a/hw/virtio/vhost-user.c
> +++ b/hw/virtio/vhost-user.c
> @@ -1083,6 +1083,91 @@ static int vhost_user_set_vring_endian(struct vhost_dev *dev,
> return vhost_user_write(dev, &msg, NULL, 0);
> }
>
> +static int vhost_user_get_u64(struct vhost_dev *dev, int request, uint64_t *u64)
> +{
> + int ret;
> + VhostUserMsg msg = {
> + .hdr.request = request,
> + .hdr.flags = VHOST_USER_VERSION,
> + };
> +
> + if (vhost_user_per_device_request(request) && dev->vq_index != 0) {
> + return 0;
> + }
> +
> + ret = vhost_user_write(dev, &msg, NULL, 0);
> + if (ret < 0) {
> + return ret;
> + }
> +
> + ret = vhost_user_read(dev, &msg);
> + if (ret < 0) {
> + return ret;
> + }
> +
> + if (msg.hdr.request != request) {
> + error_report("Received unexpected msg type. Expected %d received %d",
> + request, msg.hdr.request);
> + return -EPROTO;
> + }
> +
> + if (msg.hdr.size != sizeof(msg.payload.u64)) {
> + error_report("Received bad msg size.");
> + return -EPROTO;
> + }
> +
> + *u64 = msg.payload.u64;
> +
> + return 0;
> +}
> +
> +static int vhost_user_get_features(struct vhost_dev *dev, uint64_t *features)
> +{
> + if (vhost_user_get_u64(dev, VHOST_USER_GET_FEATURES, features) < 0) {
> + return -EPROTO;
> + }
> +
> + return 0;
> +}
> +
> +/* Note: "msg->hdr.flags" may be modified. */
> +static int vhost_user_write_sync(struct vhost_dev *dev, VhostUserMsg *msg,
> + bool wait_for_reply)
> +{
> + int ret;
> +
> + if (wait_for_reply) {
> + bool reply_supported = virtio_has_feature(dev->protocol_features,
> + VHOST_USER_PROTOCOL_F_REPLY_ACK);
> + if (reply_supported) {
> + msg->hdr.flags |= VHOST_USER_NEED_REPLY_MASK;
> + }
> + }
> +
> + ret = vhost_user_write(dev, msg, NULL, 0);
> + if (ret < 0) {
> + return ret;
> + }
> +
> + if (wait_for_reply) {
> + uint64_t dummy;
> +
> + if (msg->hdr.flags & VHOST_USER_NEED_REPLY_MASK) {
> + return process_message_reply(dev, msg);
> + }
> +
> + /*
> + * We need to wait for a reply but the backend does not
> + * support replies for the command we just sent.
> + * Send VHOST_USER_GET_FEATURES which makes all backends
> + * send a reply.
> + */
> + return vhost_user_get_features(dev, &dummy);
> + }
> +
> + return 0;
> +}
> +
> static int vhost_set_vring(struct vhost_dev *dev,
> unsigned long int request,
> struct vhost_vring_state *ring)
> @@ -1255,91 +1340,6 @@ static int vhost_user_set_vring_err(struct vhost_dev *dev,
> return vhost_set_vring_file(dev, VHOST_USER_SET_VRING_ERR, file);
> }
>
> -static int vhost_user_get_u64(struct vhost_dev *dev, int request, uint64_t *u64)
> -{
> - int ret;
> - VhostUserMsg msg = {
> - .hdr.request = request,
> - .hdr.flags = VHOST_USER_VERSION,
> - };
> -
> - if (vhost_user_per_device_request(request) && dev->vq_index != 0) {
> - return 0;
> - }
> -
> - ret = vhost_user_write(dev, &msg, NULL, 0);
> - if (ret < 0) {
> - return ret;
> - }
> -
> - ret = vhost_user_read(dev, &msg);
> - if (ret < 0) {
> - return ret;
> - }
> -
> - if (msg.hdr.request != request) {
> - error_report("Received unexpected msg type. Expected %d received %d",
> - request, msg.hdr.request);
> - return -EPROTO;
> - }
> -
> - if (msg.hdr.size != sizeof(msg.payload.u64)) {
> - error_report("Received bad msg size.");
> - return -EPROTO;
> - }
> -
> - *u64 = msg.payload.u64;
> -
> - return 0;
> -}
> -
> -static int vhost_user_get_features(struct vhost_dev *dev, uint64_t *features)
> -{
> - if (vhost_user_get_u64(dev, VHOST_USER_GET_FEATURES, features) < 0) {
> - return -EPROTO;
> - }
> -
> - return 0;
> -}
> -
> -/* Note: "msg->hdr.flags" may be modified. */
> -static int vhost_user_write_sync(struct vhost_dev *dev, VhostUserMsg *msg,
> - bool wait_for_reply)
> -{
> - int ret;
> -
> - if (wait_for_reply) {
> - bool reply_supported = virtio_has_feature(dev->protocol_features,
> - VHOST_USER_PROTOCOL_F_REPLY_ACK);
> - if (reply_supported) {
> - msg->hdr.flags |= VHOST_USER_NEED_REPLY_MASK;
> - }
> - }
> -
> - ret = vhost_user_write(dev, msg, NULL, 0);
> - if (ret < 0) {
> - return ret;
> - }
> -
> - if (wait_for_reply) {
> - uint64_t dummy;
> -
> - if (msg->hdr.flags & VHOST_USER_NEED_REPLY_MASK) {
> - return process_message_reply(dev, msg);
> - }
> -
> - /*
> - * We need to wait for a reply but the backend does not
> - * support replies for the command we just sent.
> - * Send VHOST_USER_GET_FEATURES which makes all backends
> - * send a reply.
> - */
> - return vhost_user_get_features(dev, &dummy);
> - }
> -
> - return 0;
> -}
> -
> static int vhost_user_set_vring_addr(struct vhost_dev *dev,
> struct vhost_vring_addr *addr)
> {
>
next prev parent reply other threads:[~2023-08-31 7:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 13:40 [PATCH v2 0/7] vhost-user: call VHOST_USER_SET_VRING_ENABLE synchronously Laszlo Ersek
2023-08-30 13:40 ` [PATCH v2 1/7] vhost-user: strip superfluous whitespace Laszlo Ersek
2023-08-31 7:13 ` Laszlo Ersek
2023-09-06 7:12 ` Albert Esteve
2023-09-06 9:09 ` Laszlo Ersek
2023-10-02 19:48 ` Laszlo Ersek
2023-08-30 13:40 ` [PATCH v2 2/7] vhost-user: tighten "reply_supported" scope in "set_vring_addr" Laszlo Ersek
2023-08-31 7:14 ` Laszlo Ersek
2023-08-30 13:40 ` [PATCH v2 3/7] vhost-user: factor out "vhost_user_write_sync" Laszlo Ersek
2023-08-30 13:40 ` [PATCH v2 4/7] vhost-user: flatten "enforce_reply" into "vhost_user_write_sync" Laszlo Ersek
2023-08-30 13:40 ` [PATCH v2 5/7] vhost-user: hoist "write_sync", "get_features", "get_u64" Laszlo Ersek
2023-08-31 7:20 ` Laszlo Ersek [this message]
2023-09-06 9:59 ` Philippe Mathieu-Daudé
2023-08-30 13:40 ` [PATCH v2 6/7] vhost-user: allow "vhost_set_vring" to wait for a reply Laszlo Ersek
2023-08-30 13:40 ` [PATCH v2 7/7] vhost-user: call VHOST_USER_SET_VRING_ENABLE synchronously Laszlo Ersek
2023-09-07 15:59 ` Eugenio Perez Martin
2023-09-07 20:27 ` Laszlo Ersek
2023-09-07 16:01 ` [PATCH v2 0/7] " Eugenio Perez Martin
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=406fe376-b432-db47-9642-04d6254faf37@redhat.com \
--to=lersek@redhat.com \
--cc=eperezma@redhat.com \
--cc=gerry@linux.alibaba.com \
--cc=gmaglione@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=slp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).