qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org, marcel.a@redhat.com, afaerber@suse.de,
	mst@redhat.com, peter.maydell@linaro.org, pbonzini@redhat.com,
	lersek@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] list supported machine types in well-defined order
Date: Mon, 22 Sep 2014 22:38:34 +0200	[thread overview]
Message-ID: <1411418316-5169-1-git-send-email-lersek@redhat.com> (raw)

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(-)

-- 
1.8.3.1

             reply	other threads:[~2014-09-22 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 20:38 Laszlo Ersek [this message]
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

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=1411418316-5169-1-git-send-email-lersek@redhat.com \
    --to=lersek@redhat.com \
    --cc=afaerber@suse.de \
    --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).