From: Gavin Shan <gshan@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
peter.maydell@linaro.org, imammedo@redhat.com,
richard.henderson@linaro.org, quic_llindhol@quicinc.com,
b.galvani@gmail.com, strahinja.p.jankovic@gmail.com,
kfting@nuvoton.com, wuhaotsh@google.com,
nieklinnenbank@gmail.com, rad@semihalf.com,
marcin.juszkiewicz@linaro.org, eduardo@habkost.net,
marcel.apfelbaum@gmail.com, wangyanan55@huawei.com,
vijai@behindbytes.com, palmer@dabbelt.com,
alistair.francis@wdc.com, bin.meng@windriver.com,
liwei1518@gmail.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, shan.gavin@gmail.com
Subject: Re: [PATCH v7 2/8] machine: Introduce helper is_cpu_type_supported()
Date: Wed, 29 Nov 2023 09:55:15 +1100 [thread overview]
Message-ID: <34773ba2-e5f7-4f73-a728-57c5004c8502@redhat.com> (raw)
In-Reply-To: <c3e8f22b-c03e-4803-a960-699489afb92b@linaro.org>
Hi Phil,
On 11/28/23 20:38, Philippe Mathieu-Daudé wrote:
> On 27/11/23 00:12, Gavin Shan wrote:
>> The logic, to check if the specified CPU type is supported in
>> machine_run_board_init(), is independent enough. Factor it out into
>> helper is_cpu_type_supported(). machine_run_board_init() looks a bit
>> clean with this. Since we're here, @machine_class is renamed to @mc
>> to avoid multiple line spanning of code. The error messages and comments
>> are tweaked a bit either.
>>
>> No functional change intended.
>>
>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>> ---
>> hw/core/machine.c | 90 +++++++++++++++++++++++++++--------------------
>> 1 file changed, 51 insertions(+), 39 deletions(-)
>>
>> diff --git a/hw/core/machine.c b/hw/core/machine.c
>> index b3ef325936..05e1922b89 100644
>> --- a/hw/core/machine.c
>> +++ b/hw/core/machine.c
>> @@ -1387,13 +1387,57 @@ out:
>> return r;
>> }
>> +static void is_cpu_type_supported(const MachineState *machine, Error **errp)
>
> Functions taking an Error** last argument should return a boolean value.
>
Correct, especially @errp instead of @local_err will be passed from
machine_run_board_init() to is_cpu_type_supported(). We needs an
indicator for machine_run_board_init() to bail immediately to avoid
calling mc->init() there in the failing cases.
>> +{
>> + MachineClass *mc = MACHINE_GET_CLASS(machine);
>> + ObjectClass *oc = object_class_by_name(machine->cpu_type);
>> + CPUClass *cc;
>> + int i;
>> +
>> + /*
>> + * Check if the user specified CPU type is supported when the valid
>> + * CPU types have been determined. Note that the user specified CPU
>> + * type is provided through '-cpu' option.
>> + */
>> + if (mc->valid_cpu_types && machine->cpu_type) {
>> + for (i = 0; mc->valid_cpu_types[i]; i++) {
>> + if (object_class_dynamic_cast(oc, mc->valid_cpu_types[i])) {
>> + break;
>> + }
>> + }
>> +
>> + /* The user specified CPU type isn't valid */
>> + if (!mc->valid_cpu_types[i]) {
>> + error_setg(errp, "Invalid CPU type: %s", machine->cpu_type);
>> + if (!mc->valid_cpu_types[1]) {
>> + error_append_hint(errp, "The only valid type is: %s",
>> + mc->valid_cpu_types[0]);
>> + } else {
>> + error_append_hint(errp, "The valid types are: %s",
>> + mc->valid_cpu_types[0]);
>> + }
>> +
>> + for (i = 1; mc->valid_cpu_types[i]; i++) {
>> + error_append_hint(errp, ", %s", mc->valid_cpu_types[i]);
>> + }
>> +
>> + error_append_hint(errp, "\n");
>> + return;
>> + }
>> + }
>> +
>> + /* Check if CPU type is deprecated and warn if so */
>> + cc = CPU_CLASS(oc);
>> + if (cc && cc->deprecation_note) {
>> + warn_report("CPU model %s is deprecated -- %s",
>> + machine->cpu_type, cc->deprecation_note);
>
> Why did you move the deprecation warning within the is_supported check?
>
This check is more relevant to CPU type, to check if the CPU type has
been deprecated. Besides, @oc and @cc can be dropped from machine_run_board_init().
>> + }
>> +}
>> void machine_run_board_init(MachineState *machine, const char *mem_path, Error **errp)
>> {
>> ERRP_GUARD();
>> MachineClass *machine_class = MACHINE_GET_CLASS(machine);
>> - ObjectClass *oc = object_class_by_name(machine->cpu_type);
>> - CPUClass *cc;
>> Error *local_err = NULL;
>> /* This checkpoint is required by replay to separate prior clock
>> @@ -1449,43 +1493,11 @@ void machine_run_board_init(MachineState *machine, const char *mem_path, Error *
>> machine->ram = machine_consume_memdev(machine, machine->memdev);
>> }
>> - /* If the machine supports the valid_cpu_types check and the user
>> - * specified a CPU with -cpu check here that the user CPU is supported.
>> - */
>> - if (machine_class->valid_cpu_types && machine->cpu_type) {
>> - int i;
>> -
>> - for (i = 0; machine_class->valid_cpu_types[i]; i++) {
>> - if (object_class_dynamic_cast(oc,
>> - machine_class->valid_cpu_types[i])) {
>> - /* The user specified CPU is in the valid field, we are
>> - * good to go.
>> - */
>> - break;
>> - }
>> - }
>> -
>> - if (!machine_class->valid_cpu_types[i]) {
>> - /* The user specified CPU is not valid */
>> - error_setg(&local_err, "Invalid CPU type: %s", machine->cpu_type);
>> - error_append_hint(&local_err, "The valid types are: %s",
>> - machine_class->valid_cpu_types[0]);
>> - for (i = 1; machine_class->valid_cpu_types[i]; i++) {
>> - error_append_hint(&local_err, ", %s",
>> - machine_class->valid_cpu_types[i]);
>> - }
>> - error_append_hint(&local_err, "\n");
>> -
>> - error_propagate(errp, local_err);
>> - return;
>> - }
>> - }
>> -
>> - /* Check if CPU type is deprecated and warn if so */
>> - cc = CPU_CLASS(oc);
>> - if (cc && cc->deprecation_note) {
>> - warn_report("CPU model %s is deprecated -- %s", machine->cpu_type,
>> - cc->deprecation_note);
>> + /* Check if the CPU type is supported */
>> + is_cpu_type_supported(machine, &local_err);
>> + if (local_err) {
>> + error_propagate(errp, local_err);
>
> This becomes:
>
> if (!is_cpu_type_supported(machine, errp)) {
>
Nod
>> + return;
>> }
>> if (machine->cgs) {
>
Thanks,
Gavin
next prev parent reply other threads:[~2023-11-28 22:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 23:12 [PATCH v7 0/8] Unified CPU type check Gavin Shan
2023-11-26 23:12 ` [PATCH v7 1/8] machine: Use error handling when CPU type is checked Gavin Shan
2023-11-28 9:43 ` Philippe Mathieu-Daudé
2023-11-28 22:47 ` Gavin Shan
2023-11-26 23:12 ` [PATCH v7 2/8] machine: Introduce helper is_cpu_type_supported() Gavin Shan
2023-11-28 9:38 ` Philippe Mathieu-Daudé
2023-11-28 22:55 ` Gavin Shan [this message]
2023-11-26 23:12 ` [PATCH v7 3/8] machine: Print CPU model name instead of CPU type Gavin Shan
2023-11-28 9:55 ` Philippe Mathieu-Daudé
2023-11-29 3:53 ` Gavin Shan
2023-11-26 23:12 ` [PATCH v7 4/8] hw/arm/virt: Hide host CPU model for tcg Gavin Shan
2023-11-28 9:29 ` Philippe Mathieu-Daudé
2023-11-26 23:12 ` [PATCH v7 5/8] hw/arm/virt: Check CPU type in machine_run_board_init() Gavin Shan
2023-11-27 10:13 ` Marcin Juszkiewicz
2023-11-27 10:42 ` Gavin Shan
2023-11-26 23:12 ` [PATCH v7 6/8] hw/arm/sbsa-ref: " Gavin Shan
2023-11-26 23:12 ` [PATCH v7 7/8] hw/arm: " Gavin Shan
2023-11-28 9:31 ` Philippe Mathieu-Daudé
2023-11-26 23:12 ` [PATCH v7 8/8] hw/riscv/shakti_c: " Gavin Shan
2023-11-27 10:10 ` [PATCH v7 0/8] Unified CPU type check Marcin Juszkiewicz
2023-11-27 10:15 ` Gavin Shan
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=34773ba2-e5f7-4f73-a728-57c5004c8502@redhat.com \
--to=gshan@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=b.galvani@gmail.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=kfting@nuvoton.com \
--cc=liwei1518@gmail.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=nieklinnenbank@gmail.com \
--cc=palmer@dabbelt.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.com \
--cc=richard.henderson@linaro.org \
--cc=shan.gavin@gmail.com \
--cc=strahinja.p.jankovic@gmail.com \
--cc=vijai@behindbytes.com \
--cc=wangyanan55@huawei.com \
--cc=wuhaotsh@google.com \
--cc=zhiwei_liu@linux.alibaba.com \
/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).