I think that a device model with support for devices in shared libraries combined with dynamic definition of the simulated HW would be great to be able to support a large number of HW variants in QEmu. I have developed several full system simulators for large embedded systems, and we have always en
Hi
I have been following the discussion about some more dynamic way to configure and define a simulation set-up
for Qemu. If You want to attract others than hard core developers, I think that an unified device model is
something to aim for. With a generic device model I think you open up a sea
m: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim
C. Brown
Sent: Sunday, April 09, 2006 6:08 PM
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unified device model
On Sun, Apr 09, 2006 at 04:21:42PM +0100, Paul Brook wrote:
I'm not a fan of binary plugins (for the same re
Bochs 2.3 release.
Thanks,
Stanislav
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim
C. Brown
Sent: Sunday, April 09, 2006 6:08 PM
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unified device model
On Sun, Apr 09, 2006 at 04:21:42PM +0100, Paul Brook wrote:
On Sun, Apr 09, 2006 at 04:21:42PM +0100, Paul Brook wrote:
> > > I'm not a fan of binary plugins (for the same reasons I'm don't like
> > > binary kernel modules), and don't think there's any real need to them.
> >
> > A binary plugin API and a source plugin API (one that requires each driver
> >
Paul Brook wrote:
I don't buy that. We either share the same drivers (in which case keeping the
two in sync is trivial) or we don't. All of the systems under consideration
are [L]GPL licences. We can easily copy the source, so I don't think being
able to copy bits of binary goo gains us anythi
> > I'm not a fan of binary plugins (for the same reasons I'm don't like
> > binary kernel modules), and don't think there's any real need to them.
>
> A binary plugin API and a source plugin API (one that requires each driver
> device to be recompiled for each of the platforms (Xen, qemu, bochs, e
On Sun, Apr 09, 2006 at 08:26:11AM +0200, Stanislav Shwartsman wrote:
> I am talking about the device models only. Inside CPU emulation QEMU, Bochs
> and Xen are completely different, but they use the same devices for full
> system emulation and they most likely want to move forward together.
I ha
On Sun, Apr 09, 2006 at 11:38:28AM +0100, Paul Brook wrote:
> I think to be acceptable to qemu (and probably also for Xen) the devices
> would
> have to be written in C. C++ is more pain that it's worth in this context.
> Of course there's no reason why we couldn't use the subset of C that's also
> >>I am wondering about making unified device models architecture for open
> >>source simulators.
> >>The device models will be used in QEMU, Bochs, Xen and other open source
> >>simulators which would use the device models.
> >
> >I would support this idea, if it was possible.
>
> Why not ?
> You
@nongnu.org
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,
Hi again,
>>It is not a secret that all open source emulators (QEMU, Bochs, Xen) use
>>the same emulated devices and mostly copy-paste their emulation one from
>>another.
>While from my understanding Xen uses qemu's hardware emulation for it's VT
>support, this is not really true otherwise.
>Th
On Sat, Apr 08, 2006 at 09:17:52PM +0200, Johannes Schindelin wrote:
> IIRC bochs does it in C++. Which makes it rather impossible to share code
> :-(
>
> Ciao,
> Dscho
>
This is why I guessed qemu was a rewrite-from-scratch - C++ code is forbidden
in qemu.
Fortunately this does not prevent a
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
Hi,
On Sat, 8 Apr 2006, Jim C. Brown wrote:
> On Sat, Apr 08, 2006 at 09:57:10PM +0200, Stanislav Shwartsman wrote:
> >
> > It is not a secret that all open source emulators (QEMU, Bochs, Xen) use the
> > same emulated devices and mostly copy-paste their emulation one from
> > another.
>
> Whil
On Sat, Apr 08, 2006 at 09:57:10PM +0200, Stanislav Shwartsman wrote:
> Hello All,
>
>
>
> It is not a secret that all open source emulators (QEMU, Bochs, Xen) use the
> same emulated devices and mostly copy-paste their emulation one from
> another.
While from my understanding Xen uses qemu's
Hello All,
It is not a secret that all open source emulators
(QEMU, Bochs, Xen) use the same emulated devices and mostly copy-paste their
emulation one from another.
I don’t know who originally wrote the device models
but now Bochs and QEMU maintain two similar implementations of the s
17 matches
Mail list logo
