From: "Richard W.M. Jones" <rjones@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
patches@linaro.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block/curl: Implement the libcurl timer callback interface
Date: Wed, 15 Jan 2014 21:37:19 +0000 [thread overview]
Message-ID: <20140115213719.GC13802@redhat.com> (raw)
In-Reply-To: <1389806638-3114-1-git-send-email-peter.maydell@linaro.org>
On Wed, Jan 15, 2014 at 05:23:58PM +0000, Peter Maydell wrote:
> libcurl versions 7.16.0 and later have a timer callback interface which
> must be implemented in order for libcurl to make forward progress (it
> will sometimes rely on being called back on the timeout if there are
> no file descriptors registered). Implement the callback, and use a
> QEMU AIO timer to ensure we prod libcurl again when it asks us to.
Somewhat off topic, but does the curl driver work for you at all?
Especially if you have a disk image on a remote server, but one with
relatively low latency (eg. on a LAN but not localhost).
We have had endless problems with it, including upstream discussions
with curl people, summarised in this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=971790
Just now I tried the latest qemu from git with and without your patch
and still cannot make it work, although the bugginess is now different
from RHBZ#971790. I opened a new bug about what I'm seeing today
(https://bugs.launchpad.net/qemu/+bug/1269606).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
next prev parent reply other threads:[~2014-01-15 21:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 17:23 [Qemu-devel] [PATCH] block/curl: Implement the libcurl timer callback interface Peter Maydell
2014-01-15 21:37 ` Richard W.M. Jones [this message]
2014-01-15 21:56 ` Peter Maydell
2014-01-16 8:40 ` Paolo Bonzini
2014-01-15 22:06 ` Paolo Bonzini
2014-01-15 22:15 ` Peter Maydell
2014-01-16 8:38 ` Paolo Bonzini
2014-01-16 9:55 ` Peter Maydell
2014-01-16 10:15 ` Paolo Bonzini
2014-01-16 9:12 ` Richard W.M. Jones
2014-01-16 9:24 ` Richard W.M. Jones
2014-01-16 9:52 ` Kevin Wolf
-- strict thread matches above, loose matches on Subject: below --
2014-01-24 13:56 Paolo Bonzini
2014-01-24 15:01 ` Kevin Wolf
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=20140115213719.GC13802@redhat.com \
--to=rjones@redhat.com \
--cc=kwolf@redhat.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.com \
/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).