qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Albert Esteve <aesteve@redhat.com>
Cc: qemu-devel@nongnu.org, Fam Zheng <fam@euphon.net>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	cohuck@redhat.com, kraxel@redhat.com, marcandre.lureau@gmail.com
Subject: Re: [PATCH v6 3/3] vhost-user: add shared_object msg
Date: Thu, 7 Sep 2023 08:19:09 +0200	[thread overview]
Message-ID: <a8a2f3cf-4d68-7ffd-23f2-205461ff772f@linaro.org> (raw)
In-Reply-To: <CADSE00K7=roimgZy4ZnMmQu=vEP13S71BuEctWgfUB0Hv5iF0A@mail.gmail.com>

On 6/9/23 18:18, Albert Esteve wrote:

>     So:
>     - Regarding the two functions with the same, seems to be solved with
>     the squash before,
>        and it was probably causing the compile error to begin with, so
>     one less thing to worry about!
>     - Regarding splitting the commit, sure, no problem. I'll ensure they
>     do compile separately.
>     - Regarding the error, I read the long comment in the error file and
>     checked surrounding code. I think
>        you are right and will be better propagating the error.
> 
> 
> But I think I will omit the Error propagation for 
> `vhost_user_backend_handle_shared_object_lookup`.
> In this function returning an error code does not necessarily mean that 
> we should log an error.
> So if we pass the local_err from the backend_read function to the 
> handler, we cannot be sure
> when we should actually print the log.
> `vhost_backend_handle_iotlb_msg` has the same issue and does not 
> propagate the error either,
> relies solely on `error_report` calls.
> 
> Therefore, I will propagate it for `vhost_user_send_resp` and 
> `vhost_user_backend_send_dmabuf_fd` only.

Sounds good!



      reply	other threads:[~2023-09-07  6:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 11:15 [PATCH v6 0/3] Virtio shared dma-buf Albert Esteve
2023-09-06 11:15 ` [PATCH v6 1/3] uuid: add a hash function Albert Esteve
2023-09-06 11:15 ` [PATCH v6 2/3] virtio-dmabuf: introduce virtio-dmabuf Albert Esteve
2023-09-06 12:03   ` Albert Esteve
2023-09-06 14:21   ` Philippe Mathieu-Daudé
2023-09-06 15:34     ` Albert Esteve
2023-09-06 11:15 ` [PATCH v6 3/3] vhost-user: add shared_object msg Albert Esteve
2023-09-06 14:27   ` Philippe Mathieu-Daudé
2023-09-06 14:33     ` Albert Esteve
2023-09-06 14:43       ` Philippe Mathieu-Daudé
2023-09-06 16:01         ` Albert Esteve
2023-09-06 16:18           ` Albert Esteve
2023-09-07  6:19             ` Philippe Mathieu-Daudé [this message]

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=a8a2f3cf-4d68-7ffd-23f2-205461ff772f@linaro.org \
    --to=philmd@linaro.org \
    --cc=aesteve@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=fam@euphon.net \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).