qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure toQEMU
Date: Mon, 11 May 2009 11:10:04 -0500	[thread overview]
Message-ID: <4A084DDC.1050506@us.ibm.com> (raw)
In-Reply-To: <4A0841F7.7000201@redhat.com>

Avi Kivity wrote:
>> There's also the issue that shared libraries imply it's OK for third 
>> parties to ship binary plugins.
>>   
>
> Can't we add wording to LICENSE to address this?  I'd really like to 
> allow GPL plugins.  Linux and now gcc allow this.

There's a lot of technical work to actually support shared libraries on 
all the platforms QEMU supports.  Even if we had that, and I expect a 
big flame war wrt reinventing autoconf here too, in order to 
realistically talk about plugins, we would need a much more modular 
infrastructure than we have today to allow a config file to specify a 
particular device without any core knowledge in QEMU of that device.

It's an admirable goal but we're far away from that.  When we eventually 
get there, we still have the issue of stable ABI (and Linux has this too).

So, I don't think this is a debate that we need to have now.  There's 
plenty of work to do before we get there :-)

-- 
Regards,

Anthony Liguori

  reply	other threads:[~2009-05-11 16:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 14:26 [Qemu-devel] [PATCH 0/4][RFC] Add module infrastructure to QEMU Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 1/4] " Anthony Liguori
2009-05-11 21:37   ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-11 21:53     ` Anthony Liguori
2009-05-11 21:53   ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-11 22:02     ` Anthony Liguori
2009-05-12  9:38       ` Gerd Hoffmann
2009-05-12 10:15         ` Paul Brook
2009-05-12 13:10         ` Anthony Liguori
     [not found]   ` <9EE414CC7AEE4488A45A263DE5B82EFE@jupiter>
2009-05-12 13:19     ` Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 2/4] Convert block infrastructure to use new module init functionality Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 3/4] Move block drivers into their own directory Anthony Liguori
2009-05-11 14:26 ` [Qemu-devel] [PATCH 4/4] Introduce global .config to selectively enable compile features Anthony Liguori
2009-05-11 15:22   ` Avi Kivity
2009-05-11 18:37     ` Anthony Liguori
2009-05-11 18:41       ` Avi Kivity
2009-05-11 14:48 ` [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU Paul Brook
2009-05-11 15:19   ` Avi Kivity
2009-05-11 16:10     ` Anthony Liguori [this message]
2009-05-11 16:45       ` [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure toQEMU Avi Kivity
2009-05-11 16:05   ` [Qemu-devel] Re: [PATCH 0/4][RFC] Add module infrastructure to QEMU Anthony Liguori
2009-05-11 16:16     ` Paul Brook
2009-05-11 16:20       ` Anthony Liguori
2009-05-11 16:43         ` Paul Brook
     [not found] ` <AEED36F4EA194EC2B57D5E4DB7D64896@jupiter>
2009-05-12 13:18   ` [Qemu-devel] " Anthony Liguori

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=4A084DDC.1050506@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=paul@codesourcery.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).