From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: pbonzini@redhat.com, Laszlo Ersek <lersek@redhat.com>,
hch@lst.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/7] introduce BSD-licensed block driver for "raw"
Date: Fri, 16 Aug 2013 16:06:55 +0100 [thread overview]
Message-ID: <20130816150655.GU22602@redhat.com> (raw)
In-Reply-To: <874napfzr8.fsf@codemonkey.ws>
On Fri, Aug 16, 2013 at 09:59:07AM -0500, Anthony Liguori wrote:
> Laszlo Ersek <lersek@redhat.com> writes:
>
> > Paolo asked me to write such a driver based on his textual specification
> > alone. The first patch captures his email in full, the rest re-quotes
> > parts that are being implemented.
> >
> > The tree compiles at each patch. The series passes "make check-block".
> >
> > "block/raw.c" is not removed because I wanted to keep it out of my
> > series and out of my brain.
> >
> > Disclaimer: I couldn't care less if the raw block driver was public
> > domain or AGPLv3+, as long as it qualifies as free software. I'm only
> > trying to do what Paolo asked of me.
>
> Generally speaking, rewriting parts of QEMU to be !GPL is something I
> would strongly, strongly oppose.
>
> I believe that Paolo had a good reason for this though. I suppose the
> logic is that we want to expose a "libqemublock" that libvirt can use such
> that it can stop parsing qcow2 files.
>
> Now libvirt just needs LGPLv2+, right?
LGPLv2+ is fine, but regardless of license, libvirt won't use any
libqemublock.so library as long as it links to glib with abort on
OOM behaviour.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2013-08-16 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 14:15 [Qemu-devel] [PATCH 0/7] introduce BSD-licensed block driver for "raw" Laszlo Ersek
2013-08-16 14:15 ` [Qemu-devel] [PATCH 1/7] add skeleton for BSD licensed "raw" BlockDriver Laszlo Ersek
2013-08-16 14:15 ` [Qemu-devel] [PATCH 2/7] raw_bsd: emit debug events in bdrv_co_readv() and bdrv_co_writev() Laszlo Ersek
2013-08-16 14:15 ` [Qemu-devel] [PATCH 3/7] raw_bsd: add raw_create() Laszlo Ersek
2013-08-16 14:15 ` [Qemu-devel] [PATCH 4/7] raw_bsd: introduce "special members" Laszlo Ersek
2013-08-20 8:11 ` Kevin Wolf
2013-08-16 14:15 ` [Qemu-devel] [PATCH 5/7] raw_bsd: add raw_create_options Laszlo Ersek
2013-08-16 14:15 ` [Qemu-devel] [PATCH 6/7] raw_bsd: register bdrv_raw Laszlo Ersek
2013-08-16 14:15 ` [Qemu-devel] [PATCH 7/7] switch raw block driver from "raw.o" to "raw_bsd.o" Laszlo Ersek
2013-08-18 14:29 ` Paolo Bonzini
2013-08-20 7:51 ` Kevin Wolf
2013-08-16 14:59 ` [Qemu-devel] [PATCH 0/7] introduce BSD-licensed block driver for "raw" Anthony Liguori
2013-08-16 15:06 ` Daniel P. Berrange [this message]
2013-08-18 14:25 ` Paolo Bonzini
2013-08-19 16:24 ` Laszlo Ersek
2013-08-20 8:21 ` Kevin Wolf
2013-08-21 8:20 ` Laszlo Ersek
2013-08-21 9:03 ` Paolo Bonzini
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=20130816150655.GU22602@redhat.com \
--to=berrange@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=hch@lst.de \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--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).