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 3/8] machine: Print CPU model name instead of CPU type
Date: Wed, 29 Nov 2023 14:53:23 +1100 [thread overview]
Message-ID: <9b3db19d-8756-447a-a9a3-948c826c1b40@redhat.com> (raw)
In-Reply-To: <32bf41db-375b-4061-bbf3-17ae6b543926@linaro.org>
Hi Phil,
On 11/28/23 20:55, Philippe Mathieu-Daudé wrote:
> On 27/11/23 00:12, Gavin Shan wrote:
>> The names of supported CPU models instead of CPU types should be
>> printed when the user specified CPU type isn't supported, to be
>> consistent with the output from '-cpu ?'.
>>
>> Correct the error messages to print CPU model names instead of CPU
>> type names.
>>
>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>> ---
>> hw/core/machine.c | 21 +++++++++++++++------
>> 1 file changed, 15 insertions(+), 6 deletions(-)
>>
>> diff --git a/hw/core/machine.c b/hw/core/machine.c
>> index 05e1922b89..898c25552a 100644
>> --- a/hw/core/machine.c
>> +++ b/hw/core/machine.c
>> @@ -1392,6 +1392,7 @@ static void is_cpu_type_supported(const MachineState *machine, Error **errp)
>> MachineClass *mc = MACHINE_GET_CLASS(machine);
>> ObjectClass *oc = object_class_by_name(machine->cpu_type);
>> CPUClass *cc;
>> + char *model;
>> int i;
>> /*
>> @@ -1408,17 +1409,25 @@ static void is_cpu_type_supported(const MachineState *machine, Error **errp)
>> /* The user specified CPU type isn't valid */
>> if (!mc->valid_cpu_types[i]) {
>> - error_setg(errp, "Invalid CPU type: %s", machine->cpu_type);
>> + model = cpu_model_from_type(machine->cpu_type);
>> + g_assert(model != NULL);
>> + error_setg(errp, "Invalid CPU type: %s", model);
>> + g_free(model);
>
> g_autofree char *requested = cpu_model_from_type(machine->cpu_type);
> error_setg(errp, "Invalid CPU type: %s", requested);
>
Yes, g_autofree shall be used here. Besides, "Invalid CPU type" needs to
be "Invalid CPU model".
>> +
>> + model = cpu_model_from_type(mc->valid_cpu_types[0]);
>> + g_assert(model != NULL);
>> if (!mc->valid_cpu_types[1]) {
>> - error_append_hint(errp, "The only valid type is: %s",
>> - mc->valid_cpu_types[0]);
>> + error_append_hint(errp, "The only valid type is: %s", model);
>
> g_autofree char *model = cpu_model_from_type(mc->valid_cpu_types[0]);
> error_append_hint(errp, "The only valid type is: %s\n", model);
>
Yes, as above.
>> } else {
>> - error_append_hint(errp, "The valid types are: %s",
>> - mc->valid_cpu_types[0]);
>> + error_append_hint(errp, "The valid types are: %s", model);
>
> Please move all the enumeration in this ladder, this makes the logic
> simpler to follow:
>
> error_append_hint(errp, "The valid types are: ");
> for (i = 0; mc->valid_cpu_types[i]; i++) {
> g_autofree char *model =
> cpu_model_from_type(mc->valid_cpu_types[i]);
> error_append_hint(errp, ", %s", model);
> }
> error_append_hint(errp, "\n");
>
Yes, but we still need to ensure mc->valid_cpu_types[0] != NULL in advance.
"The valid types are: " needs to be "The valid models are: ". Besides,
your proposed code needs to be adjusted a bit like below. Otherwise, we
will get output "The valid types are: , aaa, bbb"
} else {
error_append_hint(errp, "The valid types are: ");
for (i = 0; mc->valid_cpu_types[i]; i++) {
error_append_hint(errp, "%s%s",
mc->valid_cpu_types[i],
mc->valid_cpu_types[i + 1] ? ", " : "");
}
error_append_hint(errp, "\n");
}
I will have separate PATCH[v8 3/9] to have the changes, together with the
precise hint when only mc->valid_cpu_types[0] is valid.
>> }
>> + g_free(model);
>> for (i = 1; mc->valid_cpu_types[i]; i++) {
>> - error_append_hint(errp, ", %s", mc->valid_cpu_types[i]);
>> + model = cpu_model_from_type(mc->valid_cpu_types[i]);
>> + g_assert(model != NULL);
>> + error_append_hint(errp, ", %s", model);
>> + g_free(model);
>> }
>> error_append_hint(errp, "\n");
Thanks,
Gavin
next prev parent reply other threads:[~2023-11-29 3:54 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
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 [this message]
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=9b3db19d-8756-447a-a9a3-948c826c1b40@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).