All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unified device model
Date: Sun, 9 Apr 2006 11:38:28 +0100	[thread overview]
Message-ID: <200604091138.31242.paul@codesourcery.com> (raw)
In-Reply-To: <E1FSSRx-0004OR-Eg@lists.gnu.org>

> >>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 always could consider to add simple modules C++ to QEMU or build C++
> device -> C device interface bridge ...

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 
valid C++. You could also write C++ wrappers round the interface for bochs to 
use.

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. I can't see 
any good reasons why open source devices would need to be broken out into a 
separate shared library.

If you do want to accommodate proprietary binary plugins then C++ is a really 
bad idea. The C++/libstdc++ ABI simply isn't stable enough to make this a 
realistic option.

Paul

  reply	other threads:[~2006-04-09 10:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 19:57 [Qemu-devel] Unified device model Stanislav Shwartsman
2006-04-08 19:12 ` 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 [this message]
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=200604091138.31242.paul@codesourcery.com \
    --to=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.