qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEmu as a Device Software Optimization tool
Date: Thu, 26 Jul 2007 21:00:31 +0200	[thread overview]
Message-ID: <fb249edb0707261200g7b492929j2d46c9d8875ab14a@mail.gmail.com> (raw)
In-Reply-To: <E0BE420D-5F03-4DF5-8E82-E8B29643AA6A@windriver.com>

Hi,

On 26/07/07, Paul Borman <paul.borman@windriver.com> wrote:
> QEmu Target Configuration - I would like to define a configuration
> file syntax (I cannot help but think back to my BSDi days and the BSD/
> OS kernel configuration file) that would define the hardware from the
> outside.  Device drivers would either need to be already linked in,
> or be able to be dynamically loaded.  I would expect that things such
> as the memory map, type of interrupt controller, the various devices
> along with their io port and memory addresses and interrupts would be
> defined here.  Again, this would not replace the current system, but
> would essentially be a new init module.  I do not want to see any
> working configurations break.

There is some interesting work being done on a similar project by Paul
Sokolovsky for his and Maria Zabolotnaya's Google Summer Of Project.
In their approach machine descriptions (but not only) are written in
python, which lets you hope that they can have a simple syntax,
practically like a config file, if desired, or a much more powerful
one, so it seems to be a better idea than plain config files.

Personally though I don't see much benefit to simple syntax config
files over C files, that are being used now.
Regards

  parent reply	other threads:[~2007-07-26 19:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 14:58 [Qemu-devel] Patch for OHW bootinfos Tero Kaarlela
2007-07-26 16:34 ` [Qemu-devel] QEmu as a Device Software Optimization tool Paul Borman
2007-07-26 16:58   ` Thiemo Seufer
2007-07-26 17:33   ` Even Rouault
2007-07-26 19:00   ` andrzej zaborowski [this message]
2007-07-26 22:16     ` [Qemu-devel] " Hollis Blanchard
2007-07-27  9:46       ` Paul Borman
2007-07-27 11:12         ` Alexander Voropay
2007-07-27 22:54         ` andrzej zaborowski
2007-07-28 16:54         ` Paul Sokolovsky
  -- strict thread matches above, loose matches on Subject: below --
2007-07-26 19:48 [Qemu-devel] " n schembr
2007-07-27  9:25 ` Paul Borman
2007-07-28 15:55   ` Paul Sokolovsky

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=fb249edb0707261200g7b492929j2d46c9d8875ab14a@mail.gmail.com \
    --to=balrogg@gmail.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).