From: "Andreas Färber" <afaerber@suse.de>
To: Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, marcel.a@redhat.com, mst@redhat.com,
peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH 2/2] machine_parse(): list supported machine types in their registration order
Date: Mon, 22 Sep 2014 14:04:44 +0200 [thread overview]
Message-ID: <5420105C.2090701@suse.de> (raw)
In-Reply-To: <1411385195-13495-3-git-send-email-lersek@redhat.com>
Am 22.09.2014 um 13:26 schrieb Laszlo Ersek:
> Based on the registration order captured in the previous patch, we sort
> the ad-hoc list printed for
>
> qemu-system-XXXX -M \?
Agree that the order is worth sanitizing. I would however argue that
registration order is not entirely stable either if you think of non-PC
cases where there's dozens of source files registering one machine each.
I would therefore propose alphabetical order as we do for QOM'ified CPUs.
> The GLib documentation is not overly clear if g_slist_sort() allocates a
> new list or reorders the input list in place, but:
> - it slightly suggests the latter,
> - and there is prior use in qemu that is consistent with the latter:
> g_slist_sort() in qdev_print_devinfos() [qdev-monitor.c] sorts the
> return value of object_class_get_list() the same as we do here in
> machine_parse().
I believe I also assumed that for -cpu ? and/or QMP.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-09-22 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 11:26 [Qemu-devel] [PATCH 0/2] list supported machine types in their registration order Laszlo Ersek
2014-09-22 11:26 ` [Qemu-devel] [PATCH 1/2] save registration order of machine types Laszlo Ersek
2014-09-22 11:26 ` [Qemu-devel] [PATCH 2/2] machine_parse(): list supported machine types in their registration order Laszlo Ersek
2014-09-22 12:04 ` Andreas Färber [this message]
2014-09-22 12:26 ` Michael S. Tsirkin
2014-09-22 12:29 ` Laszlo Ersek
2014-09-22 12:36 ` Michael S. Tsirkin
2014-09-22 12:50 ` Marcel Apfelbaum
2014-09-22 13:43 ` Laszlo Ersek
2014-09-22 15:07 ` Marcel Apfelbaum
2014-09-22 13:15 ` Laszlo Ersek
2014-09-22 15:57 ` Paolo Bonzini
2014-09-22 16:06 ` Andreas Färber
2014-09-22 16:17 ` Paolo Bonzini
2014-09-22 16:13 ` Laszlo Ersek
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=5420105C.2090701@suse.de \
--to=afaerber@suse.de \
--cc=lersek@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@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 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.