From: Mark McLoughlin <markmc@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/5] Add "info capabilities" monitor command
Date: Fri, 14 Nov 2008 16:09:07 +0000 [thread overview]
Message-ID: <1226678947.9332.104.camel@blaa> (raw)
In-Reply-To: <20081114025052.GG2055@shareable.org>
On Fri, 2008-11-14 at 02:50 +0000, Jamie Lokier wrote:
> > (qemu) info capabilities
> > [qemu]
> > accel=
> > arch=sparc
>
> I'm thinking that a qemu which supports multiple target architectures
> becomes increasingly feasible and likely, especially for system
> emulation. Therefore, [qemu] should have an "archs" property, and
> there should be separate "[arch-sparc]" headers, like this:
>
> [qemu]
> archs=sparc
>
> [arch]
> name=sparc
Yep, that sounds sensible.
> > [machine]
> > name=SS-5
> > max_cpus=1
> > nic_models=
>
> This would be prettier as [machine:SS5] or [machine SS5] imho.
I'd considered that but thought it would be ugly - now that you actually
type it out though, [machine foo] looks fine :-)
> > [machine]
> > name=Voyager
> > max_cpus=0
> > nic_models=
>
> Crumbs, zero CPUs?
Ah, vl.c has:
machine->max_cpus = machine->max_cpus ?: 1; /* Default to UP */
I guess it should do that for all machines, not just the selected one.
> > drive_cache=off,none,writethrough,writeback
>
> Do we need "off" and "none" here?
"none" - yes, I think so.
"off" - probably not, it's deprecated I guess.
Cheers,
Mark.
next prev parent reply other threads:[~2008-11-14 16:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 16:45 [Qemu-devel] [PATCH 0/5] Add "info capabilities" monitor command Mark McLoughlin
2008-11-13 16:45 ` [Qemu-devel] [PATCH 1/5] Re-factor nic model listing Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 2/5] Add cpu_list() for any targets that don't already have it Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 3/5] Rename xxx_cpu_list() to cpu_xxx_list() Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 4/5] Add new cpu_names() function Mark McLoughlin
2008-11-13 16:46 ` [Qemu-devel] [PATCH 5/5] monitor: add "info capabilities" command Mark McLoughlin
2008-11-13 19:50 ` [Qemu-devel] " Anthony Liguori
2008-11-14 16:02 ` Mark McLoughlin
2008-11-14 10:07 ` [Qemu-devel] " Avi Kivity
2008-11-14 15:58 ` Mark McLoughlin
2008-11-16 7:17 ` Avi Kivity
2008-11-14 10:13 ` Daniel P. Berrange
2008-11-13 19:47 ` [Qemu-devel] Re: [PATCH 4/5] Add new cpu_names() function Anthony Liguori
2008-11-14 15:36 ` Mark McLoughlin
2008-11-13 18:35 ` [Qemu-devel] [PATCH 1/5] Re-factor nic model listing Paul Brook
2008-11-13 19:45 ` Anthony Liguori
2008-11-13 22:50 ` Paul Brook
2008-11-14 2:31 ` Jamie Lokier
2008-11-14 2:49 ` Anthony Liguori
2008-11-13 19:44 ` [Qemu-devel] " Anthony Liguori
2008-11-14 15:34 ` Mark McLoughlin
2008-11-13 17:49 ` [Qemu-devel] [PATCH 0/5] Add "info capabilities" monitor command Blue Swirl
2008-11-14 2:50 ` Jamie Lokier
2008-11-14 16:09 ` Mark McLoughlin [this message]
2008-11-14 3:28 ` [Qemu-devel] " Anthony Liguori
2008-11-14 3:51 ` Jamie Lokier
2008-11-14 15:56 ` Mark McLoughlin
2008-11-14 22:54 ` Jamie Lokier
2008-11-14 15:51 ` Mark McLoughlin
2008-11-14 22:52 ` Jamie Lokier
2008-11-14 10:16 ` [Qemu-devel] " Daniel P. Berrange
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=1226678947.9332.104.camel@blaa \
--to=markmc@redhat.com \
--cc=jamie@shareable.org \
--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.