From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: peter.maydell@linaro.org, f4bug@amsat.org,
marcandre.lureau@redhat.com, richard.henderson@linaro.org,
berrange@redhat.com, mst@redhat.com, kraxel@redhat.com,
qemu-devel@nongnu.org
Cc: tugy@chinatelecom.cn
Subject: Re: [PATCH v1 0/2] introduce qemu_socketpiar()
Date: Mon, 05 Sep 2022 14:04:24 +0200 [thread overview]
Message-ID: <2356130.dJNAEDbtAm@silver> (raw)
In-Reply-To: <cover.1661240709.git.tugy@chinatelecom.cn>
On Dienstag, 23. August 2022 09:50:38 CEST tugy@chinatelecom.cn wrote:
> From: Guoyi Tu <tugy@chinatelecom.cn>
>
> Introduce qemu_socketpair() to create socket pair fd, and
> set the close-on-exec flag at default as with the other type
> of socket does.
>
> besides, the live update feature is developing, so it's necessary
> to do that.
>
> Guoyi Tu (2):
> oslib-posix: Introduce qemu_socketpair()
> vhost-user: Call qemu_socketpair() instead of socketpair()
>
> hw/display/vhost-user-gpu.c | 3 ++-
> hw/virtio/vhost-user.c | 2 +-
> include/qemu/sockets.h | 18 ++++++++++++++++++
> util/oslib-posix.c | 19 +++++++++++++++++++
> 4 files changed, 40 insertions(+), 2 deletions(-)
Reviewed-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
next prev parent reply other threads:[~2022-09-05 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:50 [PATCH v1 0/2] introduce qemu_socketpiar() tugy
2022-08-23 7:50 ` [PATCH v1 1/2] oslib-posix: Introduce qemu_socketpair() tugy
2022-08-23 7:50 ` [PATCH v1 2/2] vhost-user: Call qemu_socketpair() instead of socketpair() tugy
2022-09-05 9:53 ` [PATCH v1 0/2] introduce qemu_socketpiar() Guoyi Tu
2022-09-05 11:19 ` Marc-André Lureau
2022-09-05 12:27 ` Guoyi Tu
2022-09-05 12:33 ` Marc-André Lureau
2022-09-05 13:00 ` Guoyi Tu
2022-09-05 12:04 ` Christian Schoenebeck [this message]
2022-09-19 7:20 ` Guoyi Tu
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=2356130.dJNAEDbtAm@silver \
--to=qemu_oss@crudebyte.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=tugy@chinatelecom.cn \
/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.