From: Anthony Liguori <anthony@codemonkey.ws>
To: Sage Weil <sage@inktank.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Josh Durgin <josh.durgin@inktank.com>,
Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
ceph-devel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v3 2/2] rbd: link and load librbd dynamically
Date: Fri, 21 Jun 2013 14:13:57 -0500 [thread overview]
Message-ID: <87ppvfuvii.fsf@codemonkey.ws> (raw)
In-Reply-To: <alpine.DEB.2.00.1306211138310.454@cobra.newdream.net>
Sage Weil <sage@inktank.com> writes:
> Hi Anthony, Stefan, Paolo,
>
> [Resurrecting an old thread, here!]
>
> On Wed, 10 Apr 2013 Anthony Liguori wrote:
>
> Has any progress been made toward a generic dynamic linking solution for
> block drivers? It is a conceptually simple change, but non-trivial for
> anyone unfamiliar with the build system.
There are patches on the list in fact.
> In the mean time, the inability to dynamically link librbd is continuing
> to cause significant pain for distro users. Would you consider merging
> the rbd-specific linking as an interim solution until something is
> generically available to qemu?
Regards,
Anthony Liguori
>
> sage
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Sage Weil <sage@inktank.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Josh Durgin <josh.durgin@inktank.com>,
Paolo Bonzini <pbonzini@redhat.com>,
ceph-devel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v3 2/2] rbd: link and load librbd dynamically
Date: Fri, 21 Jun 2013 14:13:57 -0500 [thread overview]
Message-ID: <87ppvfuvii.fsf@codemonkey.ws> (raw)
In-Reply-To: <alpine.DEB.2.00.1306211138310.454@cobra.newdream.net>
Sage Weil <sage@inktank.com> writes:
> Hi Anthony, Stefan, Paolo,
>
> [Resurrecting an old thread, here!]
>
> On Wed, 10 Apr 2013 Anthony Liguori wrote:
>
> Has any progress been made toward a generic dynamic linking solution for
> block drivers? It is a conceptually simple change, but non-trivial for
> anyone unfamiliar with the build system.
There are patches on the list in fact.
> In the mean time, the inability to dynamically link librbd is continuing
> to cause significant pain for distro users. Would you consider merging
> the rbd-specific linking as an interim solution until something is
> generically available to qemu?
Regards,
Anthony Liguori
>
> sage
next prev parent reply other threads:[~2013-06-21 19:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 7:59 [Qemu-devel] [PATCH] rbd: add an asynchronous flush Josh Durgin
2013-03-29 20:03 ` [Qemu-devel] [PATCH v2] " Josh Durgin
2013-04-02 14:10 ` Kevin Wolf
2013-04-04 8:35 ` [Qemu-devel] [PATCH v3 1/2] " Josh Durgin
2013-04-04 8:35 ` [Qemu-devel] [PATCH 2/2] rbd: disable unsupported librbd functions at runtime Josh Durgin
2013-04-04 10:10 ` Kevin Wolf
2013-04-04 16:50 ` Josh Durgin
2013-04-05 9:31 ` Kevin Wolf
2013-04-10 0:05 ` [Qemu-devel] [PATCH v3 2/2] rbd: link and load librbd dynamically Josh Durgin
2013-04-10 8:09 ` Stefan Hajnoczi
2013-04-10 14:52 ` [Qemu-devel] runtime Block driver modules (was Re: [PATCH v3 2/2] rbd: link and load librbd dynamically) Josh Durgin
2013-04-10 15:08 ` [Qemu-devel] [PATCH v3 2/2] rbd: link and load librbd dynamically Anthony Liguori
2013-04-10 21:19 ` Paolo Bonzini
2013-04-11 8:04 ` Stefan Hajnoczi
2013-04-11 7:59 ` Stefan Hajnoczi
2013-06-21 18:42 ` Sage Weil
2013-06-21 18:42 ` Sage Weil
2013-06-21 19:08 ` Alex Bligh
2013-06-21 19:08 ` [Qemu-devel] " Alex Bligh
2013-06-21 19:13 ` Anthony Liguori [this message]
2013-06-21 19:13 ` Anthony Liguori
2013-04-10 14:03 ` [Qemu-devel] [PATCH v2] rbd: add an asynchronous flush Josh Durgin
2013-04-11 8:02 ` Stefan Hajnoczi
2013-04-11 8:48 ` Kevin Wolf
2013-04-11 17:19 ` Josh Durgin
2013-04-12 6:50 ` Kevin Wolf
2013-04-12 7:42 ` Stefan Hajnoczi
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=87ppvfuvii.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sage@inktank.com \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.