From: David Gibson <david@gibson.dropbear.id.au>
To: Laszlo Ersek <lersek@redhat.com>
Cc: peter.maydell@linaro.org, mst@redhat.com, marcel.a@redhat.com,
qemu-devel@nongnu.org, agraf@suse.de, pbonzini@redhat.com,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v2 0/2] list supported machine types in well-defined order
Date: Wed, 24 Sep 2014 10:51:35 +1000 [thread overview]
Message-ID: <20140924005135.GC24332@voom.redhat.com> (raw)
In-Reply-To: <1411418316-5169-1-git-send-email-lersek@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
On Mon, Sep 22, 2014 at 10:38:34PM +0200, Laszlo Ersek wrote:
> The first patch introduces a generic comparator. This comparator should
> cover all machine types at once that don't belong to machine type
> "families". Hence, for example, the output it produces for
>
> qemu-system-aarch64 -M \?
>
> is meant to be final. (See examples in the patches.)
>
> The second patch files piix and q35 machine types into their respective
> families.
>
> Paolo said we needed to care about "pseries, pc, q35", but I got no clue
> about "pseries", so I didn't touch that. It shouldn't be hard for
> someone who knows "pseries" to post a followup patch that covers it.
> Until then, "pseries" machine types are listed in alphabetical order (no
> families).
Acked-by: David Gibson <david@gibson.dropbear.id.au>
pseries is fairly simple; there are two pseries machine types, plain
"pseries" and "pseries-2.1". These should both be in the same family.
Implementation needs to be a little different than for PC, because the
pseries machines are fully QOM-ized so there are no QEMUMachine
structures any more. We'll need to set family from the *_class_init()
functions instead.
This is then complicated a little, because there's a pending patch in
agraf's tree which re-organizes the pseries machine types a ltitle.
After that there are still two pseries machine types, "pseries-2.1"
and "pseries-2.2" (aliased to "pseries"). Again, both should be in
the "pseries" family.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-24 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 20:38 [Qemu-devel] [PATCH v2 0/2] list supported machine types in well-defined order Laszlo Ersek
2014-09-22 20:38 ` [Qemu-devel] [PATCH v2 1/2] well-defined listing order for machine types Laszlo Ersek
2014-09-22 20:38 ` [Qemu-devel] [PATCH v2 2/2] i386/pc: add piix and q35 machtypes to sorting families for -M \? Laszlo Ersek
2014-09-22 21:31 ` [Qemu-devel] [PATCH v2 0/2] list supported machine types in well-defined order Paolo Bonzini
2014-09-23 4:43 ` Marcel Apfelbaum
2014-09-23 8:54 ` Michael S. Tsirkin
2014-09-24 0:51 ` David Gibson [this message]
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=20140924005135.GC24332@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=lersek@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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 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).