From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Config file support
Date: Mon, 23 Oct 2006 21:29:52 +0100 [thread overview]
Message-ID: <200610232129.53615.paul@codesourcery.com> (raw)
In-Reply-To: <200610231601.44583.rob@landley.net>
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.
>
> Do you at least have a list of everything that needs to be represented? (I
> have a list but am fairly certain it's not complete.)
Not really. I guess a generic key/value pair is sufficient for most things
(base address, model number, etc).
The trickier cases are where devices refer to each other: PCI, usb, IRQ lines,
DMA channels, etc. ie. anything where the existing _init function returns a
value.
I guess you could use the same key/value mechanism, and allow the value to be
an "object".
The really OTT method is to embed a python interpreter or something and do the
machine init that way. I'm not seriously suggesting that though.
Paul
next prev parent reply other threads:[~2006-10-23 20:30 UTC|newest]
Thread overview: 50+ 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 [this message]
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 ` Re[2]: " Paul Sokolovsky
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
[not found] ` <20061025153503.GB5673@aon.at>
2006-10-28 22:24 ` busybox "ps ax" woes, was: " Paul Sokolovsky
2006-10-24 23:28 ` Rob Landley
2006-10-21 18:00 ` David Baird
-- strict thread matches above, loose matches on Subject: below --
2006-10-23 18:25 [Qemu-devel] config " Ben Taylor
2006-10-18 18:42 Chuck Brazie
2006-10-22 21:51 ` Rob Landley
2006-10-23 10:58 ` Christian MICHON
2006-10-23 11:48 ` Jan Marten Simons
2006-10-23 12:24 ` Paul Brook
2006-10-23 17:50 ` K. Richard Pixley
2006-10-23 20:39 ` Rob Landley
2006-10-23 20:58 ` Paul Brook
2006-10-23 21:01 ` K. Richard Pixley
2006-10-23 21:17 ` M. Warner Losh
2006-10-23 20:42 ` André Braga
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=200610232129.53615.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.