From: Hollis Blanchard <hollisb@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEmu as a Device Software Optimization tool
Date: Thu, 26 Jul 2007 22:16:04 +0000 (UTC) [thread overview]
Message-ID: <f8b6f4$7om$1@sea.gmane.org> (raw)
In-Reply-To: fb249edb0707261200g7b492929j2d46c9d8875ab14a@mail.gmail.com
On Thu, 26 Jul 2007 21:00:31 +0200, andrzej zaborowski wrote:
>
> 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.
Really? Take a look at ppc_prep_init()...
I would love to see machine definition done in python.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2007-07-26 22:30 UTC|newest]
Thread overview: 11+ 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
2007-07-26 22:16 ` Hollis Blanchard [this message]
2007-07-27 9:46 ` [Qemu-devel] " 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 14:24 ` [Qemu-devel] " Brian Johnson
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='f8b6f4$7om$1@sea.gmane.org' \
--to=hollisb@us.ibm.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).