From: Eduardo Habkost <ehabkost@redhat.com>
To: Alistair Francis <alistair.francis@xilinx.com>
Cc: qemu-devel@nongnu.org, marcel@redhat.com, alistair23@gmail.com,
imammedo@redhat.com
Subject: Re: [Qemu-devel] [RFC v2 1/2] machine: Add a valid_cpu_types property
Date: Tue, 3 Oct 2017 11:10:02 -0300 [thread overview]
Message-ID: <20171003141002.GB7087@localhost.localdomain> (raw)
In-Reply-To: <d2e446ccb46d71bed3191fc97fe1aa6c884ea4ba.1506037164.git.alistair.francis@xilinx.com>
On Thu, Sep 21, 2017 at 04:41:50PM -0700, Alistair Francis wrote:
> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
> ---
>
> RFC v2:
> - Rebase on Igor's cpu_type work
> - Use object_class_dynamic_cast()
> - Use a NULL terminated cahr** list
> - Do the check before the machine_class init() is called
>
>
> hw/core/machine.c | 35 +++++++++++++++++++++++++++++++++++
> include/hw/boards.h | 1 +
> 2 files changed, 36 insertions(+)
>
> diff --git a/hw/core/machine.c b/hw/core/machine.c
> index 80647edc2a..abebfabdb8 100644
> --- a/hw/core/machine.c
> +++ b/hw/core/machine.c
> @@ -758,6 +758,41 @@ void machine_run_board_init(MachineState *machine)
> if (nb_numa_nodes) {
> machine_numa_finish_init(machine);
> }
> +
> + if (machine_class->valid_cpu_types && machine->cpu_type) {
> + int i;
> +
> + for (i = 0; machine_class->valid_cpu_types[i]; i++) {
> + ObjectClass *class = object_class_by_name(machine->cpu_type);
> +
> + if (!class) {
> + break;
> + }
> +
> + if (object_class_dynamic_cast(class,
> + machine_class->valid_cpu_types[i])) {
> + /* The user specificed CPU is in the valid field, we are
> + * good to go.
> + */
> + goto done;
I would move the object_class_by_name() call outside the for loop
and remove the "goto", like this:
if (machine->cpu_type && machine_class->valid_cpu_types) {
ObjectClass *class = object_class_by_name(machine->cpu_type);
int i;
/* machine->cpu_type is supposed to be always a valid QOM type */
assert(class);
for (i = 0; machine_class->valid_cpu_types[i]; i++) {
if (object_class_dynamic_cast(class,
machine_class->valid_cpu_types[i])) {
/* Valid CPU type, we're good to go */
break;
}
}
if (!machine_class->valid_cpu_types[i]) {
error_report(...);
...
}
}
machine_class->init(machine);
> + }
> + }
> +
> + /* The user specified CPU must not be a valid CPU, print a sane
> + * error
> + */
> + error_report("Invalid CPU: %s", machine->cpu_type);
> + error_printf("The valid options are: %s",
> + machine_class->valid_cpu_types[0]);
> + for (i = 1; machine_class->valid_cpu_types[i]; i++) {
> + error_printf(", %s", machine_class->valid_cpu_types[i]);
> + }
> + error_printf("\n");
I would still like to make this share code with
query-cpu-definitions one day, but I'm OK with this
implementation.
I would just rewrite the message as "valid types are:" instead of
"valid options are:" and "Invalid CPU type:" instead of "Invalid
CPU:", because the -cpu option doesn't need to match a string in
valid_cpu_types exactly, it just needs to resolve to a type that
implements a valid type.
> +
> + exit(1);
> + }
> +
> +done:
> machine_class->init(machine);
> }
>
> diff --git a/include/hw/boards.h b/include/hw/boards.h
> index 156e0a5701..191a5b3cd8 100644
> --- a/include/hw/boards.h
> +++ b/include/hw/boards.h
> @@ -191,6 +191,7 @@ struct MachineClass {
> bool has_hotpluggable_cpus;
> bool ignore_memory_transaction_failures;
> int numa_mem_align_shift;
> + const char **valid_cpu_types;
> void (*numa_auto_assign_ram)(MachineClass *mc, NodeInfo *nodes,
> int nb_nodes, ram_addr_t size);
>
> --
> 2.11.0
>
>
--
Eduardo
next prev parent reply other threads:[~2017-10-03 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 23:41 [Qemu-devel] [RFC v2 0/2] Add a valid_cpu_types property Alistair Francis
2017-09-21 23:41 ` [Qemu-devel] [RFC v2 1/2] machine: " Alistair Francis
2017-10-03 14:10 ` Eduardo Habkost [this message]
2017-09-21 23:41 ` [Qemu-devel] [RFC v2 2/2] netduino2: Specify the valid CPUs Alistair Francis
2017-10-02 18:42 ` [Qemu-devel] [RFC v2 0/2] Add a valid_cpu_types property Alistair Francis
2017-10-02 19:41 ` Philippe Mathieu-Daudé
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=20171003141002.GB7087@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=alistair23@gmail.com \
--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).