From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH]Get machine name from name of executable
Date: Sun, 14 May 2006 15:30:22 +0200 [thread overview]
Message-ID: <446730EE.8050008@mail.berlios.de> (raw)
In-Reply-To: <446718F4.9080400@bellard.org>
Hi,
ok, I think this plan is a good one. It might even be possible to run
several different machines by
starting a single QEMU emulation process. But you need some mechanism to
tell QEMU which machine(s) to run.
Of course, you could add new command line options. MIPS, for example,
could select endianness
automatically in user mode (from ELF format), but not in system mode
when running a complete system
with a firmware loader. So you need some way to tell QEMU that this is a
MIPS CPU with a certain kind
of endianness (the real CPU has a hardware input pin for this, we need
something which replaces this
hardware input pin).
Did you think about using configuration files (XML, YAML, or any other
format) with machine descriptions
(CPU, CPU variant, endianness, network hardware, serial ports, other
hardware features which are
compiled into the code or configured via command line options today)?
Regards
Stefan
Fabrice Bellard schrieb:
> Hi,
>
> The long term plan for qemu is to have a single executable for all
> machines. If you make a single executable for mips and mipsel, it is
> better to select the endianness in the code of the machine itself when
> initializing the CPU.
>
> Regards,
>
> Fabrice.
next prev parent reply other threads:[~2006-05-14 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 10:42 [Qemu-devel][PATCH]Get machine name from name of executable Stefan Weil
2006-05-14 11:34 ` Thiemo Seufer
2006-05-14 11:48 ` Fabrice Bellard
2006-05-14 13:30 ` Stefan Weil [this message]
2006-05-14 18:03 ` Fabrice Bellard
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=446730EE.8050008@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).