From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <cfontana@suse.de>,
marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] build-sys: fix win32 compilation with --target-list=''
Date: Thu, 17 Dec 2020 12:46:57 +0100 [thread overview]
Message-ID: <7fc16ac5-d0c2-9475-abc8-bd415c6b2a73@redhat.com> (raw)
In-Reply-To: <5c6d244b-1ed3-f065-88b6-7a007a224cc4@suse.de>
On 17/12/20 12:32, Claudio Fontana wrote:
> Is the root cause elsewhere though?
>
> I don't like stubs very much, because often they are introduced as the easy way out of a problem instead of doing the necessary refactoring,
> and they end up confusing the hell out of someone trying to understand what is actually used where, never mind trying to debug the linker errors.
>
> There is already an bunch of #ifndef _WIN32, #else , ... in util/main-loop.c (quite a bunch of them really),
> is that what actually needs reworking, and putting the pieces together in the build system in a way that makes sense?
qemu_fd_register is almost not needed at all, since we have
WSAEventSelect(node->pfd.fd, event, bitmask);
in aio_set_fd_handler. I think we can remove the call to
qemu_fd_register from qemu_try_set_nonblock, and that should fix the
issue as well.
Paolo
next prev parent reply other threads:[~2020-12-17 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 10:44 [PATCH] build-sys: fix win32 compilation with --target-list='' marcandre.lureau
2020-12-17 11:32 ` Claudio Fontana
2020-12-17 11:41 ` Marc-André Lureau
2020-12-17 11:46 ` Paolo Bonzini [this message]
2020-12-18 13:01 ` Marc-André Lureau
2020-12-18 13:21 ` Paolo Bonzini
2020-12-18 13:33 ` Marc-André Lureau
2020-12-18 13:23 ` Marc-André Lureau
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=7fc16ac5-d0c2-9475-abc8-bd415c6b2a73@redhat.com \
--to=pbonzini@redhat.com \
--cc=cfontana@suse.de \
--cc=marcandre.lureau@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).