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, imammedo@redhat.com,
f4bug@amsat.org
Subject: [Qemu-devel] [PATCH v3 0/5] Add a valid_cpu_types property
Date: Tue, 17 Oct 2017 15:31:09 -0700 [thread overview]
Message-ID: <cover.1508279421.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.
I have added the valid_cpu_types for some ARM machines only at the
moment.
Here is what specifying the CPUs looks like now:
$ aarch64-softmmu/qemu-system-aarch64 -M netduino2 -kernel ./u-boot.elf -nographic -cpu "cortex-m3" -S
QEMU 2.10.50 monitor - type 'help' for more information
(qemu) info cpus
* CPU #0: thread_id=24175
(qemu) q
$ aarch64-softmmu/qemu-system-aarch64 -M netduino2 -kernel ./u-boot.elf -nographic -cpu "cortex-m4" -S
QEMU 2.10.50 monitor - type 'help' for more information
(qemu) q
$ aarch64-softmmu/qemu-system-aarch64 -M netduino2 -kernel ./u-boot.elf -nographic -cpu "cortex-m5" -S
qemu-system-aarch64: unable to find CPU model 'cortex-m5'
$ aarch64-softmmu/qemu-system-aarch64 -M netduino2 -kernel ./u-boot.elf -nographic -cpu "cortex-a9" -S
qemu-system-aarch64: Invalid CPU type: cortex-a9-arm-cpu
The valid types are: cortex-m3-arm-cpu, cortex-m4-arm-cpu
V3:
- Make the varialbes static
V2:
- Rebase
- Reorder patches
- Add a Raspberry Pi 2 CPU fix
V1:
- Small fixes to prepare a series instead of RFC
- Add commit messages for the commits
- Expand the machine support to ARM machines
RFC v2:
- Rebase on Igor's work
- Use more QEMUisms inside the code
- List the supported machines in a NULL terminated array
Alistair Francis (5):
netduino2: Specify the valid CPUs
bcm2836: Use the Cortex-A7 instead of Cortex-A15
raspi: Specify the valid CPUs
xlnx-zcu102: Specify the valid CPUs
xilinx_zynq: Specify the valid CPUs
hw/arm/bcm2836.c | 2 +-
hw/arm/netduino2.c | 10 +++++++++-
hw/arm/raspi.c | 7 +++++++
hw/arm/xilinx_zynq.c | 6 ++++++
hw/arm/xlnx-zcu102.c | 17 +++++++++++++++++
5 files changed, 40 insertions(+), 2 deletions(-)
--
2.11.0
next reply other threads:[~2017-10-17 22:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 22:31 Alistair Francis [this message]
2017-10-17 22:31 ` [Qemu-devel] [PATCH v3 1/5] netduino2: Specify the valid CPUs Alistair Francis
2017-10-17 22:31 ` [Qemu-devel] [PATCH v3 2/5] bcm2836: Use the Cortex-A7 instead of Cortex-A15 Alistair Francis
2017-10-17 23:36 ` Philippe Mathieu-Daudé
2017-10-18 7:48 ` Igor Mammedov
2017-10-17 22:31 ` [Qemu-devel] [PATCH v3 3/5] raspi: Specify the valid CPUs Alistair Francis
2017-10-17 22:31 ` [Qemu-devel] [PATCH v3 4/5] xlnx-zcu102: " Alistair Francis
2017-10-20 19:16 ` Eduardo Habkost
2017-10-23 11:14 ` Philippe Mathieu-Daudé
2017-10-26 9:59 ` Alistair Francis
2017-11-29 9:09 ` Igor Mammedov
2017-10-17 22:31 ` [Qemu-devel] [PATCH v3 5/5] xilinx_zynq: " Alistair Francis
2017-10-23 7:26 ` [Qemu-devel] [PATCH v3 0/5] Add a valid_cpu_types property Alistair Francis
2017-11-07 23:30 ` Alistair Francis
2017-11-28 23:26 ` Alistair Francis
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.1508279421.git.alistair.francis@xilinx.com \
--to=alistair.francis@xilinx.com \
--cc=alistair23@gmail.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=imammedo@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).