From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
Patch Tracking <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-stable <qemu-stable@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/curl: Implement the libcurl timer callback interface
Date: Thu, 16 Jan 2014 09:40:32 +0100 [thread overview]
Message-ID: <52D79B00.2060400@redhat.com> (raw)
In-Reply-To: <CAFEAcA-e=JgDJCNTuXp13jE7N4xLpWDbWLhWag67UuGfejpT+g@mail.gmail.com>
Il 15/01/2014 22:56, Peter Maydell ha scritto:
> > 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
>
> Looking through the thread from upstream, I see they basically
> said "you need to implement the timer callback" :-)
Which was hard to do only 6 months ago. But now that Alex Bligh
implemented all the infrastructure for aio_timer_init, it is fairly easy
as Peter's patch and mine show.
Paolo
next prev parent reply other threads:[~2014-01-16 8:48 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
2014-01-15 21:56 ` Peter Maydell
2014-01-16 8:40 ` Paolo Bonzini [this message]
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=52D79B00.2060400@redhat.com \
--to=pbonzini@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=rjones@redhat.com \
--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).