From: Marcel Apfelbaum <marcel.a@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: peter.maydell@linaro.org, mst@redhat.com, qemu-devel@nongnu.org,
pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v2 0/2] list supported machine types in well-defined order
Date: Tue, 23 Sep 2014 07:43:48 +0300 [thread overview]
Message-ID: <1411447428.3666.116.camel@localhost.localdomain> (raw)
In-Reply-To: <1411418316-5169-1-git-send-email-lersek@redhat.com>
On Mon, 2014-09-22 at 22:38 +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).
>
> Laszlo Ersek (2):
> well-defined listing order for machine types
> i386/pc: add piix and q35 machtypes to sorting families for -M \?
>
> include/hw/boards.h | 2 ++
> hw/i386/pc.c | 1 +
> hw/i386/pc_piix.c | 1 +
> hw/i386/pc_q35.c | 1 +
> vl.c | 38 +++++++++++++++++++++++++++++++++++++-
> 5 files changed, 42 insertions(+), 1 deletion(-)
>
Looks good to me.
Reviewed-by: Marcel Apfelbaum <marcel.a@redhat.com>
Discussion only:
1. Adding the family field to machine options mechanism does
leverage the machines hierarchy, but in another way and not through QOM.
2. The compare function looks exactly as I thought it would, my only difference
was to take it a little further by let the family itself to sort its
machines, but *is completely unnecessary* for this purpose.
Your solution has a small footprint and I like it.
Thanks,
Marcel
next prev parent reply other threads:[~2014-09-23 4:44 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 [this message]
2014-09-23 8:54 ` Michael S. Tsirkin
2014-09-24 0:51 ` David Gibson
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=1411447428.3666.116.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=lersek@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).