From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: qemu-devel@nongnu.org, "Konstantin Kostiuk" <kkostiuk@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Weil" <sw@weilnetz.de>
Subject: Re: [PATCH 0/5] Enable unix socket support on Windows
Date: Wed, 27 Jul 2022 10:06:01 +0100 [thread overview]
Message-ID: <YuD/+ehoLlwvzopk@redhat.com> (raw)
In-Reply-To: <20220727073542.811420-1-bmeng.cn@gmail.com>
On Wed, Jul 27, 2022 at 03:35:37PM +0800, Bin Meng wrote:
> Support for the unix socket has existed both in BSD and Linux for the
> longest time, but not on Windows. Since Windows 10 build 17063 [1],
> the native support for the unix socket has came to Windows. Starting
> this build, two Win32 processes can use the AF_UNIX address family
> over Winsock API to communicate with each other.
>
> Introduce a new build time config option CONFIG_AF_UNIX when the build
> host has such a capability, and a run-time check afunix_available() for
> Windows host in the QEMU sockets util codes.
>
> [1] https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
>
>
> Bin Meng (5):
> util/qemu-sockets: Replace the call to close a socket with
> closesocket()
> util/oslib-win32: Add a helper to get the Windows version
> qga/commands-win32: Use os_get_win_version()
> util/qemu-sockets: Enable unix socket support on Windows
> chardev/char-socket: Update AF_UNIX for Windows
>
> meson.build | 6 +++++
> include/sysemu/os-win32.h | 2 ++
> chardev/char-socket.c | 8 +++++-
> qga/commands-win32.c | 27 +-------------------
> util/oslib-win32.c | 15 +++++++++++
> util/qemu-sockets.c | 52 ++++++++++++++++++++++++++++++++-------
> 6 files changed, 74 insertions(+), 36 deletions(-)
What about net/socket.c ?
Also there are many tests using AF_UNIX and this doesn't appear to
have enablede any of them. I'd at least exepct to see the sockets
tests-io-channel-socket.c test enabled to prove this functionality
is working.
There are a few other AF_UNIX references in teh code, though many
seems to be Linux specific.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-07-27 9:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 7:35 [PATCH 0/5] Enable unix socket support on Windows Bin Meng
2022-07-27 7:35 ` [PATCH 1/5] util/qemu-sockets: Replace the call to close a socket with closesocket() Bin Meng
2022-07-27 7:35 ` [PATCH 2/5] util/oslib-win32: Add a helper to get the Windows version Bin Meng
2022-07-27 8:50 ` Yan Vugenfirer
2022-07-27 9:38 ` Bin Meng
2022-07-27 9:59 ` Daniel P. Berrangé
2022-07-27 10:57 ` Yan Vugenfirer
2022-07-27 11:55 ` Bin Meng
2022-07-27 12:53 ` Daniel P. Berrangé
2022-07-27 13:15 ` Bin Meng
2022-07-27 13:18 ` Konstantin Kostiuk
2022-07-27 13:21 ` Bin Meng
2022-07-27 7:35 ` [PATCH 3/5] qga/commands-win32: Use os_get_win_version() Bin Meng
2022-07-27 8:59 ` Konstantin Kostiuk
2022-07-27 7:35 ` [PATCH 4/5] util/qemu-sockets: Enable unix socket support on Windows Bin Meng
2022-07-27 8:50 ` Yan Vugenfirer
2022-07-27 9:58 ` Bin Meng
2022-07-27 8:53 ` Konstantin Kostiuk
2022-07-27 10:01 ` Bin Meng
2022-07-28 13:11 ` Marc-André Lureau
2022-07-28 13:41 ` Bin Meng
2022-07-27 7:35 ` [PATCH 5/5] chardev/char-socket: Update AF_UNIX for Windows Bin Meng
2022-07-27 9:06 ` Daniel P. Berrangé [this message]
2022-07-27 10:15 ` [PATCH 0/5] Enable unix socket support on Windows Bin Meng
2022-07-27 10:24 ` Daniel P. Berrangé
2022-07-27 11:37 ` Bin Meng
2022-07-27 11:45 ` Stefan Weil via
2022-07-27 12:17 ` Bin Meng
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=YuD/+ehoLlwvzopk@redhat.com \
--to=berrange@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=kkostiuk@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.