From: "alex" <void@aleksoft.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Re: mingw compile error patch
Date: Wed, 23 Aug 2006 09:01:13 -0700 [thread overview]
Message-ID: <echu4b$nfq$1@sea.gmane.org> (raw)
In-Reply-To: 000c01c6c5be$fdffdda0$0464a8c0@athlon
Is anybody actively working on that?
Any hints of what should be done to make it work?
Looking at the code, I see that qemu_aio_init, qemu_aio_poll,
qemu_aio_wait_start, qemu_aio_wait, and qemu_aio_wait_end
under _WIN32 have empty bodies. Is this intentional or what should happen
there?
"Kazu" <kazoo@r3.dion.ne.jp> wrote in message
news:000c01c6c5be$fdffdda0$0464a8c0@athlon...
> Alex wrote:
>
> > That's better. What's wrong with QCOW?
> >
>
> Qcow uses aio interface but aio emulation is not fully implemented.
>
> Regards,
> Kazu
prev parent reply other threads:[~2006-08-23 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 0:24 [Qemu-devel] mingw compile error patch alex
2006-08-22 4:22 ` Kazu
2006-08-22 5:18 ` [Qemu-devel] " Alex
2006-08-22 7:45 ` Kazu
2006-08-23 16:01 ` alex [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='echu4b$nfq$1@sea.gmane.org' \
--to=void@aleksoft.net \
--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).