From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Modular qemu?
Date: Fri, 05 Dec 2008 20:19:37 +0200 [thread overview]
Message-ID: <493970B9.3060807@redhat.com> (raw)
In-Reply-To: <49393B8D.40209@codemonkey.ws>
Anthony Liguori wrote:
> Plugins are not the solution though.
What about non-plugin dlopen()? Right now building qemu (with all
options enabled) requires a large amount of libraries, hence a lot of
dependencies. For example, a server setup that will only be used with
-vnc needs to have SDL installed. This will only get worse with opengl
support.
I'm thinking of something similar to linux kernel modules: no backward
compatible ABI, simply load-on-demand functionality that can be packaged
separately to reduce dependencies. With kvm integrated, we could even
make the cpu emulator an optional loadable module.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-12-05 18:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 10:53 [Qemu-devel] Modular qemu? Joop Boonen
2008-12-05 12:40 ` Carl-Daniel Hailfinger
2008-12-05 14:32 ` Anthony Liguori
2008-12-05 14:52 ` Laurent Desnogues
2008-12-05 15:07 ` Glauber Costa
2008-12-05 15:29 ` Anthony Liguori
2008-12-05 15:25 ` Anthony Liguori
2008-12-05 18:19 ` Avi Kivity [this message]
2008-12-05 18:54 ` Thiemo Seufer
2008-12-05 19:02 ` Avi Kivity
2008-12-05 19:27 ` Anthony Liguori
2008-12-05 19:37 ` Avi Kivity
2008-12-05 19:58 ` Anthony Liguori
2008-12-05 18:56 ` [Qemu-devel] " Jan Kiszka
2008-12-05 18:57 ` [Qemu-devel] " Anthony Liguori
2008-12-05 19:12 ` Avi Kivity
2008-12-09 13:06 ` Jun Koi
2008-12-09 13:17 ` Stefano Stabellini
2008-12-09 13:44 ` Avi Kivity
2008-12-05 22:10 ` Edgar E. Iglesias
2008-12-06 13:23 ` Lionel Landwerlin
2008-12-08 10:15 ` Stefano Stabellini
2008-12-17 13:34 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2008-12-08 23:58 Salvatore Lionetti
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=493970B9.3060807@redhat.com \
--to=avi@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.