From: Anthony Liguori <anthony@codemonkey.ws>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH][RFC][RFT] Let qemu-nbd build on Windows and replace QEMU_IMG/QEMU_NBD with QEMU_TOOL
Date: Sat, 13 Sep 2008 11:48:50 -0500 [thread overview]
Message-ID: <48CBEEF2.6070608@codemonkey.ws> (raw)
In-Reply-To: <48CBE8E8.9010208@codemonkey.ws>
Anthony Liguori wrote:
> Laurent Vivier wrote:
>> Le vendredi 12 septembre 2008 à 20:05 -0500, Anthony Liguori a écrit :
>>
>>> This patch attempts to clean up the mess with qemu-nbd in the
>>> Makefile in order to get it building and working on Windows. I
>>> checked block-nbd, qemu-img, and qemu-nbd on Windows and Linux and
>>> everything seems to work. However, there were some
>>> defined(QEMU_IMG) that didn't include defined(QEMU_NBD) that now are
>>> covered by QEMU_TOOL so I'd like Laurent to look them over and see
>>> if they were intentional.
>>>
>>
>> If I remember correctly they were intentional:
>> - some of them because qemu-nbd didn't support windows (but you have
>> corrected this)
>> - others because qemu-img doesn't need to open file with O_DIRECT
>> whereas qemu-nbd must (--nocache option) (and I think you break this)
>>
>> Did you test "qemu-nbd --nocache" ?
>>
>
> No, but this is why I asked :-)
>
> So this begs the question, why does qemu-nbd need to open files with
> O_DIRECT and why doesn't qemu-img?
>
> Can we just enable the code in both?
Oh, I see. It's because we don't have bottom halves with QEMU_TOOL.
That's easy enough to fix. I'll update the patch.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-09-13 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 1:05 [Qemu-devel] [PATCH][RFC][RFT] Let qemu-nbd build on Windows and replace QEMU_IMG/QEMU_NBD with QEMU_TOOL Anthony Liguori
2008-09-13 15:30 ` [Qemu-devel] " Laurent Vivier
2008-09-13 16:23 ` Anthony Liguori
2008-09-13 16:48 ` Anthony Liguori [this message]
2008-09-13 17:25 ` Anthony Liguori
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=48CBEEF2.6070608@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Laurent.Vivier@bull.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).