qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re[2]: [Qemu-devel] Config file support
Date: Tue, 24 Oct 2006 04:38:55 +0300	[thread overview]
Message-ID: <1893885600.20061024043855@gmail.com> (raw)
In-Reply-To: <200610240136.41311.paul@codesourcery.com>

Hello Paul,

Tuesday, October 24, 2006, 3:36:40 AM, you wrote:

> On Tuesday 24 October 2006 01:12, Paul Sokolovsky wrote:
>> Hello Paul,
>>
>> Monday, October 23, 2006, 11:29:52 PM, you wrote:
>> > On Monday 23 October 2006 21:01, Rob Landley wrote:
>> >> On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
>> >> > I've been considering a machine config file for a while, but haven't
>> >> > come up with a coherent way of representing everything yet.
>>
>>    I'm glad this discussion was brought up on the list. And I'd like
>> to also bring back another related issue - what about providing
>> "plugin" system for device (chip) implementation, in addition to
>> flexible-format machine config allowing to construct "virtual boards"
>> out of them?

> IMHO we already have a fairly good device model, and it's not hard to add new
> devices.

  Maybe. But where are new chips in qemu? Why there're still only 2
ARM boards? How do I "stick" wi-fi card in one of them? So the concern
is not just if it's easy to add new devices or not, but if there're means
to actually support appearance and growth of device library. Plugin system
would be a "decree" that there's a stable API to define devices and
welcome for 3rd-party developers to develop them.

  And well, patching source is not really that easy a way to "add new devices".

> If you mean putting individual devices in shared libraries and dlopen'ing them
> at runtime then I have no interest in that. AFAICS the only reason for
> wanting to do this is to use closed-source device models.

  This one I can really agree with - a plugin system would be not
a technical, but purely political and licensing issue. Someone will think
about close-source threat, and someone else - if a plugin system in qemu
will be taken by some company as a threat to their IP. I of course mean
Microsoft, who, I heard, patented all plugins.

> Paul


P.S. This is not a troll, but another qemu anecdote. I appreciate your
work and of course don't hold breath for plugins. Would be just good
to have a machine config along the lines of what you'd written in
another message.

-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com

  reply	other threads:[~2006-10-24  1:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 17:55 [Qemu-devel] Config file support Chuck Brazie
2006-10-21  0:12 ` Johannes Schindelin
2006-10-21 10:00   ` Ricardo Almeida
2006-10-21 11:40     ` Stefan Weil
2006-10-22  9:51     ` Johannes Schindelin
2006-10-22 17:01       ` Flavio Visentin
2006-10-22 17:19         ` Martin Guy
2006-10-22 18:27           ` Paul Brook
2006-10-23  6:33             ` [Qemu-devel] " Antti P Miettinen
2006-10-23 20:01             ` [Qemu-devel] " Rob Landley
2006-10-23 20:29               ` Paul Brook
2006-10-23 22:22                 ` Rob Landley
2006-10-23 23:33                   ` Paul Brook
2006-10-24  9:04                     ` Rob Landley
2006-10-24 10:47                     ` Flavio Visentin
2006-10-24 12:05                       ` Christian MICHON
2006-10-24 16:46                         ` Blue Swirl
2006-10-24 20:38                           ` Christian MICHON
2006-10-24 23:32                       ` Rob Landley
2006-10-25  8:20                         ` Johannes Schindelin
2006-10-24  0:11                   ` andrzej zaborowski
2006-10-24  0:34                     ` Paul Brook
2006-10-24  0:12                 ` Re[2]: " Paul Sokolovsky
2006-10-24  0:36                   ` Paul Brook
2006-10-24  1:38                     ` Paul Sokolovsky [this message]
2006-10-24  2:31                       ` Paul Brook
2006-10-24  8:37                         ` Christian MICHON
2006-10-24 23:28                       ` Rob Landley
2006-10-25  0:18                         ` Re[2]: " Paul Sokolovsky
2006-10-25 15:01                           ` Paul Brook
2006-10-26 14:31                             ` Rob Landley
2006-10-27 20:00                               ` Re[2]: " Paul Sokolovsky
2006-10-27 19:33                             ` Paul Sokolovsky
2006-10-28  0:08                               ` Paul Brook
2006-10-28  1:46                                 ` Re[2]: " Paul Sokolovsky
2006-10-24 23:28                   ` Rob Landley
2006-10-21 18:00   ` David Baird

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=1893885600.20061024043855@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=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 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).