All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: DSO (dynamic shared objects) support
Date: Tue, 18 Jun 2013 15:19:34 -0500	[thread overview]
Message-ID: <20130618201934.GK31207@redhat.com> (raw)
In-Reply-To: <CA+aC4kt0w_zzHNgoTvHozf80NPkX9qPzdf4-RkVWVYfVhuTWSw@mail.gmail.com>

On Tue, Jun 18, 2013 at 07:42:11AM -0500, Anthony Liguori wrote:
> Hi,
> 
> On Tue, Jun 18, 2013 at 6:37 AM, Michael Tokarev <mjt@tls.msk.ru> wrote:
> > Hello.
> >
> > I looked at what's needed to support DSO (dynamic shared objects)
> > in qemu, in order to be able to split functionality into loadable
> > "plugins".  It isn't exactly difficult, but a few steps are needed
> > still.
> 
> As it turns out, this is an area of interest of mine too.  I put up a
> quick page describing some ideas a few weeks ago.
> 
> http://wiki.qemu.org/Features/Modules
> 
> > The whole thing is about splitting the functionality into plugins
> > from one, single, qemu build, for now, not about allowing 3rd-party
> > plugins to be distributed outside of qemu.
> 
> Ack.  Really critical and important distinction.

Agreed, if we introduce a module system to QEMU we should clearly
and explicitly document that closed source out of tree modules are
considered to be forbidden & a license violation. We should also
make use of any technical measures available to make out of tree
modules impratical to use. For example, use ELF symbol versioning
and make the version tags change on every single minor release so
you can't easily provide pre-compiled 3rd party modules. Obviously
don't install header files anywhere in /usr/include, etc

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 :|

  parent reply	other threads:[~2013-06-18 20:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 11:37 [Qemu-devel] RFC: DSO (dynamic shared objects) support Michael Tokarev
2013-06-18 12:05 ` Laszlo Ersek
2013-06-18 13:06   ` Paolo Bonzini
2013-06-18 12:17 ` Laszlo Ersek
2013-06-18 12:19   ` Michael Tokarev
2013-06-18 12:28     ` Michael Tokarev
2013-06-18 20:15   ` Daniel P. Berrange
2013-06-18 21:40     ` Richard Henderson
2013-06-18 12:42 ` Anthony Liguori
2013-06-18 13:12   ` Peter Maydell
2013-06-18 13:32     ` Paolo Bonzini
2013-06-18 13:13   ` Paolo Bonzini
2013-06-18 20:19   ` Daniel P. Berrange [this message]
2013-06-18 21:34     ` Peter Maydell
2013-06-18 19:35 ` Richard Henderson

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=20130618201934.GK31207@redhat.com \
    --to=berrange@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=mjt@tls.msk.ru \
    --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 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.