Re: [Qemu-devel] [PATCH 0/5] Add "info capabilities" monitor command

[Jamie Lokier <jamie@shareable.org>]

> (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
cpu=Fujitsu MB86900,Fujitsu MB86904,Fujitsu MB86907,LSI L64811,Cypress
CY7C601,Cypress CY7C611,TI SuperSparc II,TI MicroSparc I,TI MicroSparc
II,TI MicroSparc IIep,TI SuperSparc 40,TI SuperSparc 50,TI SuperSparc
51,TI SuperSparc 60,TI SuperSparc 61,Ross RT625,Ross RT620,BIT
B5010,Matsushita MN10501,Weitek W8601,LEON2,LEON3
etc...

> [machine]
> name=SS-5
> max_cpus=1
> nic_models=

This would be prettier as [machine:SS5] or [machine SS5] imho.

> [machine]
> name=Voyager
> max_cpus=0
> nic_models=

Crumbs, zero CPUs?

By the way, is there a min_cpus?  And does cpus mean cores or chips?
> drive_cache=off,none,writethrough,writeback

Do we need "off" and "none" here?

(Side issue: I think these names are misleading because they hide the
fact that "none" provides less underlying data integrity than
"writethrough", due to O_DIRECT vs. O_DSYNC quirks.  Sometimes you
want _both_ O_DIRECT and O_DSYNC, as they can be combined, and the
combination has a different meaning than O_DIRECT alone on some OSes
and hardware, including MS Windows.  So the options should be
"none,direct,writethrough,writeback").

-- Jamie