From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU configuration files
Date: Thu, 19 Jun 2008 01:01:24 +0100 [thread overview]
Message-ID: <200806190101.25295.paul@codesourcery.com> (raw)
In-Reply-To: <200806190049.37955.paul@codesourcery.com>
[I apparently missed out a paragraph from my first mail, so the paragraph
quoted below didn't make a whole lot of sense.]
One issue is whether/how much it's desirable to decouple the emulated hardware
configuration from the host interface configuration. e.g. should we always
create N serial ports, regardless of how many -serial options are specified.
> This is maybe slightly different between emulating embedded boards and
> workstation/server class machines. For workstation/server emulation it's
> entirely reasonable to arbitrarily add/remove serial and network devices
> from a "PC" machine based on the user config. For embedded SoC devices you
> tend to want to emulate a fixed number of devices (matching those present
> on real hardware) and leave them present but disconnected if the user does
> not specify appropriate net/serial options.
Paul
next prev parent reply other threads:[~2008-06-19 0:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 18:12 [Qemu-devel] QEMU configuration files Fabrice Bellard
2008-06-18 19:16 ` [Qemu-devel] " Sebastian Herbszt
2008-06-18 21:08 ` [Qemu-devel] " Anthony Liguori
2008-06-18 23:49 ` Paul Brook
2008-06-19 0:01 ` Paul Brook [this message]
2008-06-19 9:46 ` Fabrice Bellard
2008-06-19 11:40 ` Daniel P. Berrange
2008-06-19 11:52 ` Fabrice Bellard
2008-06-19 14:36 ` Daniel P. Berrange
2008-06-19 11:56 ` [Qemu-devel] " Sebastian Herbszt
2008-06-20 13:11 ` Fabrice Bellard
2008-06-21 8:43 ` Blue Swirl
2008-06-24 15:50 ` [Qemu-devel] " Ian Jackson
2008-06-24 19:50 ` Jamie Lokier
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=200806190101.25295.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 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).