[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Sponsorship for QEMU Developers...

From: Leonardo E. Reiter
Subject: Re: [Qemu-devel] Sponsorship for QEMU Developers...
Date: Sat, 05 Mar 2005 17:27:39 -0500
User-agent: Debian Thunderbird 1.0 (X11/20050116)


here is an easy link to use:


oss stands for Open Source Software of course.

the qemu tarball is a CVS head snapshot from the 2/20/05; mergepro.patch gets applied to it to add our 3rd party stuff. Basically what we do is enable loading a dynamic shared object as a "plugin", and export symbols back and forth as needed by supplying pointers to them both in vl.c and in our plugin. We do not use any additional header files or anything like that in our closed source bits, since that would of course violate the GPL. We mainly did this so that we could "replace" the initialization of certain built-in peripherals in QEMU with our own proprietary versions that live in the plugin. To date, we replace the GUI ("display") and the IDE driver with our own home-grown versions. You will notice that all QEMU structures are passed in as void pointers back and forth, since we don't use any of the QEMU header files which define them. We instead get and set only the members we are interested in by address in our plugin.

Note that this is fairly temporary. We are working on making all of QEMU a shared library object itself, and adding accessors (get/set) for each QEMU structure type that are exported from the shared library. This would encapsulate the GPL'd code in a much cleaner way, and would let us avoid having to calculate addresses of members in our closed-source code when getting or setting data from structures.

Let me know if you have any additional questions.

Best regards,

Leo Reiter

Marc Collin wrote:

where we can get source code of qemu you use in Win4Lin Pro?


Leonardo E. Reiter
Vice President of Engineering

Win4Lin, Inc.
Virtual Computing from Desktop to Data Center
Main: +1 512 339 7979
Fax: +1 512 532 6501

reply via email to

[Prev in Thread] Current Thread [Next in Thread]