qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@xilinx.com>
To: qemu-devel@nongnu.org
Cc: alistair.francis@xilinx.com, alistair23@gmail.com,
	ehabkost@redhat.com, marcel@redhat.com
Subject: [Qemu-devel] [RFC v1 0/2]  Add a valid_cpu_types property
Date: Tue, 5 Sep 2017 17:11:58 -0700	[thread overview]
Message-ID: <cover.1504656490.git.alistair.francis@xilinx.com> (raw)

There are numorous QEMU machines that only have a single or a handful of
valid CPU options. To simplyfy the management of specificying which CPU
is/isn't valid let's create a property that can be set in the machine
init. We can then check to see if the user supplied CPU is in that list
or not.

This is just a quick setup, if this method is agreed apon I can add a
nice macro to add the valid CPU options (similar to SET_MACHINE_COMPAT)
and improve the error messages. I just wanted to get some input before I
spent too much time on that.

Alistair Francis (2):
  machine: Add a valid_cpu_types property
  netduino2: Specify the valid CPUs

 hw/arm/netduino2.c  |  5 +++++
 hw/core/machine.c   | 27 +++++++++++++++++++++++++++
 include/hw/boards.h |  1 +
 3 files changed, 33 insertions(+)

-- 
2.11.0

             reply	other threads:[~2017-09-06  0:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06  0:11 Alistair Francis [this message]
2017-09-06  0:12 ` [Qemu-devel] [RFC v1 1/2] machine: Add a valid_cpu_types property Alistair Francis
2017-09-09 20:16   ` Eduardo Habkost
2017-09-11 11:31     ` Igor Mammedov
2017-09-21 23:06     ` Alistair Francis
2017-09-06  0:12 ` [Qemu-devel] [RFC v1 2/2] netduino2: Specify the valid CPUs Alistair Francis
2017-09-11 11:56   ` KONRAD Frederic
2017-09-21 23:07     ` Alistair Francis
  -- strict thread matches above, loose matches on Subject: below --
2017-09-18 21:57 [Qemu-devel] [RFC PATCH] vl.c: add is_system_on_chip flag to force board default cpu Philippe Mathieu-Daudé
2017-09-18 22:55 ` [Qemu-devel] [RFC v1 0/2] Add a valid_cpu_types property Eduardo Habkost
2017-09-19  9:51   ` Philippe Mathieu-Daudé
2017-09-19 10:42     ` Eduardo Habkost

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=cover.1504656490.git.alistair.francis@xilinx.com \
    --to=alistair.francis@xilinx.com \
    --cc=alistair23@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=marcel@redhat.com \
    --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).