[Top][All Lists]

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

RE: [Qemu-devel] Unified device model

From: Stanislav Shwartsman
Subject: RE: [Qemu-devel] Unified device model
Date: Sun, 9 Apr 2006 08:29:32 +0200

Currently Bochs plugins APCI already begins with such C-language bindings.
But inside the device is C++ based and derives from Bochs device model. It
has the same log writer and debugging interface as any other Bochs module
but nothing more.

Could you look into the Bochs devices code and plugin code, I think you
could say how much it is compatible fro QEMU and if there is something that
we should consider to change ...


-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Leonardo E. Reiter
Sent: Saturday, April 08, 2006 9:27 PM
To: address@hidden
Subject: Re: [Qemu-devel] Unified device model

Well, not completely impossible, but it would require some really ugly 
"glue" code.  And, the glue would have to happen outside of QEMU (i.e. 
like in the BOCHS code), to keep C++ out of QEMU.

To have a truly portable API, it should definitely have C language 
"bindings".  I'm sure this could be added to the BOCHS implementation 
somehow if this is important.

- Leo Reiter

Johannes Schindelin wrote:
> IIRC bochs does it in C++. Which makes it rather impossible to share code 
> :-(
> Ciao,
> Dscho

Leonardo E. Reiter
Vice President of Product Development, CTO

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

Qemu-devel mailing list

reply via email to

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