qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Stanislav Shwartsman" <stl@fidonet.org.il>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Unified device model
Date: Sat, 8 Apr 2006 21:57:10 +0200	[thread overview]
Message-ID: <E1FSIdM-0002h4-18@lists.gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]

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 same devices.

If one of the teams fixes the implementation or add functionality, another
team mostly copy-paste the changes to their model.

Xen project forked from QEMU and want to stay in touch with Bochs and QEMU
device models and contribute the changes to make the model better.

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 know about two professional teams working in simulation which would like
to use these device models in their simulator and 

could enrich the device library with new devices device interfaces, for
example with AGP and 3D graphics.

Bochs is already in middle of definition of new true pluginable devices
architecture. 

In near future Bochs devices will fully separatable from Bochs binary and
when could be developed separately from Bochs.

I call to QEMU developers join to this project and come with their
requirements to plugin architecture.

I don't know if QEMU supports device plugins now but I would like to see
QEMU a part of this idea, 

I would like to get single device shared library which could be loaded to
Bochs and QEMU and work perfectly for both.

This will eliminate the need to maintain two separate implementations of the
same devices, 

these implementations very fast will converge to single one, C or C++ based,
Bochs or QEMU based, doesn't matter.

I am listening for your opinions !

 

Thanks,

Stanislav


[-- Attachment #2: Type: text/html, Size: 5766 bytes --]

             reply	other threads:[~2006-04-08 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 19:57 Stanislav Shwartsman [this message]
2006-04-08 19:12 ` [Qemu-devel] Unified device model Jim C. Brown
2006-04-08 19:17   ` Johannes Schindelin
2006-04-08 19:27     ` Leonardo E. Reiter
2006-04-09  6:29       ` Stanislav Shwartsman
2006-04-08 19:28     ` Jim C. Brown
2006-04-09  6:26   ` Stanislav Shwartsman
2006-04-09 10:38     ` Paul Brook
2006-04-09 14:55       ` Jim C. Brown
2006-04-09 15:21         ` Paul Brook
2006-04-09 15:28           ` Sam Barnett-Cormack
2006-04-09 16:08           ` Jim C. Brown
2006-04-09 19:56             ` Stanislav Shwartsman
2006-04-09 21:02               ` Fabrice Bellard
2006-04-09 15:10     ` Jim C. Brown
     [not found] <1b33de610604170003q43b6c453ub94d77b1a10ed43b@mail.gmail.com>
2006-04-17  7:09 ` pete sullivan
  -- strict thread matches above, loose matches on Subject: below --
2006-04-23 21:03 Einar Larsson

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=E1FSIdM-0002h4-18@lists.gnu.org \
    --to=stl@fidonet.org.il \
    --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).