From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] Tap and VLAN socket support for win32
Date: Thu, 9 Feb 2006 23:00:33 +0900 [thread overview]
Message-ID: <005301c62d81$31d9db70$0464a8c0@athlon> (raw)
In-Reply-To: 43E4F24F.6040908@bellard.org
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Hi,
I send this mail again because it doesn't reach qemu-devel list by unknown
security reason.
Sent: Sunday, February 05, 2006 3:28 AM Fabrice Bellard wrote:
> Kazu wrote:
>> Thursday, February 02, 2006 8:10 AM Fabrice Bellard wrote:
>>
>>> Hi,
>>>
>>> I merged your patches and I made important changes to simplify them. I
>>> did not do any tests so tell me if you see problems.
>>>
>>
>> -net socket,connect doesn't work. On Windows host, connect returns with
err
>> = WSAEWOULDBLOCK and second time err = WSAEINVAL. I think changing the
>> place
>> of EWOULDBLOCK would be good. On Linux host, EWOULDBLOCK is the same as
>> EAGAIN but a patch works on both Linux and Windows.
>
> Unfortunately on Linux the correct return value we are expecting is
> EINPROGRESS. EAGAIN means that the 'connect' was not initiated so it is
> necessary to redo it.
>
There is not good way to detect a completion of asynchronous connect. So I
used an event object to detect it. A patch is attached.
>>
>> For -net socket,mcast, bind have to be done by sin_addr.s_addr =
>> INADDR_ANY.
>> It seems that it works on Linux host.
>
> It works on Linux but it is not correct because it prevents from
> listening to several multicast addresses at the same time. If doing the
> same on Windows is not possible I agree to make a special case.
>
I couldn't find a way to set a multicast address. I made it a special case
in the patch
Regards,
Kazu
[-- Attachment #2: qemu-20060208-vlan-2.patch.gz --]
[-- Type: application/x-gzip, Size: 1475 bytes --]
next prev parent reply other threads:[~2006-02-09 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 7:34 [Qemu-devel][PATCH] Tap and VLAN socket support for win32 Kazu
2006-01-31 16:00 ` André Braga
2006-02-01 23:10 ` Fabrice Bellard
2006-02-02 10:03 ` Kazu
2006-02-04 18:28 ` Fabrice Bellard
2006-02-09 2:29 ` Kazu
2006-02-09 14:00 ` Kazu [this message]
2006-02-05 4:05 ` Jim C. Brown
2006-02-07 21:18 ` Jim C. Brown
2006-02-07 21:44 ` Fabrice Bellard
2006-02-08 7:23 ` David Fraser
2006-02-08 7:32 ` M. Warner Losh
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='005301c62d81$31d9db70$0464a8c0@athlon' \
--to=kazoo@r3.dion.ne.jp \
--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).