From: Brian Johnson <bjj4@charter.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEmu as a Device Software Optimization tool
Date: Fri, 27 Jul 2007 09:24:43 -0500 [thread overview]
Message-ID: <f8cv7f$drt$1@sea.gmane.org> (raw)
In-Reply-To: <828800.95578.qm@web54107.mail.re2.yahoo.com>
n schembr wrote:
>
> -snap-
>
>> Personally though I don't see much benefit to simple syntax config
>> files over C files, that are being used now.
>
> Config files implies a self check process. A better question might
> be, has qemu grown to the point where an outsider is going to define
> a new platform?
Absolutely. I've been using it to prototype firmware for a NUMA
chipset. I've had to invent ugly command-line hacks for specifying the
number of nodes, per-node consoles, etc. And I still need to use a
debugger to override variable values in my init. code when I want to
test "odd" cases which my hacks don't support. I could make good use of
a generalized configuration file.
Brian
next prev parent reply other threads:[~2007-07-27 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 19:48 [Qemu-devel] QEmu as a Device Software Optimization tool n schembr
2007-07-27 9:25 ` Paul Borman
2007-07-28 15:55 ` Paul Sokolovsky
2007-07-27 14:24 ` Brian Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
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 19:00 ` andrzej zaborowski
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
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='f8cv7f$drt$1@sea.gmane.org' \
--to=bjj4@charter.net \
--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.