From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Modular qemu?
Date: Fri, 5 Dec 2008 23:10:07 +0100 [thread overview]
Message-ID: <20081205221007.GB25555@edgar.se.axis.com> (raw)
In-Reply-To: <49393B8D.40209@codemonkey.ws>
On Fri, Dec 05, 2008 at 08:32:45AM -0600, Anthony Liguori wrote:
> Joop Boonen wrote:
>> Hello All,
>>
>> I'm wondering if a modular qemu would be an option (loadable modules)?
>> Currently a lot different patched versions of qemu are around.
>> qemu as provided from the qemu project
>> qemu for openmoko wiki.openmoko.org
>> qemu for coreboot.org
>> and probably others.
>>
>> If it would be possible t load modules like the (linux)kernel it would be
>> possible to use one qemu version for all the projects.
>> I don't know if this is possible?
>>
>
> This has been discussed before and I believe the overall consensus was that
> plugins are not desirable.
>
> With respect to the various forks of QEMU, I believe the real problem is
> that historically, people have had a tough time getting changes into QEMU.
> This is not just a matter of getting patches accepted, but also getting the
> appropriate guidance about how to refactor things to take into account all
> of the various architecture combinations that QEMU supports and some of the
> longer term efforts.
>
> I hope this situation is improving. If people have feedback in how things
In general I think the situation has improved alot. Personally I think
the work that in particular Anthony (others too) is doing with reviewing
and applying patches is just fantastic.
> could be improved, I think everyone is eager to here it. Plugins are not
> the solution though.
Personnaly I would welcome some kind of plugin interface for some parts of
QEMU but only if someone comes up wiht a an interface that does not hurt
performace. I'd definitely have a use to plugin callbacks for every memory
accesse in system-mode and I've noticed a reocurring request for hooks to
trap syscalls while user-mode emulating.
Best regards
Edgar
next prev parent reply other threads:[~2008-12-05 22:10 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
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 [this message]
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=20081205221007.GB25555@edgar.se.axis.com \
--to=edgar.iglesias@axis.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).